Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Siebel Business Process & Functionality (MOSC)

SRProc and TimeZone issue.

Dec 11, 2013 3:25AM edited Dec 16, 2013 7:01PM in Siebel Business Process & Functionality (MOSC) 4 commentsAnswered

Repeating Instances of RCRs are struck in "Active" status.

We checked the logs for SRProc Component and this is the inference we have:

- When we created & submitted an RCR, a new repeating instance gets created with status as “Queued” and Scheduled Start Time populated.

- SRProc polls S_SRM_REQUEST table gets this queued record and routes the request to the target component WfProcMgr/WfProcBtchMgr through SRBroker.

- New Task is created on the target component and the details(Task ID) are passed to SRProc, which is then written into S_SRM_REQUEST.

- Following is the update statement triggered to update Task ID to S_SRM_REQUEST (from SRProc log file)

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month