E1: 47: Price History field (F4211.SO09) Blank for Kit Line when Using EDI Inbound Purchase Order Edit/Create (R47011) and the Price Is Overridden in EDI Purchase Order Detail - Inbound (F47012) (Doc ID 2864070.1)

Last updated on JUNE 21, 2022

Applies to:

Symptoms

The Price History field (F4211.SO09) is not updated on the kit line when the sales order is created from EDI R47011 and the price is overridden in EDI Purchase Order Detail - Inbound (F47012).

If the Unit Price is not populated in F47012, then the F4211.SO09 field is updated accordingly (with a value of 1).

In addition, when creating a sales order using P4210 for same kit that have same advance pricing and override the price after selecting the components, then the F4211.SO09 field is updated as 8.
 
This is what is expected as per E1: 42: Fields SO01-SO20 in the Sales Order Detail file (P4210/P42101/R42565/F4211/F49211) (Doc ID 1268884.1)
The SO09 field indicates the existence of pricing history behind a given sales detail line. Valid values are:
1 - Standard detail adjustments exist in the price history file. These adjustments might include accruals.
2 - At least one of the adjustments in the price history file is a rebate accrual (ACNT = 5) and will be processed by Sales Update for purposes of sales volume history accumulation.
3 - At least one of the adjustments in the price history file is a volume-level adjustment.
4 - A volume-level adjustment and a rebate accrual exist in the price history file.
8 - The 'Zero Price' row exit is taken or the unit price and extended price have been manually overridden.
9 - The unit price and extended price (both foreign and domestic) fields are blanked out by the user.

The issue can be reproduced at will with the following steps:

1. Use a kit parent with kit pricing method 1.
2. P3002 Add a Bill of Materials with 2 components for that kit.
3. P4071 Set an adjustment with Control Code 4 (accruals) and Apply on Override Price checked.
4. P47010 Populate the minimum required fields in the F47011 and F47012. Ensure to populate the Adj. Schedule field and the Unit price field with a new price.
5. Run R47011 and check the SO created. Verify the F4211.SO09 field. It has no value.

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.