JD Edwards Sales Order Management (SOM) is a complex module within the JDE Distribution Suite. Because it involves customer-facing interaction and transactions, it incorporates more functionality than most other JD Edwards modules.
Sales Order Management is usually the starting point of the Order to Cash business process. However, the actual receipt and application of cash to sales invoices is a part of the Accounts Receivable module (part of the JDE Financials Suite).
A sales order transaction is typically driven by some type of demand. Demand originates internally or externally and includes sales orders, work orders, forecasts; essentially anything that requires the business to fulfill that demand.
While SOM supports a large variety of optional processing steps, the basic steps used by most JDE clients are Order Enrty, Pick Slip Print, Ship Confirmation, Invoice Print, abd Sales Update.
The flow of sales orders in JD Edwards is driven by a flow of "Last" and "Next" statuses which are assigned and then 'bumped' based on the 'Order Activity Rules'.
Here is a brief explanation of each application. Keep in mind that the configuration behind each step can support a great deal more functionality than what is described below.
A single sales order in JD Edwards has a header record and one or more detail records. The header contains information that applies to the entire order, such as Order Date, Payment Terms, and Currency Code. These fields and many others may be overridden at the detail level. Sales Order detail records contain the Item Number of the product being sold, Order Quantity, Unit Price, and Unit of Measure just to name a few.
To enter a sales order, the only data which is absolutely required is the Ship to Address Number, the Item Number, and the Order Quantity. All other data values will default in from the Address Book, Customer Master, and tem Master or Branch/Plant tables. Additional flexibility can be achieved by using Preference Processing to control the data which defaults into the sales order.
A pick slip is a report that is used by the warehouse to gather the items that are on a sales order and due to be shipped.
Pick slips are printed to initiate the "Pick-Pack-Ship" process so that customers' orders are delivered on a timely basis. The Pick Slip Print batch program processes selected sales order lines that are at the correct 'Next Status' as defined by the Order Activity Rules. In addition to Next Status, you can control the generation of Pick Slips based on item availability, customer priority or a variety of different date criteria.
Ship Confirmation is an online application that is accessed after the pick slip has been marked up by shipping personnel to indicate how many items were actually picked and packed for shipment.
Normally, all the items on a sales order that print on a pick slip are shipped, but there may be exceptions due to inaccurate inventory records. When this happens, the Ship Confirmation program automatically updates lines that have been shipped, partially shipped and backordered, or canceled as appropriate.
Note: Rating and routing of shipments requires the JD Edwards Transportation Management module, or Oracle's Transportation module.
Invoices are normally printed in batch mode every night. Order lines that are at the correct 'Next Status' (i.e., lines that have been ship confirmed) are printed using the company's customized invoice format.
Sales Update is almost always run at night and is a resource consuming batch job. It processes order lines that have been invoiced (again based on the correct 'Next Status' code) and updates the General Ledger and the Accounts Receivable Sub-Ledger. Based on configuration settings, Sales Update will also update various historical usage tables and move completed lines to the Sales History tables.
Sales Order Management interfaces with several other JDE modules, including but not limited to Inventory, Advanced Pricing, Transportation, Address Book (Customer Master), General Ledger, and Accounts Receivable.