My Oracle Support Banner

Why Do Non-Reservable Items Default The Subinventory From The Item Attribute Rather Than The One On The Release Rule? (Doc ID 837723.1)

Last updated on AUGUST 15, 2022

Applies to:

Oracle Shipping Execution - Version 12.0.4 and later
Information in this document applies to any platform.


Why do non-reservable items default the subinventory from the item attribute rather than the one on the release rule? When using a combination of reservable and non-reservable items on a sales order, pick confirmation allocates the reservable items from the subinventory defined in the release rule, however, non-reservable items pick up the subinventory from the item attribute definition.


From Note 415829.1
WSHPSGL - Some Items Go to Staged/Pick Confirmed Status Even When the Auto Pick Confirm is Set to No

This is the expected behaviour for "non reservable" items. Please see development update regarding the behaviour on these item setup in bug 4216539 - PICKING OF NON RESERVABLE ITEMS IN MSCA:

When allocating a pick wave more order for a non-reservable
item, we do not create any allocations and close the move
order line and update the WDD to stage.


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.