Core Workflow - EBS (MOSC)

MOSC Banner

Workflow Requests That Should Be Scheduled To Run On All Instances

edited Sep 13, 2010 11:47AM in Core Workflow - EBS (MOSC) 3 commentsAnswered

<!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->

The following reflects seeded workflow requests that should be scheduled to run towards maintaining the health of workflow on each environment:

 

• Workflow Control Queue Cleanup 

 

The Workflow Control Queue Cleanup concurrent program removes inactive subscribers from the Workflow control queue, WF_CONTROL, to improve performance.  This is a concurrent request that should be scheduled once every 12 hours.

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