Shipping Execution - EBS (MOSC)

MOSC Banner

Interface Trip Stop - Single Threaded?

edited Jun 24, 2013 2:47AM in Shipping Execution - EBS (MOSC) 1 commentAnswered ✓
We have a 3rd party shipping system that ships our product.  We then interface and ship in Oracle via API's.  After ship confirm, the interface trip stop kicks off.  For some orders, the inventory interface step is not working properly.  The status on the delivery then sits on Next Step Run Interfaces.  From the logs, looks like the inventory is getting locked when multiple interface trip stops are running at one time.  Do the Interface Trip Stop jobs need to be set to only run one at a time. (incompatibility in the concurrent request setup?)

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 Shipping 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