Shipping Execution - EBS (MOSC)

MOSC Banner

ITS failing with error ORA-20002: 3133: Activity instance 'SHIP_LINE' is not a notified activity for

edited Aug 8, 2018 5:05AM in Shipping Execution - EBS (MOSC) 3 commentsAnswered

I am testing a configured to order ATO model setup in our test environment. My current company has never used ATO models and its been several years since I last used them. When completing ship confirm on the configured item, the interface trip stop is failing with error ORA-20002: 3133: Activity instance 'SHIP_LINE' is not a notified activity for item 'OEOL/1063261'. The order line then reverts to Supply Eligible status, losing its reservation, but still has the delivery associated with it. This is happening on every order I create so I'm thinking its a setup issue.

Any ideas as to what setup I am missing? I am using the seeded Oracle workflows for order header and lines.

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