14 Sales Posting
If not using Sales Audit, such as if you are using a 3rd party sales auditing solution, sales and returns from your point-of-sale (POS) and order management (OMS) solutions can be integrated directly to Merchandising using the Upload Sales job.
Once the data is staged in Merchandising, other modules take over the posting of that data to sales transaction, sales history, and stock-on-hand tables. This is the processing used by data integrated from the Oracle Retail Sales Audit solution (as part of the Merchandising Foundation Cloud Service), as well.
The Sales Posting process consists of a number of related programs.
-
Upload POSU File for Processing (uploadsales.ksh) reads the input file and writes its contents to a series of staging tables. Process Multiple POSU Files (uploadsales_all.ksh) wraps uploadsales.ksh to process multiple files.
-
Main Processing of Staged Sales/Returns (salesprocess.ksh) reads the staged data and performs major validation, financial and inventory processing.
-
Reject POSU Transactions (salesgenrej.ksh) creates a reject file for transactions that fail validation.
-
Archive Successfully Posted Transactions (salesuploadarch.ksh) archives successfully processed transactions and clears them out of the staging tables.
-
Purge Aged Archived POSU Transactions (salesuploadpurge.ksh) purges transactions from the archive tables after the transactions age out of the system.