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.WF_ITEM_ACTIVITY_STATUS dependencies on WF_ITEM_ACTIVITY_STATUSES

Line 90: from WF_ITEM_ACTIVITY_STATUSES WIAS

86: wf_item_activity_status.c_begindate, wf_item_activity_status.c_enddate,
87: wf_item_activity_status.c_duedate,
88: wf_item_activity_status.c_errname, wf_item_activity_status.c_errmsg,
89: wf_item_activity_status.c_errstack
90: from WF_ITEM_ACTIVITY_STATUSES WIAS
91: where WIAS.ITEM_TYPE = itemtype
92: and WIAS.ITEM_KEY = itemkey
93: and WIAS.PROCESS_ACTIVITY = actid;
94:

Line 122: -- Update the notification id and assigned user in WF_ITEM_ACTIVITY_STATUSES

118: end InitCache;
119:
120: --
121: -- Update_Notification (PRIVATE)
122: -- Update the notification id and assigned user in WF_ITEM_ACTIVITY_STATUSES
123: -- table for a given item activity.
124: -- IN
125: -- itemtype - Activity item type.
126: -- itemkey - The item key.

Line 139: WF_ITEM_ACTIVITY_STATUSES set

135: user in varchar2)
136: is
137: begin
138: update
139: WF_ITEM_ACTIVITY_STATUSES set
140: NOTIFICATION_ID = notid,
141: ASSIGNED_USER = user
142: where ITEM_TYPE = itemtype
143: and ITEM_KEY = itemkey

Line 252: -- the WF_ITEM_ACTIVITY_STATUSES table, the status out variable will be null.

248:
249: --
250: -- Status (PRIVATE)
251: -- Returns the status for this item activity. If there is no row in
252: -- the WF_ITEM_ACTIVITY_STATUSES table, the status out variable will be null.
253: -- IN
254: -- itemtype - Activity item type.
255: -- itemkey - The item key.
256: -- actid - Process activity (instance id).

Line 282: -- row in the WF_ITEM_ACTIVITY_STATUSES table, both status and result

278:
279: --
280: -- Result (PRIVATE)
281: -- Returns the status and result for this item activity. If there is no
282: -- row in the WF_ITEM_ACTIVITY_STATUSES table, both status and result
283: -- out variables will be null.
284: -- IN
285: -- itemtype - Activity item type.
286: -- itemkey - The item key.

Line 348: -- If there is no row in the WF_ITEM_ACTIVITY_STATUSES table, the notid

344:
345: --
346: -- Notification_Status (PRIVATE)
347: -- Returns the notification id and assigned user for this item activity.
348: -- If there is no row in the WF_ITEM_ACTIVITY_STATUSES table, the notid
349: -- and user out variables will contain null.
350: -- IN
351: -- itemtype - Activity item type.
352: -- itemkey - The item key.

Line 476: from WF_ITEM_ACTIVITY_STATUSES

472:
473: select
474: error_name,error_message,error_stack
475: into l_errname,l_errmsg,l_errstack
476: from WF_ITEM_ACTIVITY_STATUSES
477: where ITEM_TYPE = itemtype
478: and ITEM_KEY = itemkey
479: and PROCESS_ACTIVITY = actid;
480:

Line 485: WF_ITEM_ACTIVITY_STATUSES set

481: l_errname:= substrb(l_errname||prefix||errname||']', 1, 30);
482: l_errmsg:=substrb(l_errmsg||prefix||errmsg||']', 1, 2000);
483: l_errstack:=substrb(l_errstack||prefix||errstack||']', 1, 4000);
484: update
485: WF_ITEM_ACTIVITY_STATUSES set
486: ERROR_NAME=l_errname,
487: ERROR_MESSAGE = l_errmsg,
488: ERROR_STACK = l_errstack
489: where ITEM_TYPE = itemtype

Line 536: WF_ITEM_ACTIVITY_STATUSES set

532:
533: -- Store error info and set status/result
534:
535: update
536: WF_ITEM_ACTIVITY_STATUSES set
537: ACTIVITY_STATUS = wf_engine.eng_error,
538: ACTIVITY_RESULT_CODE = errcode,
539: ERROR_NAME = errname,
540: ERROR_MESSAGE = errmsg,

Line 550: -- No record was found in WF_ITEM_ACTIVITY_STATUSES. We will check

546:
547: end if;
548:
549: -- Bug 3960517
550: -- No record was found in WF_ITEM_ACTIVITY_STATUSES. We will check
551: -- the history table. If record exists in WF_ITEM_ACTIVITY_STATUSES_H,
552: -- we may have re-entered a node causing engine to prepare for looping.
553: -- But instead of going through all the activities along the loop, it has
554: -- progressed through a different path. Since there maybe multiple records

