Shipping Execution - EBS (MOSC)

MOSC Banner

Interface trip stop and workflow purge

edited May 6, 2013 2:45AM in Shipping Execution - EBS (MOSC) 2 commentsAnswered
Hi All,
interface trip stop often completes with warning and deliveries are stuck in the interface.

Analyst says this may be because of workflow purges before interfacing.

I have checked in the system and no one has submitted 'Purge Order Management Workflow' concurrent request and neither it has been scheduled.

however “Purge Obsolete Workflow Runtime Data” concurrent request scheduled twice a day with below parameters

(1) , , 7, TEMP, N, 500, N
(2) , , 30, PERM, Y, 500, N

can above scheduled concurrent request be the reason for my workflow purging and stuck deliveries in interface?

Please advise.

Thanks
SidK

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center