Introduction: Update (02-05)

Overview

This selection is used to update sales transactions for a branch/day into the Sales Transactions files. This is the last step of the Sales Transaction Update Process.

During update, sales transaction information is sent to many other areas of the system. For more information on how Sales Transactions interacts with other areas of the system, please see the Sales Transactions Overview section of this document.

NOTE: As of the 21.500 Tyler Release, amounts are automatically interfaced to G/L at the time of update. You no longer need to run G/L Interface (02-41).

Special Notes

  • A branch/day must have a status of ‘G’ in order to be eligible for update.
  • You can include all branches or a single branch in the update. You can also choose to update a single day or a range of days.
  • You can update transactions for more than one region at a time. The system can automatically restart an update if it does not run to completion (i.e., a power failure). If this happens, run the update again for the region that did not run to completion. Branches/days that did not successfully update during the last attempt will appear on the screen. Follow the on-screen instructions and the update will resume where it left off.

Error Records

To handle unusual situations during the update process, the error records listed below exist to accommodate changes that occur in the database between the time of POS Entry and Update. These changes might include: inventory items that are inadvertently deleted, A/R Open accounts that are deleted, or salesmen that are removed from the Sales Analysis files.

Inventory
Item Number ZZZZZZZZZZZZ
Department Code XX
Product Type Code XXX
Brand Code XXXXX

A/R Open
Account 9999999 – Layaway error record
Account R999999 – Open Charge error record
Account F999999 – Fin. Company Memo error record
Account *###### – Retail Credit Memo error record

Payroll
(Sales Analysis)
Salesman 000