Orphan Move Orders From Process Manufacturing: Move Orders Not Closed Even If Process Batch Is Cancelled (Doc ID 2096764.1)

Last updated on DECEMBER 10, 2024

Applies to:

Symptoms

Find orphan move orders for closed/canceled process batches.

Expect move orders to close when the related job / process batch are closed.

Background
When a process batch is created, a move order is created automatically.
The move orders are created in the inventory move order header table (MTL_TXN_REQUEST_HEADERS) and lines table (MTL_TXN_REQUEST_LINES) to support process manufacturing (OPM).
When the batch is closed, move order are not getting closed resulting in orphan move orders.

The issue can be misleading as users cannot query the move orders in the standard transact move order form because these are process manufacturing (OPM).
The move order shows that it supports Work in Process (WIP) with a transaction source type id of 5 / WIP.
The WIP entity type is 10/Process Batch (WIP_ENTITIES.ENTITY_TYPE = 10).
Although the batch creates a WIP Entity record, it does not create a WIP Discrete Job (WIP_DISCRETE_JOBS) record.

Steps
1. Create a process batch
2. The move order is created automatically
3. Close the batch
4. The move order is not closed.

Business Impact
As a result of this issue, you could fail to inactivate items because the open move orders preventing changing the item to inactive with an error like this:

Cause

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