E1: 32: Line Number (LNID) not Populating in Work Order Table (F4801) for Configured Orders Causes Sales Update (R42800) to Report Incorrect Journal Entries With Product Cost Detail (Doc ID 3071150.1)

Last updated on FEBRUARY 11, 2025

Applies to:

Symptoms

When releasing a quote (P420111) for a configured parent with configured line type W children, the system will not populate the Line Number (LNID) field in the Work Order table (F4801) for the child Work Orders. This can have a significant impact in a branch that has "Use Product Cost Detail" active in the Branch Constants (P41001). If there are multiple configured lines in a Sales Order (P4210) that was created from a quote, Sales Update (R42800) may create overvalued COGS journal entries.

Steps:
1. Create a configured parent and two configured child items (P4101, P41026).
2. Create Configured Item Segments (P3291) for all configured items.
3. Create simple P Assembly Inclusion Rules for the child configured items (P3293) using purchased items with Frozen Standard Costs (F30026).
4. In the parent's P Assembly Inclusion Rules, add the configured children, both with Line Type W.
5. Create a Sales Quote (SQ) order for the configured parent (P4210).
6. Release the quote to a Sales Order (P420111).
7. Inquire on the related Work Orders in databrowser, table F4801. Notice that the Line Number (LNID) field is blank for the child Work Orders.
8. Run Sales Update (R42800) over the configured Sales Order; notice that the journal entries related to Cost of Goods Sold (COGS) may be overvalued.

Changes

Cause

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