APPS.GMS_WF_PKG dependencies on GMS_COMMITMENT_ENCUMBERED_V

Line 74: -- a join with gms_commitment_encumbered_v .

70: -- Bug 3465169 : This function returns the Burden amount calculated
71: -- for input parameters burdenable_raw_cost,expenditure_type
72: -- organization_id and ind_compiled_set_id.
73: -- This is introduced for performance fix inorder to avoid
74: -- a join with gms_commitment_encumbered_v .
75:
76: FUNCTION Get_Burden_amount (p_expenditure_type VARCHAR2,
77: p_organization_id NUMBER,
78: p_ind_compiled_set_id NUMBER,

Line 2848: -- fires gms_commitment_encumbered_v twice i.e once for fetching raw line

2844:
2845: /*
2846: -- Bug 3465169 : Modified the below sql to fix issue 'Sharable memory is greater than 1000000.'
2847: -- Fix : The below cursor was using gms_status_commitments_v which inturn
2848: -- fires gms_commitment_encumbered_v twice i.e once for fetching raw line
2849: -- and once for burden line.
2850: -- Hence modified the sql to directly use gms_status_commitments_v for fetching
2851: -- raw data and calculate burden for each raw line.
2852: -- The option of directly calling base tables was not feasible as there was

Line 2893: FROM gms_commitment_encumbered_v cmt

2889: )
2890: )
2891: )
2892: )
2893: FROM gms_commitment_encumbered_v cmt
2894: WHERE cmt.award_id = p_award_id
2895: AND (cmt.project_id,cmt.task_id) IN (SELECT gmpf.project_id,nvl(gmpf.task_id,cmt.task_id)
2896: FROM gms_summary_project_fundings gmpf
2897: WHERE gmpf.installment_id =p_installment_id )