E1: 31P: 32: Configured Work Order Related to Project Workbench - P31P001 is Always Using ZJDE0001 Version of Configured Item Revisions - P3210 Program (Doc ID 2938722.1)

Last updated on MARCH 31, 2023

Applies to:

Symptoms

When having a manufacturing shippable task created for a configured item and setting the ETO Workbench to use a certain P3210 version for validating the configuration of the configured item, the system always calls the ZJDE0001 version, which can trigger different results for the entire configuration.

The issue can be reproduced at will with the following steps:

1. IV – Define a version for P3210: e.g. TEST, a copy of ZJDE0001.
2. IV - Defined a P48013 version e.g. TEST that calls the P3210 version TEST.
3. IV – Define a version for P31P001 that calls the P3210 version TEST.
4. P48013 – Use the above P48013_TEST version to create a simple configured WO, Requested Quantity = 1. Notice that P3210 version TEST pops-up correctly and the desired configuration can be defined.
5. P48013 – Use the TEST version and take Row Exit > Configuration option.
6. P32983 - note the configuration defined above.
7. The same configuration details cand be checked by using P48013 > Form Exit > Config Item Specs > P3210 > Edit Item /Price / Cost action.
8. P31P001 – Add a Manufacturing shippable task for the same configured item in a new ETO Project or in an existing one.
9. P31P001 – Using ETO Workbench defined to call P3210_TEST version take option More Task Actions > Configurator WO and notice that the system opens the P3210_ZJDE0001 instead of P3210_TEST.
10. P3210_ZJDE0001 - Define the exact same configuration as above. Take Save and Close option in P31P001.

Changes

Cause

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