My Oracle Support Banner

Extra Component Quantity Allocated To A Job - Discrete Job Component Pick Release Does Not Consider Over Picked Quantity (Doc ID 2496317.1)

Last updated on FEBRUARY 10, 2021

Applies to:

Oracle Work in Process - Version 12.2.7 and later
Information in this document applies to any platform.



The Discrete Job Component Pick Release doesn't consider over picked quantities

Discrete Job: DJ111
Component Required Quantity: 12180

Component Pick Release creates 3 move orders:

A Move Order for 1015 has been over picked (QUANTITY_DELIVERED 5000).
Then the application backordered line for 9165 and submitted the Component Pick Release again.
Thew application still creates a move order for 9165.  It should create a move order for 5180 = 9165 - 3985.

Inventory Organization is WMS enabled.


Would expect the new move order to be created for less, after the first MO was overpicked.


Discrete Jobs > Discrete Jobs

The initial job quantity is 11,000
The component required quantity is 11,165
The component pick release creates a move order and task for 11,165

Then I change WO quantity into 12,000:
The component required quantity now is 12,180
T component pick release creates another move order and task for 1015 (12,180-11,165)

Then I perform the second task first, and enter 5000 (overpick qty is 3,985)

Now there are 2 tasks for the Discrete Job
One Completed for 5000 and one Pending for 11,165.

Backorder Pending move order
The Discrete Job Component Pick Release (SRS) now creates a new move order and task still
for 11165

Customer expects it should create only for the difference: 12180 – 5000 = 7180


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

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