My Oracle Support Banner

E1: 32: Requested Date (DRQJ) Sales Order Header (P4210) Change on Split Sales Order Clears Configurator Master Table (F3201) Records (Doc ID 2889558.1)

Last updated on MARCH 08, 2023

Applies to:

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

Symptoms

If a change to the Sales Order header Requested Date updates multiple split lines on the order detail Requested Dates, the system will continuously call the P3210 until eventually the following error will display:

Sales Order Entry - Transactional Warning Message

This application did not originate the transaction. Therefore,
only the original application will allow committing the change in
the configuration.

This will cause the system to delete related records in the Configurator Master Table (F3201). This will cause a problem when attempting to complete (P31114) the Work Order or confirm shipments (P4205). The user will be presented with the following error:

Error ID 013Z - Configuration must be selected

Steps
1. Create a Configured item (P4101, P41026) with Configured Item Segments (P3291) and a simple P Assembly Inclusion Rule (P3293)
2. Create five Sales Order detail lines for the Configured item, each with a quantity of 10.
3. Review the F3210, F3211 and F3215; note the configured string and unique configuration ID values.
4. Run the R31410 over the related Work Orders.
5. Do a full completion (P31114) of the first Work Order (10 EA) and partial completions of the second and third Work Order (5 EA)
6. Review the P3201 again for the related orders; note that there are new Configuration IDs for the split lines.
7. In the Sales Order application, make sure the option "Update Header to Detail" is active.
8. Make a change to the Sales Order requested date in the header and click OK.
9. The system will call the Sales Order detail with each line’s Requested Date changed. Click OK and notice that the system calls the P3210 multiple times.
10. After clicking Add to Order in P3210 multiple times, the system will display the following error:
Sales Order Entry - Transactional Warning Message

This application did not originate the transaction. Therefore,
only the original application will allow committing the change in
the configuration.

11. After saving the Sales Order, review the F3201 and notice that the system deleted records linked to one of the split Sales Order detail line.

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.