Manual Pack operation using WSH_CONTAINER_PUB.Container_Actions

Perform Manual Pack operation using the LPN created previously

In order to pack the delivery detail line item using the LPN created previously, we can use the public API “WSH_CONTAINER_PUB.Container_Actions”. We need to check the Maximum Weight and Volume of Previously Created LPN and might need to update if required. The Previously Created LPN can be found in Shipping Transactions form.

Once the LPN is created the LPN can be found in Delivery Details.

 Sample code to which will enable the packing action on the created LPN’s:

Once the script executes we can see the Item on the LPN in Shipping Transactions form at Detail Level.

Packing completed. LPN (AOAApiCT) is displayed in the Parent LPN field of the delivery detail of the Delivery Details which are assigned to this LPN.

Manual Pack creation of LPN’s

Manually Pack the Items by creating LPN’s using WSH_CONTAINER_PUB.create_containers:

To Manually Pack the items and Create the LPN or Container for the Particular Item we need to ensure that the Item attribute in Physical Attributes has container flag checked. Continue reading


Creating Move Order using API’s:

Creating Move Order using INV_PICK_WAVE_PICK_CONFIRM API’s:

Sample Script to Populate data into MTL_MATERIAL_TRANSACTIONS_TEMP and serial numbers temp tables: Continue reading

Issues releated to Back Order in Oracle OM

Any issue related to Back ordering will definitely fall 1 among these cases:

1. Check in Shipping Transaction Form, make sure the order still in “Ready to Release”.
2. There might be a lot of possibilities for this problem:

  • Order on hold
  • Do not have enough qty
  • Lot expired
  • Wrong reservation (even inventory have enough qty)
  • Inventory reserved for other orders.
  • Inventory picked up by other orders
  • Previously return to stock not done properly.

3. Case 1, check if the order is on hold. Check the order type in Shipping Transaction Form ® “Detail” ® “Source”.
4. There is another way to check the order type. That is go to WMS Control Board ® “Picking”.
5. Or go to OM Shipping View to see the order type.
6. Go to the correct “Sales Order View” instant accordingly by keying in the order# and order type.
7. Click on “Open Order” ® “Action” ® “Additional order info”.
8. Do the same for order level and line level.
9. Case 2 & 3, go to Material Workbench to check if the lot has expired or not having enough inventory for this order.
10. We can check if any lot is reserved for other order as well.
11. In Material Work Bench, go check for each lot in the physical locator by clicking on the “Attribute” button. (lot level reservation)
12. Alternatively, go to Shipping Transaction Form ® OM Shipping View, or go to “Lot Number” (Ctrl + L), click on Attribute column to check the SO reservation of the lot.
13. Compare the SO info with the order that are having problem.
14. Case 4, go “Reserve Supply” form (Ctrl + L) to check if the order is wrongly reserved.
15. Case 5, in the “Reserve Supply form, we can check if the qty is being picked up by other order as well. (order level reservation regardless of lot)
16. Also, can go to Material Workbench ® Availability, to check for the available to reserve.
17. Case 6, it might have high possibility the qty is taken up by order with different line, or other orders which have been auto launched.
18. If this is the case, must do backorder.
19. Go to Transact Move Order Form ® tab “Pick Wave” ® View/Update allocation ® Lot/Serial.
20. Click on the checkbox for order which need to be backordered, then go to Tool ® Back Order Line.
21. Case 7, ask the user if the order has done return to stock previously.
22. If yes, it might has high possibility that the return to stock not done properly.
23. Check the lot state, must be in “Resides in inventory”.
24. Check in Material Workbench to see if the lot is still packed with LPN or not.
25. Check also if the lot is in physical locator rather than logical locator.

Source for this post is from Oracle Forums.

Pick Release the Sales Order using WSH_DELIVERIES_PUB.Delivery_Action

Pick Release a Delivery using wsh_deliveries_pub.delivery_action API:

Once the Delivery Details are assigned to a Delivery the Next Step is to Pick Release the Delivery.

Sample code to Pick Release the Delivery:

Test the API:


  • (move order tables. Here request is generated to move item from Source (RM or FG) sub-inventory to staging sub-inventory)
  • MTL_MATERIAL_TRANSACTIONS_TEMP (link to above tables through MOVE_ORDER_HEADER_ID/LINE_ID, this table holds the record temporally)
  • MTL_SERIAL_NUMBERS_TEMP (if item is serial controlled at receipt then record goes in this table)
  • MTL_SERIAL_NUMBERS (enter value in GROUP_MARK_ID )

In shipping transaction form order status remains “Released to Warehouse” and all the material still remains in source sub-inventory. We need to do Move Order Transaction for this order. Till this no material transaction has been posted to MTL_MATERIAL_TRANSACTIONS.

Below post will give you the details about the pick release status
Instance: 11i or R12
Possible Values:
B: Backordered- Line failed to be allocated in Inventory
C: Shipped -Line has been shipped
D: Cancelled -Line is Cancelled
N: Not Ready for Release -Line is not ready to be released
R: Ready to Release: Line is ready to be released
S: Released to Warehouse: Line has been released to Inventory for processing
X: Not Applicable- Line is not applicable for Pick Release
Y: Staged- Line has been picked and staged by Inventory
Delivery line statuses in detail
Not Applicable (Code X)  
The delivery line can be invoiced but non-shippable, for example, a service line or a warranty line.
Not Ready for Release (Code N)
 The delivery line is not eligible for pick release. This happens when the order line is manually imported into Oracle Shipping Execution using the Import Delivery Line concurrent process or the corresponding order line has not reached the Awaiting Shipping workflow activity.
Ready for Release (Code R)
  The delivery line is eligible for pick release.  Occurs when the order line has reached the Awaiting Shipping workflow activity (it is booked, scheduled, and in Oracle Shipping Execution).
Submitted to Warehouse (Code S)
Pick release has processed the delivery line and has:
1.       Created move order headers and lines.
2.       Found available quantity and created inventory allocations.
3.       Not pick confirmed. If you are using auto-pick confirm, it changes release status to Staged. If you are not using auto-pick confirm and want to progress the delivery lines, navigate to Oracle Inventory Move Order Transaction window and perform manual pick confirm.
Staged (Code Y)
 The delivery line is pick confirmed; inventory is transferred from storage sub-inventory to staging sub-inventory.  It remains staged until ship confirm.
Backordered (Code B)
Some of the circumstances that can causes this status are listed below
a. Pick release has processed the delivery line and cannot find the entire quantity.  This typically occurs when the Oracle Inventory indicates that there is not enough material (either because there is not enough material or because the inventory balance is incorrect).
b. At ship confirm, you: Enter Shipped Quantity that is less than Original Requested Quantity Backorder the entire delivery quantity transfer a reservation to cycle count.
c. This typically occurs when the material that you want to ship:
1.       Has become unavailable, for example, damaged, between picking and shipping.
2.       Is available and you backorder material for specific business reasons. For example, all available material has been allocated to a specific customer when you find out additional supply for other orders will be delayed.
Shipped (Code C)
  The delivery line’s delivery is ship confirmed and posted as in-transit, OM Interface and Inventory Interface have processed, and the trip is closed.
Cancelled (Code D)

The order line that the delivery line supports is cancelled.