You are on page 1of 8

JDE Questions - Sales

Sales Update
Purpose of Sales Update

During the daily processing of sales transactions, the sales system operates independently from
other systems (except for inventory). The primary purpose of the sales update program is to
interface the sales system with other EnterpriseOne systems.

1. Updates the Financials systems by:

 Creating journal entries in the General Ledger (F0911) file.


 Creating receivable records in the Accounts Receivable (F03B11) file.

2. Updates the item's on-hand quantity if not previously done by Shipment Confirmation
(P4205).
3. Closes out the sales order.
4. Purges the closed sales order to the history files if the processing options are set. Files that
will be purged and/or moved to history include:

 Sales Order Detail records (F4211) are moved to the Sales Order Detail History File
(F42119).
 Sales Order Detail Tag records (F49211) are moved to the Sales Order Detail Tag
History File (F49219).
 Sales Header records (F4201) are moved to the Sales Order Header History File
(F42019).
 Media Objects storage records (F00165) are purged but not moved to a history file.
 Price Adjustment History records (F4074) are purged but not moved to a history file.

Table Updates

The update of the following tables is dependent on line type setup, Branch/Plant setup or
processing options on the Update tab behind Sales Update (R42800):

 Accounts Receivable (F03B11) and General Accounting (F0911)


 Inventory (F41021/F4111)
 Sales History (F4229) and Item History (F4115)
 Sales Commission (F42005)
 Sales Order Detail History (F42119)
 Sales Order Header History (F42019)
 Sales Order Detail File (F4211)
 Media Objects (F00165)
 Price Adjustments History (F4074)
 Ship And Debit Claims (F4576)

Page 1 of 8
JDE Interview Questions
Sales Update AAIs

DMAAIs used by Sales Update 


Debit Credit

4220 - Cost of Goods Sold 4240 - Inventory

Debtor Control A/c 4230 - Revenue

Debtor Control A/c 4270 - Price Adjustments

4245 - AR Trade

4280 - Rebate Payable

Commitment Types
Soft Commitment

 Does not specify a location from where to remove inventory.


 Uses the primary location as the default location at order entry.

Hard Commitment

 Normally occurs at Print Pick Slips (R42520), yet can occur at any time during the sales order
process by running Inventory Commitment (R42997).
 Specify a location (SDLOCN) or lot (SDLOTN) other than Primary in the Sales Order Detail
(F4211) at Sales Order Entry (P4210).

Future Commitment

 Uses a future Promised Ship Date (PPDJ) at time of Sales Order Entry (P4210).
 Determined by Specific Commitment Days field (COMH) in the Branch Plant Constants
(P41001).
 To re-commit future commitments the Re-Commit Future Orders (R42995) must be run.
 Future commitments only apply to line types with a Y inventory interface.
 Nonstock lines and direct ship items will not be future committed.  Nonstock lines and direct
ship lines update the Order Amount (OTOT) value for orders.

Specific commitment (days)  

 Field COMH set in the Branch Plant Constants (P41001).


 Determines when to commit inventory to an order in sales order processing.  This value is
added to today's date and compared with the Promised Ship Date (PPDJ) for the order line
to determine the type of commitment created.  If the Pick Date is greater than the calculated
date, the order line will be future committed.
 Set to '999' to eliminate future commitments for individual branches.

Page 2 of 8
JDE Interview Questions

Repost Active Sales Orders (R42995)

Used for four purposes via the appropriate Processing Option settings:  

Future Orders: To recommit future sales orders:

 Sales Detail Lines having quantities future committed are changed to either hard or
soft committed and a hold code is applied if applicable.
 Sales Detail Line having Requested Date far enough in the future are changed to a
future committed line.

Repost Active Sales Orders: To re-establish Sales Order data by:

 Updating item commitment quantities in the Item Location (F41021) file with
information from the Sale Order Detail (F4211) file.
 Updating commitment quantities in the Location Detail Information (F4602) file with
information from the Sales order Detail (F4211) file. This update occurs if the
Warehouse Management System is active.

Repost Order Totals: To re-establish Sales Order data by:

 Updating order totals in the Sales Order Header (F4201) file with information from
the Sales Order Detail (F4211) file.

Repost Customer Open Order Amount:  To re-establish Sales Order data by:

 Updating open order amounts in the Customer Master (F03012) file with information
from the Sale Order Detail (F4211) file.

Transfer Order (ST/OT)

A Transfer Order is an internal sales order used to transfer inventory from one warehouse (branch) to another.
The Transfer Order (P4210) program creates both a sales order in the "From Branch" (shipping branch) and a
purchase order in the "To Branch" (receiving branch). The default document types created are ST (sales
order) and OT (purchase order), and are often referred to as an ST/OT order. When a sales transfer order
(ST) order is created, the purchase transfer order (OT) is also created, regardless of whether the "Generate
Purchase Order" flag is activated or not in the line type constants (P40205). Further, field SDS011
(Transfer/Direct Ship/Intercompany) in the Sales Order Detail file (F4211) is marked with a '1', indicating a
transfer order.
EnterpriseOne does not support EDI creation or updating of transfer orders using the 850 Inbound
Order Creation (R47011) or 860 Inbound Order Change (R47131) programs. There is no "From Branch/Plant"
and "To Branch/Plant" field to enter in the EDI 850 Header Table (F47011) or EDI 860 Header Table (F47131).
The ST/OT functionality is internal and is intended for transfers within an organization's branches, whereas the
EDI system is for use between an organization and its external customers.

