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.GMS_BILLING dependencies on GMS_BURDEN_COMPONENTS

Line 456: FROM gms_burden_components

452: IS
453: SELECT expenditure_item_id, adl_line_num, actual_project_id,
454: actual_task_id, expenditure_org_id, burden_exp_type, burden_cost_code,
455: amount, revenue_accumulated, creation_date
456: FROM gms_burden_components
457: WHERE award_project_id = f_project_id
458: AND event_num = f_event_num
459: AND event_type = UPPER(f_event_calling_process);
460:

Line 463: f_burd_rev_accumulated gms_burden_components.revenue_accumulated%TYPE;

459: AND event_type = UPPER(f_event_calling_process);
460:
461: f_burd_exp_item_id gms_award_distributions.expenditure_item_id%TYPE;
462: f_burd_adl_line_num gms_award_distributions.adl_line_num%TYPE;
463: f_burd_rev_accumulated gms_burden_components.revenue_accumulated%TYPE;
464: f_burd_revenue_amount gms_burden_components.amount%TYPE;
465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;

Line 464: f_burd_revenue_amount gms_burden_components.amount%TYPE;

460:
461: f_burd_exp_item_id gms_award_distributions.expenditure_item_id%TYPE;
462: f_burd_adl_line_num gms_award_distributions.adl_line_num%TYPE;
463: f_burd_rev_accumulated gms_burden_components.revenue_accumulated%TYPE;
464: f_burd_revenue_amount gms_burden_components.amount%TYPE;
465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;

Line 465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;

461: f_burd_exp_item_id gms_award_distributions.expenditure_item_id%TYPE;
462: f_burd_adl_line_num gms_award_distributions.adl_line_num%TYPE;
463: f_burd_rev_accumulated gms_burden_components.revenue_accumulated%TYPE;
464: f_burd_revenue_amount gms_burden_components.amount%TYPE;
465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;
469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;

Line 466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;

462: f_burd_adl_line_num gms_award_distributions.adl_line_num%TYPE;
463: f_burd_rev_accumulated gms_burden_components.revenue_accumulated%TYPE;
464: f_burd_revenue_amount gms_burden_components.amount%TYPE;
465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;
469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;
470: f_burd_creation_date gms_burden_components.creation_date%TYPE;

Line 467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;

463: f_burd_rev_accumulated gms_burden_components.revenue_accumulated%TYPE;
464: f_burd_revenue_amount gms_burden_components.amount%TYPE;
465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;
469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;
470: f_burd_creation_date gms_burden_components.creation_date%TYPE;
471:

Line 468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;

464: f_burd_revenue_amount gms_burden_components.amount%TYPE;
465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;
469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;
470: f_burd_creation_date gms_burden_components.creation_date%TYPE;
471:
472: -- Get_Event_Details required as Event to Installment has one - many relationship

Line 469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;

465: f_burd_act_project_id gms_burden_components.actual_project_id%TYPE;
466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;
469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;
470: f_burd_creation_date gms_burden_components.creation_date%TYPE;
471:
472: -- Get_Event_Details required as Event to Installment has one - many relationship
473:

Line 470: f_burd_creation_date gms_burden_components.creation_date%TYPE;

466: f_burd_act_task_id gms_burden_components.actual_task_id%TYPE;
467: f_burd_org_id gms_burden_components.expenditure_org_id%TYPE;
468: f_burd_exp_type gms_burden_components.burden_exp_type%TYPE;
469: f_burd_cost_code gms_burden_components.burden_cost_code%TYPE;
470: f_burd_creation_date gms_burden_components.creation_date%TYPE;
471:
472: -- Get_Event_Details required as Event to Installment has one - many relationship
473:
474: CURSOR get_event_details (f_project_id NUMBER, f_event_num NUMBER,

Line 497: || 30. Deleting from gms_burden_components

493: /* --------------------------------------------------------------------------
494: || Rollback Activities Include:
495: || 10. Updating gms_award_distributions (revenue_distributed_flag/billed_flag)
496: || 20. Deleting from gms_event_intersect
497: || 30. Deleting from gms_burden_components
498: || 40. Updating gms_summary_project_fundings
499: || 50. Deleting gms_event_attribute
500: -------------------------------------------------------------------------- */
501:

Line 611: -- 30: Deleting records from gms_burden_components

607: f_burd_creation_date;
608: EXIT WHEN get_exp_burden_info%NOTFOUND;
609:
610: BEGIN -- Expenditure Rollup Block
611: -- 30: Deleting records from gms_burden_components
612: x_stage := 30;
613:
614: IF f_burd_rev_accumulated = 'Y' and evt.event_type = 'Revenue'
615: THEN

Line 638: FROM gms_burden_components

634: );
635: END IF;
636:
637: DELETE
638: FROM gms_burden_components
639: WHERE expenditure_item_id = f_burd_exp_item_id
640: AND adl_line_num = f_burd_adl_line_num
641: AND award_project_id = evt.project_id
642: AND event_num = evt.event_num

