eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PO_APPROVAL_REMINDER_SV dependencies on WF_ITEM_ACTIVITY_STATUSES_V

Line 2839: from wf_item_activity_statuses_v wias, wf_items_v wi

2835: --we want to make sure that the reminder notification with new item key
2836: --is aborted correctly.
2837: Cursor cand_active_wf(l_itemkey VARCHAR2) IS
2838: select wias.activity_status_code, wias.item_key
2839: from wf_item_activity_statuses_v wias, wf_items_v wi
2840: where wias.item_type = 'APVRMDER'
2841: and wias.item_key like l_itemkey||'%'
2842: and wias.item_type = wi.item_type
2843: and wias.item_key = wi.item_key

Line 3110: --wf_item_activity_statuses_v is a view which is based on

3106: BEGIN
3107: x_progress := 'PO_APPROVAL_REMINDER_SV.is_active-001';
3108:
3109: --bug#3693990 commented out the above sql because the view
3110: --wf_item_activity_statuses_v is a view which is based on
3111: --a union all between wf_item_activity_statuses and
3112: --wf_item_activity_statuses_h(history). A new record
3113: --gets inserted into history table when the wf process
3114: --raises an error.

Line 3117: --instead of query the wf_item_activity_statuses_v view directly.

3113: --gets inserted into history table when the wf process
3114: --raises an error.
3115: --WF Team has provided an api wf_engine.itemstatus to check the
3116: --active status of any given activity. We need to call this
3117: --instead of query the wf_item_activity_statuses_v view directly.
3118: BEGIN
3119: wf_engine.itemstatus (itemtype => x_item_type,
3120: itemkey => x_item_key,
3121: status => x_act_status,