E1: 45: "Skip To" Not Working Correctly on MIN Adjustment
(Doc ID 2553112.1)
Last updated on MARCH 23, 2020
Applies to:
JD Edwards EnterpriseOne Advanced Pricing - Sales - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Sales Order Entry (P4210)
When the Skip To on the first adjustment in the schedule is set to go to the third adjustment, but the adjustment is not applied, the system still skips the second adjustment and goes to the third. The client is upgrading from 9.0 to 9.2. This did not happen in the 9.0 environment.
- Create a Line Level Sales Price Adjustment Definition (P4071) named MIN59. On Additional Options Tab select the Min Adjustment radio button and set the Min/Max Rule to 1
- Create a second and third line level adjustment (SEC59 and THIRD59).
- Create an Adjustment Schedule (SKIPSCH) as follows
- Seq No. 10 MIN59 Skip To 30
- Seq No. 20 SEC59
- Seq No. 30 THIRD59
- Create a Price Adjustment Detail (P4072) record for All Customers/All Items for MIN59.
- Set From Level to Blank, Threshold UM to EA, Basis Code to 5, and Factor Value to 0.0001.
- Create a Price Adjustment Detail (P4072) record for All Customers/All Items for SEC59.
- Set From Level to 1, Threshold UM to EA, Basis Code to 1 (% of Base Price), and Factor Value to -40.
- Create a Price Adjustment Detail (P4072) record for All Customers/All Items for THIRD59.
- Use From Quantity 1, Threshold UM EA, Basis Code 5, Factor Value 0.
- Create a Sales Order for any Customer and Branch and populate the Adjustment Schedule in the Order Header.
- Enter an item that you know has a Base Price Setup.
- Go to Price History (P4074). The third adjustment was applied. The system skipped over the second adjustment even though the first adjustment was not applied because a base price exists.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |