Pick Load and Pick Drop are one of the most widely used processes by Warehouse users/customers. These processes are an integral part of Outbound and Warehousing transactions. To help warehouse customers, these processes would be exposed as Public APIs for use and are made available in the Oracle Integration Repository.

A. Public API for Pick load – WMS_TASK_MGMT_PUB.load_task

The API can be called in PLSQL context to Load. It should be called with one task at a time. The Input is in the form of MMTT ID (MTL_MATERIAL_TRANSACTIONS_TEMP table) or MMTT Rec. It will provide the details of the Loaded task. In case the task processing results in error or validations fail, error messages to be sent back.

Please note following important notes about expected functionality of the API and the limitations.

  • 1. The API does not have any visibility to a Pick Load Page Template here the same would not be honored.
  • 2. Pick from packed Onhand, Loose unhand, LPN Picked AS IS will be supported.
  • 3. The employee/user against whom task Load/completion would be reported needs to be passed to the API.
  • 4. Dispatching of tasks under the same Pick Slip will not work and does not serve any purpose as well.
  • 5. The API will not provide any functionality to skip a task, however if the task exists as skipped already, it will not be processed.
  • 6. The API should be able to process the tasks involving different Pick Partial exception combinations such as Pick Partial + change locator exception + curtail pick, Pick Partial + Pick Later, the same way it is on MSCA UI. For cases with Exception, each and every exception, pertaining to this task ONLY should be passed in as parameter which can be a collection.
  • 7. Tasks with status of dispatched will not be supported.
  • 8. Move Order Transfers, Sales Order Pick, Internal Sales Order Pick, Backflush Transfers, WIP Component Issue are supported picks for the API.
  • 9. Pick Load for Advanced Catch Weight items/orders would be supported.
  • 10. The functionality to support selective backorder of tasks based on raised exceptions would be supported provided an input is passed to the API.
  • 11. API should be able to generate Labels for the flow related to the task being loaded/dropped.
  • 12. For Split Tasks, since the original temp_id is maintained and can be continued to be worked upon, users can send the same temp Id again to complete or end the task.
  • 13. Lot Substitution would be supported, provided Exception reason is passed in.


B. Public API for Pick drop – WMS_TASK_MGMT_PUB.pick_drop

The API can be called in PLSQL context. It should be called for one LPN at a time. The Input is loaded LPN ID/LPN Name.

Please note following important notes about expected functionality of the API and the limitations.

  • 1. This API should be configured to accept 1 LPN at a time and be able to drop the same.
  • 2. Drop LPN is to be provided up-front by the user.
  • 3. Change in Drop locator is supported provided user has passed in an Audit reason.
  • 4. Any LPN which will be reconsolidated during drop will not be supported.
  • 5. Label Printing Support.

Review (Doc ID 2984590.1) the more information on the API Signatures and links for sample calls of these APIs.