Line 754: -- records from gms_event_intersect and gms_burden_components

750: END billing_rollback;
751:
752: -- -----------------------------------------------------------------------------
753: -- Following procedure DELETE_NULL_EVENTS will delete the null event
754: -- records from gms_event_intersect and gms_burden_components
755: -- At the same time, it will reset the award distribution lines billing flags
756: -- For invoice records, procedure may have to update summary fundings ...
757:
758: -- !!! Flags will be reset with a value of "Z" indicating net zero ...

Line 856: from gms_burden_components

852: set billed_flag = decode(billed_flag,'Y','Z','Z','N')
853: where (expenditure_item_id,adl_line_num) in
854: (select expenditure_item_id,
855: adl_line_num
856: from gms_burden_components
857: where award_project_id = X_award_project_id
858: and event_num = -2
859: and request_id = X_request_id
860: and event_type = X_event_type

Line 875: from gms_burden_components

871: set revenue_distributed_flag = decode(revenue_distributed_flag,'Y','Z','Z','N')
872: where (expenditure_item_id,adl_line_num) in
873: (select expenditure_item_id,
874: adl_line_num
875: from gms_burden_components
876: where award_project_id = X_award_project_id
877: and event_num = -2
878: and request_id = X_request_id
879: and event_type = X_event_type

Line 890: from gms_burden_components

886: gms_error_pkg.gms_debug('In DELETE_NULL_EVENTS - Stage: Burden - Delete records', 'C');
887: END IF;
888:
889: Delete
890: from gms_burden_components
891: where award_project_id = X_award_project_id
892: and event_num = -2
893: and request_id = X_request_id
894: and event_type = X_event_type;

Line 1180: || 3. Deleting from gms_burden_components

1176: /* --------------------------------------------------------------------------
1177: || Here's what we need to do :
1178: || 1. Updating gms_summary_project_fundings
1179: || 2. Deleting from gms_event_intersect
1180: || 3. Deleting from gms_burden_components
1181: || 4. Updating gms_award_distributions (revenue_distributed_flag/billed_flag)
1182: -------------------------------------------------------------------------- */
1183:
1184: select award_project_id

Line 1224: from gms_burden_components

1220: AND event_num is NULL
1221: AND event_type = x_event_type
1222: union
1223: select expenditure_item_id, adl_line_num
1224: from gms_burden_components
1225: where expenditure_item_id = x_expenditure_item_id
1226: AND award_project_id = x_award_project_id
1227: AND event_num is NULL
1228: AND event_type = x_event_type );

Line 1237: DELETE FROM gms_burden_components

1233: AND event_num is NULL
1234: AND event_type = x_event_type ;
1235:
1236:
1237: DELETE FROM gms_burden_components
1238: WHERE expenditure_item_id = x_expenditure_item_id
1239: AND award_project_id = x_award_project_id
1240: AND event_num IS NULL
1241: AND event_type = x_event_type ;

Line 2610: --amount that has been billed or accrued to_date from the GMS_BURDEN_COMPONENTS table

2606: ---------------------------------------------------------------------------------
2607: --------------------------------------------------------------------------------
2608: --Procedure GET_BURD_AMT_IN_INTERSECT: For a given expenditure item and for a given burden
2609: --cost component used to burden this expenditure item this procedure will return the burden
2610: --amount that has been billed or accrued to_date from the GMS_BURDEN_COMPONENTS table
2611: --------------------------------------------------------------------------------
2612: PROCEDURE GET_BURD_AMT_IN_INTERSECT(X_Expenditure_Item_Id IN NUMBER,
2613: X_Adl_Line_Num IN NUMBER,
2614: X_Calling_Process IN VARCHAR2,

Line 2625: GMS_BURDEN_COMPONENTS

2621: Select
2622: nvl(sum(nvl(amount,0)),0)
2623: into X_Burden_Amt_In_Table
2624: from
2625: GMS_BURDEN_COMPONENTS
2626: where
2627: expenditure_item_id = X_Expenditure_Item_Id
2628: and adl_line_num = X_Adl_Line_Num
2629: and burden_cost_code = X_Burden_Cost_Code

Line 2741: --GMS_BURDEN_COMPONENTS table for a given expenditure item id and for a given burden

2737: -----------------------------------------------------------------------------------
2738:
2739: ----------------------------------------------------------------------------------
2740: --Procedure GET_BURDEN_AMT_TO_INSERT returns the burden amount to be inserted into
2741: --GMS_BURDEN_COMPONENTS table for a given expenditure item id and for a given burden
2742: --cost component
2743: ----------------------------------------------------------------------------------
2744: PROCEDURE GET_BURDEN_AMT_TO_INSERT(X_Expenditure_Item_Id IN NUMBER,
2745: X_Adl_Line_Num IN NUMBER,

Line 2789: --Procedure INSERT_GMS_BURDEN_COMPONENTS: Inserts rows into GMS_BURDEN_COMPONENTS table for

2785: End GET_BURDEN_AMT_TO_INSERT;
2786: ------------------------------------------------------------------------------------
2787:
2788: -----------------------------------------------------------------------------------
2789: --Procedure INSERT_GMS_BURDEN_COMPONENTS: Inserts rows into GMS_BURDEN_COMPONENTS table for
2790: --each component that a raw cost transaction is burdened by for an amount equal to the difference
2791: --between the current Burden Amt from the View for that Component and that expenditure item id and
2792: --the cumulative amount in GMS_BURDEN_COMPONENTS table for that component and that exp item.
2793: -----------------------------------------------------------------------------------

Line 2792: --the cumulative amount in GMS_BURDEN_COMPONENTS table for that component and that exp item.

2788: -----------------------------------------------------------------------------------
2789: --Procedure INSERT_GMS_BURDEN_COMPONENTS: Inserts rows into GMS_BURDEN_COMPONENTS table for
2790: --each component that a raw cost transaction is burdened by for an amount equal to the difference
2791: --between the current Burden Amt from the View for that Component and that expenditure item id and
2792: --the cumulative amount in GMS_BURDEN_COMPONENTS table for that component and that exp item.
2793: -----------------------------------------------------------------------------------
2794: PROCEDURE INSERT_GMS_BURDEN_COMPONENTS(X_Award_Project_Id IN NUMBER,
2795: X_Expenditure_Item_Id IN NUMBER,
2796: X_Adl_Line_Num IN NUMBER,

Line 2794: PROCEDURE INSERT_GMS_BURDEN_COMPONENTS(X_Award_Project_Id IN NUMBER,

2790: --each component that a raw cost transaction is burdened by for an amount equal to the difference
2791: --between the current Burden Amt from the View for that Component and that expenditure item id and
2792: --the cumulative amount in GMS_BURDEN_COMPONENTS table for that component and that exp item.
2793: -----------------------------------------------------------------------------------
2794: PROCEDURE INSERT_GMS_BURDEN_COMPONENTS(X_Award_Project_Id IN NUMBER,
2795: X_Expenditure_Item_Id IN NUMBER,
2796: X_Adl_Line_Num IN NUMBER,
2797: X_Request_Id IN NUMBER,
2798: X_Calling_Process IN VARCHAR2,

Line 2815: INSERT INTO GMS_BURDEN_COMPONENTS(AWARD_PROJECT_ID,

2811:
2812: If X_Burd_Amt_To_Insert <> 0 then
2813: Begin
2814:
2815: INSERT INTO GMS_BURDEN_COMPONENTS(AWARD_PROJECT_ID,
2816: EXPENDITURE_ITEM_ID,
2817: ADL_LINE_NUM,
2818: AMOUNT,
2819: REQUEST_ID,

Line 2885: End INSERT_GMS_BURDEN_COMPONENTS;

2881:
2882: End;
2883: End If;
2884:
2885: End INSERT_GMS_BURDEN_COMPONENTS;
2886: ------------------------------------------------------------------------------------
2887: -----------------------------------------------------------------------------------------
2888: -- Procedure INSERT_GMS_EVENT_INTERSECT: Inserts a row into GMS_EVENT_INTERSECT table for an
2889: -- amount equal to the difference between the current Raw Cost on the Expenditure Item and

Line 3047: --Procedure UPDATE_GMS_BURDEN_COMPONENTS: Updates GMS_BURDEN_COMPONENTS table with the Event Num of

3043:
3044: --------------------------------------------------------------------------------------------
3045:
3046: --------------------------------------------------------------------------------------------
3047: --Procedure UPDATE_GMS_BURDEN_COMPONENTS: Updates GMS_BURDEN_COMPONENTS table with the Event Num of
3048: --the event created.
3049: --------------------------------------------------------------------------------------------
3050: PROCEDURE UPDATE_GMS_BURDEN_COMPONENTS(X_Event_Num IN NUMBER,
3051: X_Award_Project_Id IN NUMBER,

Line 3050: PROCEDURE UPDATE_GMS_BURDEN_COMPONENTS(X_Event_Num IN NUMBER,

3046: --------------------------------------------------------------------------------------------
3047: --Procedure UPDATE_GMS_BURDEN_COMPONENTS: Updates GMS_BURDEN_COMPONENTS table with the Event Num of
3048: --the event created.
3049: --------------------------------------------------------------------------------------------
3050: PROCEDURE UPDATE_GMS_BURDEN_COMPONENTS(X_Event_Num IN NUMBER,
3051: X_Award_Project_Id IN NUMBER,
3052: X_Request_Id IN NUMBER,
3053: X_Actual_Project_Id IN NUMBER,
3054: X_Actual_Task_Id IN NUMBER,

Line 3064: update /+INDEX(GMS_BURDEN_COMPONENTS GMS_BURDEN_COMPONENTS_N3)/ GMS_BURDEN_COMPONENTS

3060: Begin
3061: IF L_DEBUG = 'Y' THEN
3062: gms_error_pkg.gms_debug('IN BURDEN COMPONENTS Updation - START','C');
3063: END IF;
3064: update /*+INDEX(GMS_BURDEN_COMPONENTS GMS_BURDEN_COMPONENTS_N3)*/ GMS_BURDEN_COMPONENTS
3065: set
3066: EVENT_NUM = X_Event_Num
3067: ,last_update_date = sysdate
3068: ,last_updated_by = fnd_global.user_id

Line 3099: End UPDATE_GMS_BURDEN_COMPONENTS;

3095: IF L_DEBUG = 'Y' THEN
3096: gms_error_pkg.gms_debug('IN BURDEN COMPONENTS Updation - END','C');
3097: END IF;
3098:
3099: End UPDATE_GMS_BURDEN_COMPONENTS;
3100: ---------------------------------------------------------------------------------------------
3101: --PROCEDURE: EVENT_ATTRIBUTE_UPDATION, new procedure to update event number on Event_Attribute
3102:
3103: PROCEDURE EVENT_ATTRIBUTE_UPDATION(X_Event_Num IN NUMBER,

Line 4061: GMS_BURDEN_COMPONENTS

4057: ,Burden_Cost_Code
4058: ,Expenditure_Org_Id
4059: ,sum(Amount)
4060: from
4061: GMS_BURDEN_COMPONENTS
4062: where
4063: award_project_id = X_Project_Id and
4064: request_id = X_Request_Id and
4065: event_type = decode(X_Calling_Process,'Revenue','REVENUE','Invoice','INVOICE') and

Line 4287: UPDATE_GMS_BURDEN_COMPONENTS(Evt_Num ,

4283:
4284: /* ------------------------------------------------------------------------------- */
4285: -- Updating Burden Components
4286:
4287: UPDATE_GMS_BURDEN_COMPONENTS(Evt_Num ,
4288: Ins_Award_Project_Id,
4289: X_Request_Id ,
4290: Ins_Actual_Project_Id ,
4291: Ins_Actual_Task_Id ,

Line 5034: INSERT_GMS_BURDEN_COMPONENTS(X_Project_Id,

5030: -- Rounding fix : Bug 1417062
5031: X_Burd_Amt_To_Insert_By_Comp := pa_currency.round_currency_amt(nvl(X_Burd_Amt_To_Insert_By_Comp,0));
5032:
5033:
5034: INSERT_GMS_BURDEN_COMPONENTS(X_Project_Id,
5035: X_Expenditure_Item_Id,
5036: X_Adl_Line_Num,
5037: X_Request_Id,
5038: X_Calling_Process,

Line 5929: INSERT_GMS_BURDEN_COMPONENTS(X_Project_Id,

5925:
5926: -- Rounding fix : Bug 1417062
5927: X_Rev_Burd_Amt_To_Ins_By_Comp := pa_currency.round_currency_amt(nvl(X_Rev_Burd_Amt_To_Ins_By_Comp,0));
5928:
5929: INSERT_GMS_BURDEN_COMPONENTS(X_Project_Id,
5930: X_Rev_Expenditure_Item_Id,
5931: X_Rev_Adl_Line_Num,
5932: X_Request_Id,
5933: X_Calling_Process,