DBA Data[Home] [Help]

APPS.GMS_COST_PLUS_EXTN dependencies on STANDARD

Line 2016: -- now new standard AP gets in lets say +1000, The total is still

2012: -- INFORMATION :
2013: -- The following IF codition - PURPOSE
2014: -- Let say AP has credit memo of -50,000 for the same award
2015: -- and expenditures, so AP_RAW_COST = -50,000 and AP_BURDEN = 0
2016: -- now new standard AP gets in lets say +1000, The total is still
2017: -- -49,000. Since AP can becomes actuals and we don't want to get
2018: -- in a situation where Raw cost is -Ve and Burden is +Ve.
2019: -- Thats why we calculates Zero Burden for this scenario.
2020: -- This is true for any type of transaction entry. i.e. AP, PO, REQ

Line 2712: -- Defaulting as a standard AP.

2708: bc_pkt_rec := p_record ;
2709: bc_pkt_rec.entered_cr := nvl(bc_pkt_rec.entered_cr,0) ;
2710: bc_pkt_rec.entered_dr := nvl(bc_pkt_rec.entered_dr,0) ;
2711: -- ------------------------------
2712: -- Defaulting as a standard AP.
2713: -- ------------------------------
2714: X_AP_TYPE := 'STD' ;
2715:
2716: if bc_pkt_rec.entered_cr <> 0 then

Line 2730: -- 2.4 - Standard AP.

2726: -- 2. IDC Limit Scenarios.
2727: -- 2.1 - Credit Memo.
2728: -- 2.2 - Debit Memo.
2729: -- 2.3 - Cancelled AP
2730: -- 2.4 - Standard AP.
2731: -- -----------------------------------------
2732: -- ----------------------------------------------
2733: -- CASE 2.3 - Cancelled AP or AP with ZERO
2734: -- Raw cost.