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.IEX_STRATEGY_WF dependencies on IEX_STRATEGIES

Line 62: select jtf_object_type,jtf_object_id from iex_strategies

58: select distinct item_key from wf_item_attr_values_ondemand
59: where name = 'WRITEOFF_ID' and text_value = c_id and item_type = 'IEXWRREQ';
60:
61: cursor get_strategy_info(c_strategy_id IN number) is
62: select jtf_object_type,jtf_object_id from iex_strategies
63: where strategy_id = c_strategy_id;
64: -- end bug 7703319
65:
66: BEGIN

Line 241: from iex_strategies a,

237: iex_debug_pub.logmessage ('**** BEGIN CHECK_WORK_ITEM_OPEN ************');
238: END IF;
239: select count(*)
240: INTO v_result
241: from iex_strategies a,
242: ieX_strategy_work_items b
243: where a.strategy_id =p_strategy_id
244: and a.strategy_id =b.strategy_id
245: and a.next_work_item_id =b.work_item_id

Line 270: select count(*) INTO v_result from iex_strategies

266: -- IF PG_DEBUG < 10 THEN
267: IF (FND_LOG.LEVEL_EVENT >= PG_DEBUG) THEN
268: iex_debug_pub.logmessage ('**** BEGIN CHECK_CURRENT_WORK_ITEM ************');
269: END IF;
270: select count(*) INTO v_result from iex_strategies
271: where strategy_id =p_strategy_id
272: and next_work_item_id =p_work_item_id
273: and status_code ='OPEN';
274: return v_result;

Line 918: FROM IEX_STRATEGIES stry

914: ,stry_temp_wkitem.closure_time_uom escalate_wait_time_uom
915: ,stry_temp_wkitem.notify_yn NOTIFY_YN
916: ,NULL resource_id
917: ,workflow_item_type custom_workflow_type
918: FROM IEX_STRATEGIES stry
919: , IEX_STRATEGY_WORK_TEMP_XREF xref
920: , IEX_STRY_TEMP_WORK_ITEMS_VL stry_temp_wkitem
921: WHERE stry.STRATEGY_TEMPLATE_ID = xref.STRATEGY_TEMP_ID
922: and xref.WORK_ITEM_TEMP_ID = stry_temp_wkitem.WORK_ITEM_TEMP_ID

Line 967: FROM IEX_STRATEGIES stry

963: , uitem.escalate_wait_time_uom escalate_wait_time_uom
964: , uitem.NOTIFY_YN NOTIFY_YN
965: , uitem.resourcE_id resource_id
966: , uitem.custom_workflow_type custom_workflow_type
967: FROM IEX_STRATEGIES stry
968: , IEX_STRATEGY_user_items uitem
969: , IEX_STRY_TEMP_WORK_ITEMS_VL stry_temp_wkitem
970: WHERE stry.STRATEGY_ID = uitem.STRATEGY_ID
971: and uitem.WORK_ITEM_TEMP_ID = stry_temp_wkitem.WORK_ITEM_TEMP_ID

Line 990: select account_number,location from iex_strategies_bali_v

986: */
987:
988: -- Start Bug 6717880/7170165 by Ehuh
989: Cursor c_get_accloc(p_str_id number) Is
990: select account_number,location from iex_strategies_bali_v
991: where strategy_id = p_str_id;
992:
993: l_location varchar2(50);
994: l_acct_number varchar2(50);

Line 1100: from iex_strategies

1096: -- get_resource(p_party_id,l_competence_tab,l_resource_id);
1097: begin
1098: select jtf_object_type, jtf_object_id, cust_account_id,customer_site_use_id
1099: into l_object_code, l_object_id, l_cust_account_id,l_siteuse_id
1100: from iex_strategies
1101: where strategy_id = p_strategy_id;
1102: exception
1103: when others then
1104: iex_debug_pub.logmessage ('populate_schedule_times: More than one row for this Strategy. Exception on selecting strategy!!!!!');

Line 1690: select strategy_template_id from iex_strategies

