With Contributing Author:  Sibghatullah Hussaini Syed

 

Public APIs help customers extend their custom functionalities and at the same time, use the oracle provided/supported functionality.  Public APIs often provide a ‘Plug and Play’ experience where customers can enhance/extend their business processes by building UIs, as per their need or use any third-party application, and then complete the transaction in Oracle, or simply bring any extra validation to the process.  In all such cases public APIs are helpful to build the logic.

The following processes are widely used in warehouse management therefore the need to expose these processes as public APIs.  Customers can now use these to ‘Plug and Play’ in their processes as described above.

  • 1. Pick Load
  • 2. Pick Drop
  • 3. LPN load
  • 4. LPN Unload

All of these processes are an integral part of Outbound and Warehousing transactions.

 

Consider the below case where Oracle Warehouse Management enables you to ship confirm material for a sales order line without having to pick release or pick confirm the delivery lines.

Pick release is the process to select the correct material allocated for a particular sales order, based on any user defined rules. However, in environments where the product is built to customer order, in a just-in-time mode, this decision is already made by the production schedule.  The pick release is redundant and unnecessary.  In such manufacturing modes, the material is completed off the assembly line and ready to be loaded onto trucks for shipment. The assumption that forms the premise of pick release is that material is on-hand in a warehouse storage location when the warehouse is ready to begin processing for shipment. This does not hold true for these scenarios. The additional step to pick material and deliver it to the staging lane is unnecessary because the material is brought to an outbound preparation area directly from manufacturing.

 

The Direct Ship MSCA UI provides a simple way to load a fully reserved LPN and does not ask the user for demand details.  A detailed reservation can be made at the LPN level, either manually, or via an LPN based completion of a job that is reserved to a sales order.  You can reserve an entire LPN against the sales order demand.

When you are using direct ship with a reserved LPN, rather than re-entering the sales order data, the system can automatically derive the sales order number and sales order lines tied to the LPN. You only need to scan the LPN, enter any details about the delivery or freight costs, and the shipment is complete.

The public API for load LPN aims at providing similar experience. This API could be invoked from custom UIs or custom applications.

 

There are 4 new public APIs introduced in release 12.2.13 for these functionalities. Please refer following notes for details on these new public APIs as well as sample codes on how to use them.

12.2.13: How To Perform Direct Ship LPN Load and Unload Using New APIs From WMS_SHIPPING_TRANSACTION_PUB? (Doc ID 2984300.1)

12.2.13: How To Do Pick Load And Pick Drop For LPNs In An WMS Enabled Organization Using New APIs From WMS_TASK_MGMT_PUB? (Doc ID 2984590.1)