My Oracle Support Banner

E1: 32: Configured Child WO Is Not Rescheduled When Requested Date on Related SO Is Changed in P4210 Customer Service Inquiry (Doc ID 2852095.1)

Last updated on MAY 30, 2022

Applies to:

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

Symptoms

Issue occurs when changing an existing sales order line in Customer Service Inquiry (P4210) to a future requested date (two months into the future). Notice that the top level configured item WO start date is rescheduled two months into the future. But for the sub-assembly configured items under the top, the start date of the WOs is not rescheduled, but remains the original one. Check this in Manufacturing Work Order Processing (P48013).
It is important to have the WADL = 0 for the sub-assembly configured item on the P rule of the top parent configured item in Work With Assembly Inclusion Rules (P3293).

Steps:

  1. Create a multi level top configured item with a configured item as a component.
  2. Create an SO for the top configured parent with the requested date one month into the future. Save.
  3. Check the start date for both configured items.
  4. Change the sales order line to a future requested date (two months into the future). Save.
  5. Notice that the top level configured item WO start date is rescheduled two months into the future. But for the sub-assembly configured item under the top, the start date of the WO is not rescheduled, but remains the original one.

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.