My Oracle Support Banner

WS: 42: Sales Update: Overview (P42800) (Doc ID 626781.1)

Last updated on OCTOBER 02, 2018

Applies to:

JD Edwards World Sales Order Management - Version A7.3 cume 4 and later
Information in this document applies to any platform.

Purpose

End of day processing is the last step in sales order processing and consists of updating, verifying, and posting daily sales information.  This is perhaps the most important step in the sales order processing cycle because the system updates the records in the JD Edwards World Sales Order Management system and the records in the other systems with which it interacts, such as Accounts Receivable and Inventory.

In the JD Edwards World Sales Order Management system, the Sales Update program P42800 is used to perform this End of Day processing.

This document provides information related to system interfaces, file updates, processing order, related reports, Automatic Accounting Instructions used, accounting as well as links to related/referenced documents.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Details
 Overview
 System Interfaces and File Updates
 Accounts Receivable (A/R) and General Accounting (F0311/F0911)
 Inventory (F41021/F4111)
 Sales History (F4229/F4115)
 Commissions (F42005)
 Sales Order Detail History (F42119)
 Sales Order Header History (F42019)
 Tax File (F0018)
 Sales Order Detail File (F4211)
 Associated Text (F4314)
 Price Adjustments History (F4074)
 Processing Order
 First P42800 Cycle:
 Second P42800 Cycle:
 Third P42800 Cycle:
 Sales Tax File F0018
 Reports Generated By Sales Update
 Invoice Journal (P42800)
 Error Report P42801
 Sales Journal (P42810)
 Sales Update AAIs
 Tax AAIs Used By Sales Update
 DMAAI 4250 vs. AAI RT
 Bypassing Accounts Receivable
 You Can Create Four Different Types Of Batches With Sales Update.
 Running Sales Update In Summary vs. Detail
 Accounts Receivable Entries
 Notes on summarization:
 General Ledger Entries
 Summarizing Inventory and COGS to a Separate Batch:
 Running Sales Update In Proof vs. Final Mode
 Updates To On-Hand Quantity And The Cardex
 Relieving Inventory at Ship Confirmation:
 Relieving Inventory at Sales Update:
 Running invoiced orders vs. orders that have not been invoiced
 How to tell if an invoice number has been assigned
 Purging Records By Running Sales Update
 What happens if something is incorrect such as duplicate data, incorrect invoice numbers, files half updated? How can the data be repaired? Can Sales Update be re-run?
 Common reasons for asking this question include:
 Change G/L or Invoice Dates
 Records Not Included in Update
 Data Purged Erroneously
 Data Not Purged
 An incorrect account number is used and you need to change it to the correct account:
 One or more data files are not written 
 Sales Update Error Report
   
  
 
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.