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.CS_WF_EVENT_PKG dependencies on WF_ENGINE

Line 127: -- is BES enabled, If not we will not call wf_engine.event().

123: IF (sel_workflow_csr%FOUND AND l_sel_workflow_rec.workflow IS NOT NULL) THEN
124:
125:
126: -- Before attempting to raise an event workflow,we check if the workflow process
127: -- is BES enabled, If not we will not call wf_engine.event().
128: -- This is important since calling event() api on a non BES workflow causes
129: -- it to raise an exception, which is handled in this custom rule function's
130: -- exception handler with a return status of 'ERROR'. A return status of ERROR
131: -- causes workflow to rollback any raised event performed, and since this is a

Line 149: -- the wf_engine.event() api.

145: INTO l_wf_activity_name;
146:
147: IF (sel_workflow_act_csr%FOUND) THEN
148: -- Workflow has a receive event as Start activity, so we can call
149: -- the wf_engine.event() api.
150:
151:
152: IF (l_sel_workflow_rec.AUTOLAUNCH_WORKFLOW_FLAG = 'Y') AND
153: (( l_sel_workflow_rec.resource_type = 'RS_EMPLOYEE' AND

Line 202: WF_ENGINE.Event(

198: -- This will raise an exception when the workflow does not have a receive event
199: -- activity,i.e., the workflow is not BES enabled.
200: --BEGIN
201:
202: WF_ENGINE.Event(
203: itemtype => 'SERVEREQ',
204: itemkey => l_item_key,
205: process_name => l_sel_workflow_rec.workflow,
206: event_message => p_event);

Line 269: If it is a BES workflow then it will call WF_ENGINE.Event .

265: This custom rule function corresponds to the subscriptions for workflow
266: business events oracle.apps.cs.sr.ServiceRequest.statuschanged
267:
268: This subscription will see if there are any workflow associated to the status transition.
269: If it is a BES workflow then it will call WF_ENGINE.Event .
270: If the proces is not BES compatible then it will try to launch the workflow process using
271: the old non-BES workflow API calls, i.e., CreateProcess(), StartProcess() .
272: This provides backward compatibility for those clients who has custom
273: workflow processes but has not converted to BES.

Line 382: -- is BES enabled, If not we will not call wf_engine.event().

378: IF (sel_workflow_csr%FOUND AND l_sel_workflow_rec.workflow IS NOT NULL) THEN
379:
380:
381: -- Before attempting to raise an event workflow,we check if the workflow process
382: -- is BES enabled, If not we will not call wf_engine.event().
383: -- This is important since calling event() api on a non BES workflow causes
384: -- it to raise an exception, which is handled in this custom rule function's
385: -- exception handler with a return status of 'ERROR'. A return status of ERROR
386: -- causes workflow to rollback any raised event performed, and since this is a

Line 422: WF_ENGINE.Event(

418: -- This will raise an exception when the workflow does not have a receive event
419: -- activity,i.e., the workflow is not BES enabled.
420: --BEGIN
421:
422: WF_ENGINE.Event(
423: itemtype => 'SERVEREQ',
424: itemkey => l_item_key,
425: process_name => l_sel_workflow_rec.workflow,
426: event_message => p_event);

Line 440: WF_ENGINE.CreateProcess(

436:
437: l_itemtype :='SERVEREQ';
438:
439: -- Create and launch the Workflow process
440: WF_ENGINE.CreateProcess(
441: itemtype => l_itemtype,
442: itemkey => l_item_key,
443: process => l_process_name );
444:

Line 445: WF_ENGINE.SetItemAttrText(

441: itemtype => l_itemtype,
442: itemkey => l_item_key,
443: process => l_process_name );
444:
445: WF_ENGINE.SetItemAttrText(
446: itemtype => l_itemtype,
447: itemkey => l_item_key,
448: aname => 'USER_ID',
449: --avalue => FND_GLOBAL.USER_ID );

Line 451: WF_ENGINE.SetItemAttrText(

447: itemkey => l_item_key,
448: aname => 'USER_ID',
449: --avalue => FND_GLOBAL.USER_ID );
450: avalue => l_user_id);
451: WF_ENGINE.SetItemAttrText(
452: itemtype => l_itemtype,
453: itemkey => l_item_key,
454: aname => 'RESP_ID',
455: --avalue => FND_GLOBAL.RESP_ID );

Line 458: WF_ENGINE.SetItemAttrText(

454: aname => 'RESP_ID',
455: --avalue => FND_GLOBAL.RESP_ID );
456: avalue => l_resp_id );
457:
458: WF_ENGINE.SetItemAttrText(
459: itemtype => l_itemtype,
460: itemkey => l_item_key,
461: aname => 'RESP_APPL_ID',
462: --avalue => FND_GLOBAL.RESP_APPL_ID );

Line 483: WF_ENGINE.SetItemAttrText(

479: x_role_name => l_initiator_role,
480: x_role_display_name => l_dummy );
481:
482:
483: WF_ENGINE.SetItemAttrText(
484: itemtype => l_itemtype,
485: itemkey => l_item_key,
486: aname => 'INITIATOR_ROLE',
487: avalue => l_initiator_role );

Line 489: WF_ENGINE.SetItemAttrText(

485: itemkey => l_item_key,
486: aname => 'INITIATOR_ROLE',
487: avalue => l_initiator_role );
488:
489: WF_ENGINE.SetItemAttrText(
490: itemtype => l_itemtype,
491: itemkey => l_item_key,
492: aname => 'WF_ADMINISTRATOR',
493: avalue => l_administrator );

Line 496: WF_ENGINE.SetItemOwner

492: aname => 'WF_ADMINISTRATOR',
493: avalue => l_administrator );
494:
495:
496: WF_ENGINE.SetItemOwner
497: ( itemtype => l_itemtype,
498: itemkey => l_item_key,
499: owner => l_initiator_role );
500: --End Bug 12411987

Line 501: WF_ENGINE.StartProcess(

497: ( itemtype => l_itemtype,
498: itemkey => l_item_key,
499: owner => l_initiator_role );
500: --End Bug 12411987
501: WF_ENGINE.StartProcess(
502: itemtype => l_itemtype,
503: itemkey => l_item_key );
504:
505: END IF;