Shipping Execution - EBS (MOSC)

MOSC Banner

Error when running Interface Trip Stop

edited May 20, 2012 6:50PM in Shipping Execution - EBS (MOSC) 3 commentsAnswered
I received the following error when running the Interface Trip Stop:

InterfaceTripStop: processing stop_id 345497 for INV OM DSNO
Time spent in notification framework is (sec) .01
no. of OE messages :1
Error msg: ORA-20002: 3133: Activity instance 'SHIP_LINE' is not a notified acti
vity for item 'OEOL/894155'. in Package OE_Delayed_Requests_PVT Procedure Proces
s_Request_Pvt
Failed to interface Batch  226333  to Order Management because API interface_hea
der_to_OM failed
InterfaceTripStop: total stops processed: 1
Stops processed for ORDER MANAGEMENT with status NORMAL: 0
Stops processed for ORDER MANAGEMENT with status WARNING: 1
Stops interfaced for ORDER MANAGEMENT: 0

Has anyone else had this problem?

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