E1: 32: P Configured Table Rules Using Blank Branch Plant in Rules Setup is not Using the Correct Component Branch for the Sales Order (Doc ID 2737629.1)

Last updated on FEBRUARY 26, 2023

Applies to:

Symptoms

The component branch is not being applied correctly in the P3210 for new sales order when P table rules are setup using a blank branch plant. Table rule definition, cross reference and table values are all setup with a blank branch plant in the header. The P assembly inclusion rule has a different branch in the header then the component branch in the detail. With this setup the system is not selecting the component branch when creating the sales order

EXPECTED BEHAVIOR

To have the system select the correct component branch for the configured sales order



STEPS TO DUPLICATE

1. Create a configured parent item in two branches
2. Create a component item in two branches
3. Create a simple required configured item segment with a default
4. Create a table name in UDC 32/TN
5. Setup a P table rule 1x1 definition with a blank branch plant
6. Setup a P table rule cross reference with a blank branch plant
7. Setup P configured table rules value with a blank branch plant
8. Setup an unconditional P assembly inclusion rule with a parent branch different then the detail component branch
9. Enter a sales order for the parent
10. Notice in the P3210 for Edit Item/Price/Cost screen the component branch is incorrect

Cause

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