IN_FUL_BCT Sets Demand Line To Shipped When Xml Has Negative Qty and Picks& Confirmes a Demand Line with Partial Qty although Partial QTY is Not Allowed

(Doc ID 2358249.1)

Last updated on FEBRUARY 14, 2018

Applies to:

PeopleSoft Enterprise SCM Inventory - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Interfaces and Integrations


IN_FUL_BCT sets demand line to shipped when xml has negative quantity although it should not.

Issue 1: When receiving the xml file from the warehouse with the negative qty, the IN_FUL_BCT process does generate an error based on the fact that a negative QTY is not allowed, or that the QTY does not match the requested QTY (as we do not allow partials). It seems the
process ignores the fact that the QTY is negative and just confirms the picking. (Replication file attached)

IN_FUL_BCT sets demand line to confirmed for partial Qty, when Partial Qty is not allowed.

Issue2: "We have an interface with our warehouse where we release orders to them via the SHIPPING_ORDER_RELEASE and receive back the INVENTORY_SHIPPING message. When we release an order with a line for which we do not allow partial QTYS and the return message only has a partial QTY for that line, the IN_FUL_BCT generates an error as expected: "Partial Quantities cannot be shipped. Keys: ERGON OM NTENL EU00433154 1 1 T1000-25740 2"
However the demand line is completely picked and confirmed and added to the ship ID, which is not what we would expect to happen. We would expect the transaction to error and not do any demand processing."

Scenario/test case:

a)"We are able to reserve and release the full QTY since the stock exists in PS, the warehouse just returns a QTY that is less than released.
b) Online we do see a message when trying to confirm less (You cannot pick less than allocated for this schedule line. (11100,443) )
c) But the inventory shipping message does pick and confirm the full QTY, but then doesn't ship it, so the order remains confirmed.
d) It shouldn't do anything and just set the transaction to error. Now it's setting the transaction to error but still confirms the pick line(s)."

 

 

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