E1: 42W: After Fulfillment Release (R4277703) Released an Order Line, There was No Inventory Available and Pick Slip (R42520) Put Order Line on Backorder (Doc ID 3004801.1)

Last updated on FEBRUARY 21, 2024

Applies to:

Symptoms

A Fulfillment Management Sales Order XXXXXX Line 167.700 for 2 Units of Item YYYYY was released from Fulfillment on December 21, 2023 and went to Status 50. At the time the order line was released from Fulfillment the Item Ledger shows there were 8 units On-Hand in Inventory. On December 23, 2023, all the 8 units were hard committed to other line numbers (167.500, 167.501, 167.600 and 167.601) for the same item on the same order and shipped out and invoiced to the customer. On January 2, 2024 the Shipment for Line 167.700 was Consolidated Manually and Approved and then Pick Slip was run to hard commit the inventory, but there was no inventory left. All the inventory has already been shipped 12/23/2023 under the other line numbers.

Steps to Duplicate:

1. Order Line 167.700 was released from Fulfillment in 12/21/2023 and went to Fulfillment Status 50.
2. There were 8 units On-Hand on 12/21/2023 which could have been be hard committed that day.
3. The Item Ledger (P4111) and Sales Ledger (F42199) shows there were 9 units shipped out 12/23/2023 on the same Sales Order XXXXXX but on different lines that needed the same item:
   1. Order XXXXXX, Line 167.500 received 1 unit
   2. Order XXXXXX, Line 167.501 received 1 unit
   3. Order XXXXXX, Line 167.600 received 4 units
   4. Order XXXXXX, Line 167.601 received 3 units
4. Client did not run Pick Slip (R42520) to Hard Commit the Order line 167.700 until January 2, 2024.
   1. When Order XXXXXX, Line 167.500 was hard committed on January 2, 2024, all the inventory had been shipped, so the order line went on backorder.

Cause

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