My Oracle Support Banner

Pick Confirm Items For Internal Requisitions Cause A Performance When Executed From API (Doc ID 2275122.1)

Last updated on FEBRUARY 15, 2019

Applies to:

Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.


On release 12.1.3 using an API to Pick Release:

Pick confirm via Public API fails for certain items on Internal Requisitions, and it is also causing a major performance.

APIs involved:
1) inv_move_order_pub.get_move_order
2) inv_pick_wave_pick_confirm_pub.pick_confirm
3) inv_trx_util_pub.insert_ser_trx
4) inv_serial_number_pub.updateserial


-- Pick confirm API is called from Middleware, 1500-2000 items are called in a single request.

-- Allocation API - Customer is using these APIs and seeing a performance issue.

-- What is working --
Most of the time, this works. Occurs for any random item. Happens for Internal Orders which have >500 quantities.

External Orders do not have any issue and follows a different cycle.
This occurs in Production. Have not been able to replicate the issue in Test environment.

Items are serializable.
The Serial Numbers are passed from the external system to the pick Confirm API as parameter.
This is a Pick Confirm Issue. When tried manually, the addition of IMEIs are very slow and sometimes disconnects. Have to be loaded in a batch of 200s.

Process transaction without errors.

We have tracked the process.

Calling API and start the process as follow

1. Once the Process is called from Middleware, it is all in Oracle.
2. The control does not go back to Middleware unless there is a success or a failure.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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