My Oracle Support Banner

E1: 32: Multiple Validations Clear Required Segment UDC Values In P3210 (Doc ID 1987739.1)

Last updated on MARCH 12, 2021

Applies to:

JD Edwards EnterpriseOne Configurator - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Symptoms

EnterpriseOne 9.1
When clicking the Validate Configuration at least six times during one session in the Configured Item Revisions (P3210), then accepting the configuration and then going back into the P3210 (via the Kit/Configurator Row exit), the system clears and "grays out" Required Segments associated to a UDC. No errors occur and the system allows you to click the Add to Order button without problem. Setup seems to require a multi-level setup in which a Required Segment must exist before a Calculated Setup. The issue can also occur by going into the P3210, validating the configuration and clicking the Add to Order button and then entering back into P3210 and following the same steps six times. The system clears and grays out the Required Segment Values to that the user cannot change the answer. However, if you ultimately click Add to Order in P3210, then click the Save icon in P4210, the system retains the "grayed out" values in the Configurator Segment Detail File - F3211. Subsequently, the configurator data in F3211 appears to fine although the P3210 form is corrupt and does not allow changes to the segments until the order is saved first before reinquiring on the configuration.

Another method to duplicate the issue is to Validate the Configuration in P3210, then click Add to Order, then from the SO Detail before saving the sales order, take the Kit/Configurator row exit and go in perform the same process 5-6 times.


STEPS TO DUPLICATE:
1. For a configured item, define a Required Segment associated to a UDC in the Configured Item Segments Revisions (P3291).
2. In the Assembly Inclusion Rule Revisions (P3293), create an unconditional P Assembly Inclusion Rule (AIR) to return a configured component (Stock Type C) to the configuration.
3. For the configured component, in P3291, define three segments in this specific order – Calculated Segment, Required Segment associated to a UDC, and another Calculated Segment.
4. In P3293, define an unconditional P Rule to return a purchased component.
5. For the configured component, in P3293, define two unconditional Calculated (C) AIRs for the Calculated Segments.

Process 1:
6. Enter a sales order (via P4210) for the configured item.
7. The system prompts the Configured Item Revisions (P3210) and validates the configuration upon entry into the form. In this example, the configuration is valid upon entry into the form. Click the Validate Configuration button 7 times before clicking the Add to Order button (which takes you back to the sales order detail).
8. Before accepting the sales order, take the Kits/Configurator Row exit to get back to the configuration (P3210).
9. Upon entry into P3210, note that both Required Segments associated to UDC Tables have been cleared with the –Select One—default displaying. However, there is no way to answer the segments and the system indicates that the configuration is valid and allows you to click the Add to Order button.
10. After causing the “problem” to appear by clearing out the segment value, click the Save button in the sales order detail to accept the order.
11. In the Configurator Master Table (F3201), inquire on the Order Number and Note the Configuration ID (CFGID).
12. In the Configurator Segment Detail File (F3211), Segment 10 is correctly defined with the value BLU so the data does NOT appear to be corrupt.
13. Now, go back and check the configuration from the sales order by taking the Kits/Configurator Row exit.
14. Everything appears to be valid IN P3210 and confirms what is seen in the F3211.

Steps to Duplicate – Process 2:
6. Enter a sales order (via P4210) for the configured item.
7. The system prompts the Configured Item Revisions (P3210) and validates the configuration upon entry into the form. In this example, the configuration is valid upon entry into the form. Click Add to Order which takes you back to the sales order detail (First validation of the configured item).
8. Before accepting the sales order, take the Kits/Configurator Row exit to get back to the configuration (P3210).
9. Typically you would make a change upon reentry into P3210 but this issue can be demonstrated by simply clicking the Add to Order button (2nd validation of the configured item).
10. Once back in the sales order detail, take the Kits/Configurator Row exit again to prompt the P3210 form.
11. Click the Add to Order button to accept the configuration and get back to the sales order detail (third configuration).
12. from the sales order detail, take the Kits/Configurator Row exit again to prompt the P3210 form.
13. Click the Add to Order button to accept the configuration and get back to the sales order detail (fourth configuration).
14. Again, from the sales order detail, take the Kits/Configurator Row exit again to prompt the P3210 form.
15. Click the Add to Order button to accept the configuration and get back to the sales order detail (fifth configuration).
16. Again, from the sales order detail, take the Kits/Configurator Row exit again to prompt the P3210 form.
17. Click the Add to Order button to accept the configuration and get back to the sales order detail (sixth configuration).
18. Finally, upon the seventh entry into the P3210 form, the seventh validation causes the parent segment (Segment 10) to be cleared from the configuration. The system is “graying out” the segment and does not allow the user to choose a selection from the UDC. However, the system indicates that that this is a “Valid Configuration” and allows you to click the Add to Order button.
19. After causing the “problem” to appear by clearing out the segment value, click the Save button in the sales order detail to accept the order.
20. In the Configurator Master Table (F3201), inquire on the Order Number and Note the Configuration ID (CFGID).
21. In the Configurator Segment Detail File (F3211), Segment 10 is correctly defined with the value BLU so the data does NOT appear to be corrupt.
22. Now, go back and check the configuration from the sales order by taking the Kits/Configurator Row exit.
23. Everything appears to be valid IN P3210 and confirms what is seen in the F3211.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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