Line 551: -- the history table. If record exists in WF_ITEM_ACTIVITY_STATUSES_H,

547: end if;
548:
549: -- Bug 3960517
550: -- No record was found in WF_ITEM_ACTIVITY_STATUSES. We will check
551: -- the history table. If record exists in WF_ITEM_ACTIVITY_STATUSES_H,
552: -- we may have re-entered a node causing engine to prepare for looping.
553: -- But instead of going through all the activities along the loop, it has
554: -- progressed through a different path. Since there maybe multiple records
555: -- in the history table with the same item type, item key and actid, we may

Line 559: from WF_ITEM_ACTIVITY_STATUSES_H

555: -- in the history table with the same item type, item key and actid, we may
556: -- not be able to mark the error accordingly, so we just simply ignore the error.
557: if (SQL%NOTFOUND) then
558: select 1 into l_exist
559: from WF_ITEM_ACTIVITY_STATUSES_H
560: where ITEM_TYPE = itemtype
561: and ITEM_KEY= itemkey
562: and process_activity = actid
563: and rownum < 2;

Line 587: -- Deletes the row for this item activity from WF_ITEM_ACTIVITY_STATUSES.

583: end Set_Error;
584:
585: --
586: -- Delete_Status (PRIVATE)
587: -- Deletes the row for this item activity from WF_ITEM_ACTIVITY_STATUSES.
588: -- IN
589: -- itemtype - Activity item type.
590: -- itemkey - The item key.
591: -- actid - Process activity (instance id).

Line 599: from WF_ITEM_ACTIVITY_STATUSES

595: actid in number)
596: is
597: begin
598: delete
599: from WF_ITEM_ACTIVITY_STATUSES
600: where ITEM_TYPE = itemtype
601: and ITEM_KEY = itemkey
602: and PROCESS_ACTIVITY = actid;
603:

Line 813: WF_ITEM_ACTIVITY_STATUSES set

809: -- not yet set (activity has been aborted without being executed).
810:
811: if not (newStatus) then
812: update
813: WF_ITEM_ACTIVITY_STATUSES set
814: ACTIVITY_STATUS = create_status.status,
815: ACTIVITY_RESULT_CODE = nvl(create_status.result, ACTIVITY_RESULT_CODE),
816: BEGIN_DATE = nvl(create_status.beginning, BEGIN_DATE),
817: END_DATE = nvl(create_status.ending, END_DATE),

Line 837: into WF_ITEM_ACTIVITY_STATUSES (

833: -- Create the status if not found
834: if ((newStatus) or (SQL%ROWCOUNT = 0)) then
835: begin
836: insert
837: into WF_ITEM_ACTIVITY_STATUSES (
838: ITEM_TYPE,
839: ITEM_KEY,
840: PROCESS_ACTIVITY,
841: ACTIVITY_STATUS,

Line 893: WF_ITEM_ACTIVITY_STATUSES set

889: -- automatically update to ensure fault tolerance.
890: l_newStatus := FALSE;
891:
892: update
893: WF_ITEM_ACTIVITY_STATUSES set
894: ACTIVITY_STATUS = create_status.status,
895: ACTIVITY_RESULT_CODE = nvl(create_status.result,
896: ACTIVITY_RESULT_CODE),
897: BEGIN_DATE = nvl(create_status.beginning, BEGIN_DATE),

Line 994: UPDATE wf_item_activity_statuses

990: l_username := performer;
991: end if;
992:
993: -- update the status record with the action and performer
994: UPDATE wf_item_activity_statuses
995: SET action = Audit.action,
996: performed_by = l_username
997: WHERE item_type = Audit.itemtype
998: AND item_key = Audit.itemkey

Line 1003: --wf_item_activity_statuses table, hence we should not throw an

999: AND process_activity = Audit.actid;
1000:
1001: --Bug 3361746
1002: --The existing handleerror API does not mandatorily require an entry in
1003: --wf_item_activity_statuses table, hence we should not throw an
1004: --exception if no row is found for the activity.
1005:
1006: exception
1007: when others then

Line 1029: -- UPDATE wf_item_activity_statuses

1025: -- prov_request_id in number)
1026: -- is
1027: -- begin
1028: --
1029: -- UPDATE wf_item_activity_statuses
1030: -- SET prov_request_id = Update_Prov_Request.prov_request_id
1031: -- WHERE item_type = Update_Prov_Request.itemtype
1032: -- AND item_key = Update_Prov_Request.itemkey
1033: -- AND process_activity = Update_Prov_Request.actid;