E1: 32: No Child Configured Work Orders generated by Interbranch Sales Order (Doc ID 1613734.1)

Last updated on DECEMBER 16, 2015

Applies to:

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

Symptoms

When adding a new interbranch Sales Order (P4210) for a configuration that conditionally triggers a new child work order via a P Assembly Inclusion Rule (P3293), the required child configured Work Order is created, but so is another WO for the Child configured item.

First child WO  has the correct details (Related line 2,001, Parent WO, Start Date = today)
Second child WO is created incorrectly and has blank start date, blank related line number and no parent WO number.

STEPS:
======
1. Create 2 configured items.
2. Link child to parent via conditional P AIR.
3. Raise SO for parent with segments set to call child item.
4. Save.
5. Review the configuration and Child WO + additional WO.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms