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.AD_EVENT_REGISTRY_PKG dependencies on AD_EVENT_TRANSITIONS

Line 22: Module_Name ad_event_transitions.module_name%TYPE,

18: -- worker status will be a string indicating status of all the workers
19: Worker_Status ad_event_versions.worker_status%TYPE,
20: Event_Version ad_events.last_version%TYPE,
21: Event_Type ad_events.event_type%TYPE ,
22: Module_Name ad_event_transitions.module_name%TYPE,
23: Worker_Id ad_event_transitions.worker_id%TYPE,
24: Max_Workers ad_event_versions.num_workers%TYPE );
25:
26: -- Type of table to store the list of events.

Line 23: Worker_Id ad_event_transitions.worker_id%TYPE,

19: Worker_Status ad_event_versions.worker_status%TYPE,
20: Event_Version ad_events.last_version%TYPE,
21: Event_Type ad_events.event_type%TYPE ,
22: Module_Name ad_event_transitions.module_name%TYPE,
23: Worker_Id ad_event_transitions.worker_id%TYPE,
24: Max_Workers ad_event_versions.num_workers%TYPE );
25:
26: -- Type of table to store the list of events.
27: TYPE Event_Tbl_Type IS TABLE OF Event_Rec_Type INDEX BY BINARY_INTEGER ;

Line 166: -- This procedure will insert data into the AD_EVENT_TRANSITIONS table.

