APPS.PO_APPROVAL_REMINDER_SV dependencies on WF_ITEM_ACTIVITY_STATUSES

Line 818: from wf_item_activity_statuses wias, wf_notifications wfn

814:
815: -- bug 3896181
816: select wfn.MESSAGE_NAME
817: into l_message_name
818: from wf_item_activity_statuses wias, wf_notifications wfn
819: where wias.notification_id = wfn.group_id
820: and wias.item_type = 'APVRMDER'
821: and wias.item_key = l_ItemKey ;
822: IF l_message_name = 'PO_ACCEPTANCE_PAST_DUE' then

Line 907: from wf_item_activity_statuses wias, wf_notifications wfn

903: to continue processing other POs in loop */
904: BEGIN
905: select wfn.MESSAGE_NAME
906: into l_message_name
907: from wf_item_activity_statuses wias, wf_notifications wfn
908: where wias.notification_id = wfn.group_id
909: and wias.item_type = 'APVRMDER'
910: and wias.item_key = l_ItemKey ;
911: EXCEPTION

Line 1176: from wf_item_activity_statuses wias, wf_notifications wfn

1172: --bug 3896181
1173: begin
1174: select wfn.MESSAGE_NAME
1175: into l_message_name
1176: from wf_item_activity_statuses wias, wf_notifications wfn
1177: where wias.notification_id = wfn.group_id
1178: and wias.item_type = 'APVRMDER'
1179: and wias.item_key = l_ItemKey ;
1180: exception

Line 1263: from wf_item_activity_statuses wias, wf_notifications wfn

1259: --bug 3896181
1260: begin
1261: select wfn.MESSAGE_NAME
1262: into l_message_name
1263: from wf_item_activity_statuses wias, wf_notifications wfn
1264: where wias.notification_id = wfn.group_id
1265: and wias.item_type = 'APVRMDER'
1266: and wias.item_key = l_ItemKey ;
1267: exception

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 3100: x_act_status WF_ITEM_ACTIVITY_STATUSES.ACTIVITY_STATUS%TYPE;

3096: FUNCTION is_active (x_item_type in varchar2,
3097: x_item_key in varchar2) RETURN BOOLEAN is
3098:
3099: -- Bug 3693990
3100: x_act_status WF_ITEM_ACTIVITY_STATUSES.ACTIVITY_STATUS%TYPE;
3101: x_result varchar2(30);
3102: -- Bug 3693990
3103:
3104: x_progress varchar2(100) := '001';

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 3111: --a union all between wf_item_activity_statuses and

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.
3115: --WF Team has provided an api wf_engine.itemstatus to check the

Line 3112: --wf_item_activity_statuses_h(history). A new record

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

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,