E1: 32: Configured Sales Order Hold Does Not Put Transfer Component Work Order and Nested Component Work Orders Below on Hold (Doc ID 2267090.1)

Last updated on MAY 17, 2017

Applies to:

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

Symptoms

EnterpriseOne 9.1
When sales order was put on hold, component orders including Transfer Orders (ST) and Work Orders (WO) are not being put on hold. The only orders going on hold are the parent Sales Order (SO) and Parent Work Order (WO).

Configured setup:
Configured Parent A is manufactured with a work order (WO)
Configured Component B defined as a Transfer item (Transaction Type = 2 in P3293) and is manufactured with a WO.
Configured Component C is a child of Configured Component and is manufactured with a WO.

In the test, the following orders are created:
Configured Parent A - SO (B/P 1)
Configured Parent A - WO (B/P 1)
Configured Component B - ST (B/P 2)
Configured Component B - WO (B/P 2)
Configured Component B - OT (B/P 1)
Configured Component C - WO (B/P 2)

In this scenario, the parent WO and SO go on hold, but none of the component orders go on hold.

Note - The component ST seems to be the culprit. If you have the same scenario but no transfer at the component (meaning all orders are from the same B/P), all related work orders go on hold.

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