E1: 45: ORDER DETAIL ADVANCED PREF BASED ON PROMISED RSDJ INCONSISTENT W/ BASE PC1 PREF (Doc ID 2018407.1)

Last updated on NOVEMBER 11, 2015

Applies to:

JD Edwards EnterpriseOne Advanced Pricing - Sales - Version 9.0 to 9.0 [Release 9.0]
Information in this document applies to any platform.

Symptoms

EnterpriseOne 9.0

Advanced Order Detail Preferences uses the Promised Delivery (alias RSDJ ) on the sales order against the Effective/Expiration effectivity dates to determine what preference should be applied. In this example, the Advanced Preference was defined to return a value to the Price Code 1 field (alias UPC1). This is inconsistent with the basic Price Code 1 Preference (Preference 11) which appears to use Requested Date field (alias DRQJ). 

The system should be consistent and use the same date for both basic and advanced pricing order detail preferences.

 

Steps to Duplicate:
1.  Create an Advanced Preference record via P4071. The Advanced Preference Type is 02 (Order Detail Defaults).

2.  Define your hierarchy as desired in P40073.

3.  Via P4070, create an Advanced Preference Schedule and associate the Advanced Preference to it.

4.  In the Preference Schedule Detail Revisions (P4072), define records for the same Item Number/Customer Number combination each with two different effective/expired date ranges. In this example, the first record has an Effective Date of 5/1/2015 and an Expired Date of 8/31/2015. The second record has an Effective Date of 9/1/2015 and an Expired Date of 12/31/2015.

5. Take the Pref Details Row exit and create the preference values. For the first record, populate the Price Code 1 field (PC1) with a specific value (in this example AA).

6.  For the second record, populate the PC1 field with a specific value (in this example BB).

7.  In the Billing Information of the Customer Billing Instructions (P03013), populate the Adjustment Schedule field with the newly created Preference Schedule.

8.  Now time to create a sales order via Sales Order Entry (P4210). Processing Option 1 of the Preference tab of P4210 is defined as a ‘1’ to activate preference profiles while Processing Option 3 is defined with the desired preference schedule.  

9.  Processing Option 6 of the Versions tab of P4210 is left blank.

10. Via P4210, create a sales order with three detail lines with the desired item/customer to illustrate the reported issue.  Ensure that the Requested Date, Scheduled Pick, Promised Delivery, and PC1 fields are visible in your form. Create three sales details lines. The first with the Requested Date, Scheduled Pick, and Promised Delivery fields defined as 8/31/2015. Note the PC1 field is correctly populated with the value AA. The second detail line is defined with the Requested Date, Scheduled Pick, and Promised Delivery fields as 9/1/2015 and the PC1 field is correctly populated with the value BB. Finally, the third detail line is defined with the Requested Date and Scheduled Pick fields as 8/31/2015 while the Promised Delivery date is defined as 9/1/15. Note the PC1 field is populated with the value BB which seems to be incorrect as the system is populating this field based on the Promised Delivery date instead of the Requested Date.

11. From the Customer Service Inquiry, we see that the correct Preference Schedule  (with Preference Adjustment) has been correctly returned in P40741.

12. Next run the same test but with basic/standard preferences. From menu G4231, inquire on Preference Type 11 in the Preference Master (P40070).

13. Create two records for the same Item Number/Customer Number combination. Again, they each have two different effective/expired date ranges. In this example, the first record has an Effective Date of 5/1/2015 and an Expired Date of 8/31/2015 with the Price Code 1 field defined as AA while the second record has an Effective Date of 9/1/2015 and an Expired Date of 12/31/2015 with the Price Code 1 field defined as BB.

14. Billing Information of the Customer Billing Instructions is left blank so that we do not invoke the Preference Schedule.

15. Behind Sales Order Entry (P4210), Processing Option 1 of the Preferences is defined as a ‘1’ to activate preference profiles, but Processing Option 3 is left blank.

16. A specific version of Preference Profiles (R40400) is called via Processing Option 6 of the Versions tab of P4210.

17. In the called version of R40400, the Price Code 1 Processing Option of the Process Ctl 2 field of R40400 is populated with a ‘1’ to activate this preference.  

18. Now run the same test in Sales Order Entry. Create three sales details lines. The first with the Requested Date, Scheduled Pick, and Promised Delivery fields defined as 8/31/2015. Note the PC1 field is correctly populated with the value AA. The second detail line is defined with the Requested Date (alias DRQJ), Scheduled Pick (alias PDDJ), and Promised Delivery (alias RSDJ) fields as 9/1/2015 and the PC1 field is correctly populated with the value BB. Finally, the third detail line is defined with the Requested Date and Scheduled Pick fields as 8/31/2015 while the Promised Delivery date is defined as 9/1/15. Note the PC1 field is populated with the value AA which is expected (but different than the Advanced Preference Test) as it appears that the system is validating against the Requested Date.

19. Note that the Preference History is correctly showing no records as we are not utilizing advanced preferences.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms