After long investigation and review it appeared from internal testing that this happened when they did not submit the order line_id to the process, So we had them implement that change to make sure this was targeted call to ATP API not just item in general but for a specific line_id

After this change was implemented - we see that most calls to API are not generating many calls to this SQL ID and it runs very very quicklyBut sometimes it does execute this same query many.many times

And when sending 140K lines to the API and you see 11+ million executions, then it takes excessive time.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms