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.PA_UTILS dependencies on PA_EXPEND_ITEM_ADJ_ACTIVITIES

Line 2487: pa_expend_item_adj_activities b

2483: where a.adjusted_expenditure_item_id IS NULL
2484: --and cost_distributed_flag = 'Y'
2485: start with expenditure_item_id = p_xfer_item_id
2486: connect by prior a.expenditure_item_id = a.transferred_from_exp_item_id) x,
2487: pa_expend_item_adj_activities b
2488: where x.expenditure_item_id = b.expenditure_item_id
2489: and b.module_code in ('PAXREVTXN', 'PAXPRRPE')
2490: order by 1 desc, ord;
2491:

Line 2494: from pa_expend_item_adj_activities

2490: order by 1 desc, ord;
2491:
2492: cursor check_item_activity(p_exp_item_id number) is
2493: select module_code, decode(module_code, 'PAXREVTXN', 'A', 'B') ord
2494: from pa_expend_item_adj_activities
2495: where expenditure_item_id = p_exp_item_id
2496: and module_code in ('PAXREVTXN', 'PAXPRRPE')
2497: order by ord;
2498:

Line 2499: l_module_code pa_expend_item_adj_activities.module_code%TYPE;

2495: where expenditure_item_id = p_exp_item_id
2496: and module_code in ('PAXREVTXN', 'PAXPRRPE')
2497: order by ord;
2498:
2499: l_module_code pa_expend_item_adj_activities.module_code%TYPE;
2500: l_order varchar2(1);
2501: l_previous_indx number;
2502:
2503: TYPE l_item_tbl is table of number index by binary_integer;

Line 2505: --TYPE l_mod_code_tbl is table of pa_expend_item_adj_activities.module_code%TYPE index by binary_integer;

2501: l_previous_indx number;
2502:
2503: TYPE l_item_tbl is table of number index by binary_integer;
2504: TYPE l_vc1_tbl is table of varchar2(1) index by binary_integer;
2505: --TYPE l_mod_code_tbl is table of pa_expend_item_adj_activities.module_code%TYPE index by binary_integer;
2506: TYPE l_cm_tbl is table of varchar2(30) index by binary_integer;
2507:
2508: l_item_id_tbl l_item_tbl;
2509: l_cdf_tbl l_vc1_tbl;

Line 2520: -- 1. If the current expenditure item has an entry for PAXREVTCN in the pa_expend_item_adj_activities table

2516: -- if the expenditure item has module_code as 'PAXREVTXN', then the current setup can be used.
2517: -- if the expenditure item has module code of 'PAXPRRPE', then it's an adjustment that originated from Expenditure inquiry.
2518:
2519: -- Following rules are applied to figure out the costing method to be used:
2520: -- 1. If the current expenditure item has an entry for PAXREVTCN in the pa_expend_item_adj_activities table
2521: -- then, the item is eligible to use the current costing rules setup.
2522: -- 2. If the current expenditure item has an entry for PAXPRRPE in pa_expend_item_adj_activities table,
2523: -- then traverse the related items up and down to figure out if the items are costed.
2524: -- If they're costed then the same costing method should be used on the current item.

Line 2522: -- 2. If the current expenditure item has an entry for PAXPRRPE in pa_expend_item_adj_activities table,

2518:
2519: -- Following rules are applied to figure out the costing method to be used:
2520: -- 1. If the current expenditure item has an entry for PAXREVTCN in the pa_expend_item_adj_activities table
2521: -- then, the item is eligible to use the current costing rules setup.
2522: -- 2. If the current expenditure item has an entry for PAXPRRPE in pa_expend_item_adj_activities table,
2523: -- then traverse the related items up and down to figure out if the items are costed.
2524: -- If they're costed then the same costing method should be used on the current item.
2525: --
2526: -- Need to put some examples.