Page 3 of 8
JDE Interview Questions

Sales Order Intercompany Processing (P4210/P4205/R4210IC/R42800)


One company sells items to a customer but the goods are shipped from a different company. The order type
of SI is used for the sales order to the customer. On the SI, the header branch indicates the selling company,
and the detail branch indicates the shipping company.  An intercompany sales order with an order type of SK
is created for the shipping company to bill the selling company for the items that were shipped to the
customer. An intercompany purchase order with an order type of OK is created for the selling company that
owes the shipping company for the items.

Page 4 of 8
JDE Interview Questions

Process Flow
An order type of SI is used for the sales order to the customer. On the SI, the header branch indicates the
selling company. The detail branch indicates the shipping company. The items on the sales order will be hard
committed to particular lot/locations in the Detail Branch and then shipped to the customer. Once the goods
are shipped, the Header Company can invoice the customer and the Shipping (Detail) Company can invoice
the Header Company. Sales Update (R42800) creates accounting entries for the transaction.

Page 5 of 8
JDE Interview Questions

Q1: Explain Sales Process with Program Numbers


 Typical sales process starts with Sales Order Entry. Sales order entry program is
P4210. Sales order has header and detail. (All the header information is stored
into table F4201 Sales order Header file) Header information includes Branch
plant, customer sold to, customer ship to, order date, payment terms, shipping
information & such. Details information includes item number, quantity, price,
promised ship date, promised delivery date & such. Detail can have multiple
line items with similar information. If we use advance pricing then can take row
exit to price break up screen and manually override any price, if needed. If
needed, inventory can be hard committed while order entry. Last/next status is
520/540. (All details information is stored into Sales order Detail file F4211)
 Next step in the process can be Credit Check. If order amount is more than
open credit then order goes on hold, which can be relieved by credit &
collection department.
 Next step in the process is Print Pick Slip. Pick slip program is R42520. This is a
batch application. Typically inventory is hard committed during pick slip.
Last/next status is 540/560
 Next step in the process is Confirm Shipment. Confirm shipment program is
P4205. Typically inventory is relieved during this stage. Inventory can also be
relieved during sales update. This can be governed by processing option of
P4205. We need to define order type in UDC 40/IU, if we need to relieve
inventory during this step. Last/next status is 560/580
 Next step in the process is Invoice Print. The program is R42565. At this stage,
system assigns invoice number and document type. Last/next status is 580/620
 Final step in the process is Sales Update. The program is R42800. At this stage
sales order lines are purged to sales history. This also updates customer ledger
and account ledger. Last/next status is 620/999 (Based on the business decision
Sales order details can be purged into Sales order History file F42119). At the
same time based on the Order activity rules definition transactions can be
stored into SO detail ledger file F42199)

Q2: How do we hard commit inventory while Sales Order Entry?


Inventory can be hard committed by entering respective location/lot number or serial
number at the time of order entry. Typically inventory is hard committed at pick slip
stage but this is also an option in JDE.

Page 6 of 8
JDE Interview Questions

Q3: How many ways you can hard commit inventory in sales process?
Inventory can be hard committed in two ways. One is while order entry by entering
respective location/lot number or serial number at the time of order entry. Or can be
at pick slip stage.

Q4: How many ways you can relieve inventory in sales process and set ups for it?
Inventory can be relieved at two stages. One at confirm shipment. This can be
governed by processing option of P4205 application. We also need to set up
respective order type in UDC 40/IU. If this set up is not done then inventory is
relieved at sales update stage. We need to set the processing option of R42800
application.

Q5: Sales Update Accounting entries and DMAAI’s


There are basic four accounting entries passed at sales update stage.
Debit Credit
4220 - Cost of Goods Sold 4240 - Inventory
RC AAI - Debtor Control A/c 4230 - Revenue
Debtor Control A/c 4270 - Price Adjustments
4245 - AR Trade (ST/OT)
4280 - Rebate Payable

Q6: What are the basic tables used in Sales


Basic Sales files are:
F4201 Sales Order Header File
F4211 Sales Order Detail File
F42019 Sales Order Header History File
F42119 Sales Order Detail History File
F42199 Sales Order Detail Ledger File
F4070 Price Adjustment Schedule
F4071 Price Adjustment Definition File
F4072 Price Adjustment Detail File

Page 7 of 8
JDE Interview Questions

F4074 Price Adjustment Ledger File


Q7: How the commitments can be corrected in sales?
We can use repost program R42995 (Repost Active Sales Orders) to correct
commitments. Typically this is run in nightly scheduler to correct daily commitments.

Page 8 of 8

You might also like