My Oracle Support Banner

E1: 32: Price Rollup Problem in Configured Sales Order (P4210/P3210) When Using Transaction Type 2 and Price Should Come from the Components (Doc ID 2943321.1)

Last updated on AUGUST 21, 2023

Applies to:

JD Edwards EnterpriseOne Configurator - Version 9.2 and later
Information in this document applies to any platform.


When a configured parent with Kit/Configurator Pricing Method 1 has a P rule configured component with Transfer Type 2, the parent price will not include the F4106 price amount from the lower level purchased item (below the configured child). It will only include the X price rule from the configured component.


1. In the Item Master (P4101), create a configured parent, configured child and a purchased item. Make sure the configured parent has Kit/Configurator Pricing Method = 1.
2. In the Item Branch (P41026), add the configured parent and configured child to branch M30. Add the configured child and purchased item to branch M10.
3. Create simple Configured Item Segments (P3291) for the configured child in branch M10.
4. Add the purchased item to the configured child’s P Assembly Inclusion Rule (P3293).
5. Create a Base Price (P4106) for the lower level purchased item under the configured child’s P rule.
6. Add an X Price Rule with Price Rollup = 1 (P3293) to the configured child.
7. Create simple Configured Item Segments (P3291) for the configured parent.
8. Create a P Assembly Inclusion Rule (P3293) for the parent that calls the configured child from Branch M10 and Transaction Type 2.
9. Create a Sales Order (P4210) for the configured parent.
10. When the P3210 is called, enter all segment answers and click Validate Configuration. Note the Price and Cost.
11. Select Edit Item / Price / Cost in the Actions field and click on the arrow. Notice that the configured parent’s price only has the X price rule from the configured child. The system does not include the price of the configured child’s component (F4106).
12. Change the configured parent’s P rule (calling the configured child) to Transaction Type 0.
13. Enter a new Sales Order for the configured parent and configure in P3210. Notice that the parent price now includes the price from the configured child’s P rule component as well as the X price rule.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.