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.

Demantra Solutions - EBS (MOSC)

Demantra Workflow Runtimes

May 6, 2014 7:03AM edited May 14, 2014 2:17AM in Demantra Solutions - EBS (MOSC) 10 commentsAnswered

What is the best approach to calculate workflow runtimes in Demantra.

WF_PROCESS_LOG does not seem to give accurate information as the RECORD_UPDATED column keeps on changing to the current date.

Below is the example for the schema id belonging to EBS FULL DOWNLOAD workflow

select

* from demantra.wf_process_log

where schema_id = 631

SCHEMA_ID	PROCESS_ID	STEP_ID	RECORD_UPDATED	RECORD_CREATED
631	805966	MsgDownloadOK	5/6/2014 5:03	4/9/2014 19:00
631	806052	MsgDownloadOK	5/6/2014 5:03	4/17/2014 19:00
631	806072	MsgDownloadOK	5/6/2014 5:03	4/17/2014 20:07
631	806260	MsgDownloadOK	5/6/2014 5:03	5/3/2014 5:33
631	806281	MsgDownloadOK	5/6/2014 5:03	5/4/2014
631	806352	MsgDownloadOK	5/6/2014 5:03	5/5/2014 12:10

1

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