E1: 32: P3210 Calculates Incorrect Cost With Expired Routing Steps
Last updated on DECEMBER 15, 2015
Applies to:JD Edwards EnterpriseOne Configurator - Version 9.0 to 9.0 [Release 9.0]
Information in this document applies to any platform.
Configured Item Revisions/P3210
If a configured item has R assembly inclusion rules that call an item with a routing that has both an expired and effective record with the same operation sequence (F3003), the P3210 will only evaluate the expired record and not correctly calculate the routing cost.
Steps to Duplicate
1. Create a configured item with a simple P assembly inclusion rule.
2. Create a manufactured item to be used for a routing.
3. Create a routing (P3003) for the item in step 2 with operation sequence 10 and two records for operation sequence 20. Make the first operation sequence 20 outside of the date effective range and the second operation sequence 20 within the date effective range.
4. Inquire on the work center revisions (P3006) for the records used in the routing; take the row exit to Rates and make sure that each has frozen standard work center rates.
5. Create an R assembly inclusion rule for the configured item where the operation sequence 20 is called for the routing item.
6. Create a sales order for the configured item (P4210).
7. When the system calls the P3210, click Validate Configuration.
8. While still in the P3210, go to Actions/Edit Item / Price / Cost.
9. Select the line the corresponds to operation sequence 20; note that the extended cost is blank.
10. After saving the sales order, re-inquire on it and note the unit and extended cost.
11. Run the R31410 over the related work order.
12. Re-inquire on the sales order and note the unit/extended costs now include the costs from routing step 20.
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