162: END Set_Worker_Status_String;
163:
164:
165: ---------------------------------
166: -- This procedure will insert data into the AD_EVENT_TRANSITIONS table.
167: --
168: ---------------------------------
169: PROCEDURE Insert_Event_Transitions(
170: p_Event_Id IN NUMBER ,

Line 178: INSERT INTO ad_event_transitions(

174: p_Module_Name IN VARCHAR2 ,
175: p_Worker_Id IN NUMBER := NULL )
176: AS
177: BEGIN
178: INSERT INTO ad_event_transitions(
179: transition_id,
180: event_id,
181: version,
182: new_status,

Line 188: ad_event_transitions_s.NEXTVAL,

184: transition_time,
185: module_name,
186: worker_id)
187: VALUES (
188: ad_event_transitions_s.NEXTVAL,
189: p_Event_Id,
190: p_Version,
191: p_New_Status,
192: p_Old_Status,

Line 557: l_Worker_Id ad_event_transitions.worker_id%TYPE ;

553: l_Event_Status ad_event_versions.status%TYPE;
554: l_Event_type ad_events.event_type%TYPE;
555: l_Event_Id ad_events.event_id%TYPE;
556: l_Version ad_event_versions.version%TYPE;
557: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
558: l_Worker_Status_String ad_event_versions.worker_status%TYPE ;
559: l_Module_Name ad_event_transitions.module_name%TYPE ;
560: l_Event_Index NUMBER ;
561: -- this variable is used to hold in the IN parameter

Line 559: l_Module_Name ad_event_transitions.module_name%TYPE ;

555: l_Event_Id ad_events.event_id%TYPE;
556: l_Version ad_event_versions.version%TYPE;
557: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
558: l_Worker_Status_String ad_event_versions.worker_status%TYPE ;
559: l_Module_Name ad_event_transitions.module_name%TYPE ;
560: l_Event_Index NUMBER ;
561: -- this variable is used to hold in the IN parameter
562: l_p_Context ad_events.event_context%TYPE ;
563: BEGIN

Line 626: -- an entry is inserted into AD_EVENT_TRANSITIONS with

622: WHERE event_id = l_Event_Id
623: AND version = l_Version;
624: --
625: -- Whenver an Event is getting started
626: -- an entry is inserted into AD_EVENT_TRANSITIONS with
627: -- old status NULL and new status as Initialized status.
628: --
629: Insert_Event_Transitions(
630: p_Event_Id => l_Event_Id,

Line 665: l_Worker_Id ad_event_transitions.worker_id%TYPE ;

661: l_Version ad_event_versions.version%TYPE;
662: l_Worker_Status_String ad_event_versions.worker_status%TYPE;
663: l_End_Time DATE ;
664: l_Max_Workers ad_event_versions.num_workers%TYPE ;
665: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
666: l_Module_Name ad_event_transitions.module_name%TYPE ;
667: -- the following variable stores the index that points to the current
668: -- event's record in the event list
669: l_Event_Index NUMBER ;

Line 666: l_Module_Name ad_event_transitions.module_name%TYPE ;

662: l_Worker_Status_String ad_event_versions.worker_status%TYPE;
663: l_End_Time DATE ;
664: l_Max_Workers ad_event_versions.num_workers%TYPE ;
665: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
666: l_Module_Name ad_event_transitions.module_name%TYPE ;
667: -- the following variable stores the index that points to the current
668: -- event's record in the event list
669: l_Event_Index NUMBER ;
670: -- this variable is used to hold in the IN parameter

Line 1145: l_Module_Name ad_event_transitions.module_name%TYPE ;

1141: l_Event_Id ad_event_versions.event_id%TYPE;
1142: l_Version ad_event_versions.version%TYPE;
1143: l_Event_Index NUMBER ;
1144: l_Event_Type ad_events.event_type%TYPE ;
1145: l_Module_Name ad_event_transitions.module_name%TYPE ;
1146: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
1147: -- this variable is used to hold in the IN parameter
1148: l_p_Context ad_events.event_context%TYPE ;
1149: BEGIN

Line 1146: l_Worker_Id ad_event_transitions.worker_id%TYPE ;

1142: l_Version ad_event_versions.version%TYPE;
1143: l_Event_Index NUMBER ;
1144: l_Event_Type ad_events.event_type%TYPE ;
1145: l_Module_Name ad_event_transitions.module_name%TYPE ;
1146: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
1147: -- this variable is used to hold in the IN parameter
1148: l_p_Context ad_events.event_context%TYPE ;
1149: BEGIN
1150: --

Line 1284: l_Worker_Id ad_event_transitions.worker_id%TYPE ;

1280: l_Event_Version ad_event_versions.version%TYPE;
1281: l_Event_Status ad_event_versions.status%TYPE;
1282: l_Max_Workers ad_event_versions.num_workers%TYPE ;
1283: l_Worker_Status_String ad_event_versions.worker_status%TYPE;
1284: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
1285: l_Module_Name ad_event_transitions.module_name%TYPE ;
1286: l_Event_Index NUMBER ;
1287: -- this variable is used to hold in the IN parameter
1288: l_p_Context ad_events.event_context%TYPE ;

Line 1285: l_Module_Name ad_event_transitions.module_name%TYPE ;

1281: l_Event_Status ad_event_versions.status%TYPE;
1282: l_Max_Workers ad_event_versions.num_workers%TYPE ;
1283: l_Worker_Status_String ad_event_versions.worker_status%TYPE;
1284: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
1285: l_Module_Name ad_event_transitions.module_name%TYPE ;
1286: l_Event_Index NUMBER ;
1287: -- this variable is used to hold in the IN parameter
1288: l_p_Context ad_events.event_context%TYPE ;
1289:

Line 1414: l_Worker_Id ad_event_transitions.worker_id%TYPE ;

1410: l_Event_Status ad_event_versions.status%TYPE ;
1411: l_New_Status ad_event_versions.status%TYPE ;
1412: l_Worker_Status_String ad_event_versions.worker_status%TYPE ;
1413: l_End_Time ad_event_versions.end_time%TYPE ;
1414: l_Worker_Id ad_event_transitions.worker_id%TYPE ;
1415: l_Prev_Max_Workers ad_event_versions.num_workers%TYPE ;
1416: l_Commit_Flag BOOLEAN ;
1417: l_event_completed_EXP EXCEPTION ;
1418: -- these variables are used to hold in the IN parameter

Line 1486: -- ad_event_transitions.

1482: -- of workers from the registry. If there is any change we assume that
1483: -- the event is re-scheduled among a different set of workers.
1484: -- So, the worker details in ad_event_versions has to be updated
1485: -- and a special transition entry has to be inserted into
1486: -- ad_event_transitions.
1487: --
1488: IF ( NVL (l_Prev_Max_Workers,1) <> NVL (p_Num_Workers,1) ) THEN
1489: -- # if resch check
1490: -- Set the commit flag