1686:
1687:
1688:
1689: cursor c_get_strat_template_id (p_strategy_id NUMBER) IS
1690: select strategy_template_id from iex_strategies
1691: where strategy_id =p_strategy_id;
1692:
1693:
1694: cursor c_get_next_witem(p_strategy_id NUMBER,

Line 1743: FROM IEX_STRATEGIES stry

1739: , xref.WORK_ITEM_ORDER ORDER_BY
1740: , TO_NUMBER(NULL) WORK_ITEM_ID
1741: , xref.WORK_ITEM_TEMP_ID WORK_ITEM_TEMPLATE_ID
1742: , 'NOTCREATED' STATUS
1743: FROM IEX_STRATEGIES stry
1744: , IEX_STRATEGY_WORK_TEMP_XREF xref
1745: , IEX_STRY_TEMP_WORK_ITEMS_VL stry_temp_wkitem
1746: WHERE stry.STRATEGY_TEMPLATE_ID = xref.STRATEGY_TEMP_ID
1747: and xref.WORK_ITEM_TEMP_ID = stry_temp_wkitem.WORK_ITEM_TEMP_ID

Line 1776: FROM IEX_STRATEGIES stry

1772: , uitem.WORK_ITEM_ORDER ORDER_BY
1773: , TO_NUMBER(NULL) WORK_ITEM_ID
1774: , uitem.WORK_ITEM_TEMP_ID WORK_ITEM_TEMPLATE_ID
1775: , uitem.operation STATUS
1776: FROM IEX_STRATEGIES stry
1777: , IEX_STRATEGY_user_items uitem
1778: , IEX_STRY_TEMP_WORK_ITEMS_VL stry_temp_wkitem
1779: WHERE stry.STRATEGY_ID = uitem.STRATEGY_ID
1780: and uitem.WORK_ITEM_TEMP_ID = stry_temp_wkitem.WORK_ITEM_TEMP_ID

Line 2108: select strategy_template_id from iex_strategies

2104: l_strategy_template_id NUMBER;
2105: l_error VARCHAR2(32767);
2106:
2107: cursor c_get_strat_template_id (p_strategy_id NUMBER) IS
2108: select strategy_template_id from iex_strategies
2109: where strategy_id =p_strategy_id;
2110: l_value VARCHAR2(300);
2111: Begin
2112: -- initialize variable

Line 3637: --But status of the strategy in table IEX_STRATEGIES is still 'ONHOLD'.

3633: --begin bug#4506922 schekuri 03-Dec-2005
3634: --When the delinquency corresponding to the strategy becomes CURRENT or CLOSED,
3635: --strategy management concurrent program calls the procedure IEX_STRATEGY_WF.SEND_SIGNAL.
3636: --This procedure just updates the "STRATEGY_STATUS" attribute to "CLOSED" and completes the current activity.
3637: --But status of the strategy in table IEX_STRATEGIES is still 'ONHOLD'.
3638: --If workflow is waiting at WAIT_ON_HOLD_SIGNAL node, it will be completed and it goes to ONHOLD_CHECK node.
3639: --Since the status of the strategy in table IEX_STRATEGIES is still 'ONHOLD', it again goes to WAIT_ON_HOLD_SIGNAL node
3640: --and waits for 23 hrs. To avoid this added the following code.
3641: l_value :=wf_engine.GetActivityLabel(actid);

Line 3639: --Since the status of the strategy in table IEX_STRATEGIES is still 'ONHOLD', it again goes to WAIT_ON_HOLD_SIGNAL node

3635: --strategy management concurrent program calls the procedure IEX_STRATEGY_WF.SEND_SIGNAL.
3636: --This procedure just updates the "STRATEGY_STATUS" attribute to "CLOSED" and completes the current activity.
3637: --But status of the strategy in table IEX_STRATEGIES is still 'ONHOLD'.
3638: --If workflow is waiting at WAIT_ON_HOLD_SIGNAL node, it will be completed and it goes to ONHOLD_CHECK node.
3639: --Since the status of the strategy in table IEX_STRATEGIES is still 'ONHOLD', it again goes to WAIT_ON_HOLD_SIGNAL node
3640: --and waits for 23 hrs. To avoid this added the following code.
3641: l_value :=wf_engine.GetActivityLabel(actid);
3642: if instr(l_value,'STRATEGY_WORKFLOW')>0 then
3643: l_strategy_status := wf_engine.GetItemAttrText(

Line 3661: from iex_Strategies

3657: itemkey => itemkey,
3658: aname => 'STRATEGY_ID');
3659:
3660: select decode(count(*),0,'N','Y') into l_result
3661: from iex_Strategies
3662: where strategy_id =l_strategy_id
3663: and status_code ='ONHOLD';
3664:
3665: --begin bug#4506922 schekuri 03-Dec-2005