E1: 32: Extended Cost From Child X Rule Rounding Issue Causes Price Invalid Error in PO Receipts P4312
Last updated on JULY 01, 2016
Applies to:JD Edwards EnterpriseOne Configurator - Version 9.0 to 9.0 [Release 9.0]
Information in this document applies to any platform.
When a configured parent has a configured component that creates a purchase order (as defined by the Transaction Type 4), the rounding logic executed by configurator is not the same as the rounding logic executed in the Purchase Order. This is causing the purchase order to not being able to be received as an 'Extended Price Not Found' error.
After further testing, the following was determined:
When calculating the Unit Cost for a configured item based on an X Rule value, the system rounds it differently in sales than in purchasing.The problem this causes is that, if a configured component has a purchase order generated at the time of the parent sales order, the component cost is calculated correctly but the Extended Cost (which is not seen) is rounded at a certain value. When attempting to receive the component item in PO Receipts (P4312), the system returns an ‘Extended Price Invalid’ error as the value is off by a penny. If you clear the Extended Cost on the purchase order detail line, the system recalculates the extended Cost to another value that is correct in the purchasing side of the calculation.
Note 1 – If you create a stand-alone purchase order for the configured component item, no error occurs as the Extended Cost is correct.
Note 2 – If you create a stand-alone sales order for the configured component item, the Extended Cost is calculated at the value that is incorrect and different than from purchasing.
Note 3 – If you clear the Extended Cost field in the stand-alone sales order, the system will recalculate the value to what matches the stand-alone purchase order Extended Cost calculation.
Note 4 – The same “incorrect” value is calculated regardless of how the X Rule is defined. If the test is done with a purchased item’s (Stock Type P) with a P4105 cost at the same cost of the X Rule calculated value, the system calculates it differently and consistent with purchasing.
To demonstrate the issue and how it affects the user down-stream, this is a multi-level configured test.
1. For the configured parent item (Stock Type C) in the Item Master (P4101), define the Configurator Costing Method (CMETH) as ‘3’ to cost by X Rules. Note – The parent configured item dictates the CMETH for all components regardless of how they have the CMETH defined.
2. In the Configured Item Segment Revisions (P3291), define a segment for the parent configured item.
3. In the Assembly Inclusion Rule Revisions (P3293), define an unconditional P Rule to return a configured (Stock Type C) component. Ensure that the Transaction Type is defined as ‘4’ to create a purchase order for the component. Although it is not necessary for the test, populate the Write Attached Detail Line as a ‘1.’
4. In the Configured Item Segment Revisions (P3291), define a numeric Required Segment for the parent configured item.
5. In the Assembly Inclusion Rule Revisions (P3293), define an unconditional X Rule to calculate a cost. Ensure that the Cost field is populated with a 1, and the Derived Calculation is defined with a value of S20*.632. Also note that the Price Rollup field (alias PRU) must be defined as ‘1’ to roll the cost to the item.
6. Before entering a Sales Order (via P4210), note the value of Processing Option 14 of the Versions tab to identify the version of the Configured Item Revisions (P3210) being used.
7. Go to Interactive Versions and check the Processing Options of the called version of P3210. On the Versions tab, ensure that there is a value defined in the Purchase Order Version Processing Option. If this is left blank, the system will NOT generate a purchase order.
8. Create a sales order for the configured parent at a quantity of 24 to demonstrate the issue.
9. When the Configured Item Revisions form (P3210) is prompted, configure both items. To demonstrate the problem, for the component item, enter an answer of 76.667. Click the Add to Order button.
10. Save the sales order an reinquire on it. Note the Unit Cost of the component item is $48,4535. Per the design of the software, the Extended Cost of the component item is blank as this item is not being shipped on the sales order.
11. From the Sales Order Detail, take the Row exit to the Related Configured Orders Form (P3201) and click the Show Details? box. Note the purchase order number that has been generated for the configured component item.
12. Go to Purchase Order Receipts (P4312) and inquire on the order. Note the Unit Cost of $48.4535 and the Extended Cost of $1,162.89. Populate the Lot Number field and the Lot Expiration Date, then click Save.
13. The system returns an Item Location Record Not Found warning which is correct. However, an ‘Extended Price Invalid’ hard error is returned. The Error ID is 0252.
14. If you clear the Extended Price, the system will recalculate it at the value of $1,162.88 and let you process the receipt without problem.
15. If you create a purchase order for the component item by itself in P4310 with the same quantity of 24 and configure the item with the Required Segment value of 76.66, the system calculates the Extended Cost as $1,162.88.
16. To further demonstrate that the issue originates from the sales order side, enter a sales order for the component configured item at a quantity of 24, and configure it with the value of the Required Segment as 76.667.
17. The system calculates the Extended Cost as $1,162.89.
18. Here’s the weird part…If you clear out the Extended Cost or edit the line in other ways, the system recalculates the value from $1,162.89 to $1,162.88.
19. Tried a couple more tests. The first was to change the X Rule Derived Calculation field to not reference the Segment Value but to put the value of 76.667*.632 directly into the Derived Calculation.
20. Created a sales order with the same results as the Extended Cost is $1,162.89 and can be cleared and recalculated as $1,162.88.
21. One last test with the X Rule as this time the calculated value of 76.667*.632 (48.453544) was input directly into the Derived Calculation field. Again, created the sales order w/ a quantity of 24 and again, the Extended Cost is $1,162.89 and can be cleared and recalculated as $1,162.88.
22. One last test to check if the issue is with sales or configurator. For a purchased component (Stock Type P) Sales/Inventory Unit Cost is defined as $48.453544 in P4105.
23. A sales order was created with a quantity of 24 for the purchased item. The Extended Cost was calculated as $1,162.88 which is different than what configurator is calculating as $1,162.89. Subsequently, with a discrete item, this is not a problem.
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