Core Workflow - EBS (MOSC)

MOSC Banner

R12.2 Critical Workflow Patch

edited Mar 16, 2018 5:04AM in Core Workflow - EBS (MOSC) 1 commentAnswered

Following HOT or Downtime patching mode, Workflow processes get stuck and / or errant.  These Workflow processes cannot be fixed - even by issuing a Retry.

Workflow process definition is changed (upgraded or uploaded).  Subsequently, a patch is applied in HOT or Downtime patching mode, as opposed to the Online patching mode as normally recommended on 12.2.x releases of EBS.  Afterwards, processes are started (as when sales orders or order lines are created) between the time workflow was changed and the time patching was done may become stuck or errant.  Even Retry will not progress these errant workflow processes.

For additional details and for Patch information, refer to

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