Order Management - EBS (MOSC)

MOSC Banner

Best practices on backlog order workbench

edited May 21, 2018 5:00AM in Order Management - EBS (MOSC) 1 commentAnswered

We're on Oracle eBS R12.1.3 and we've implemented Global Order Promising, including allocated ATP (segregated stock based on demand classes). We run the backlog order workbench on a daily basis and at the same time we book and schedule sales orders, receive sales orders through EDI, receive sales orders through iStore, etcetera. In the last couple of months, we see an increasing number of issues where the backlog order workbench gets into a deadlock with error "ORA-00060: deadlock detected while waiting for resource in Package oe_line_util Procedure Update_Row".

Be aware that we've been running the backlog order workbench for many, many years. We started in R11i where we never had these issues. This issue really started in R12.1.3 and has increased over time.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

EBS Order Mgmt Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center