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_BGT_BASELINE_PKG dependencies on PA_BC_PACKETS

Line 39: --then we have to delete from pa_bc_packets all the transactions that were created

35: where project_id = p_project_id
36: for update nowait;
37:
38: --When baselining errors with oracle error, insufficient funds and if user rebaselines
39: --then we have to delete from pa_bc_packets all the transactions that were created
40: --during the first baseline. The cursor below is for this purpose
41: -- R12 Funds Management Uptake : Obsolete logic with new architecture
42:
43: --Cursor to update status code from C to A for packets that have been funds checked

Line 48: -- procedure to create pa_bc_balances records from PA_BUDGET_LINES and to clean up PA_BC_PACKETS

44: --before the budget baselining notification was approved
45: -- R12 Funds Management Uptake : Obsolete cursor c_updsts with new architecture
46:
47: ---------------------------------------------------------------------------------------------
48: -- procedure to create pa_bc_balances records from PA_BUDGET_LINES and to clean up PA_BC_PACKETS
49: /* ========================================================================================== +
50: FOLLOWING CODE MOVED TO PA_BUDGET_FUND_PKG (PABBFNDB.pls)
51:
52: PROCEDURE INSERT_BGT_BALANCES(

Line 668: -- into pa_bc_packets for funds check

664: END is_fc_required;
665: -------------------------------------------------------------------------------
666:
667: -- procedure to load all the vendor invoices, expense reports and BTC transactions
668: -- into pa_bc_packets for funds check
669: PROCEDURE INSERT_VI_ER_BTC_TXNS(
670: p_packet_id IN NUMBER,
671: p_sob_id IN NUMBER,
672: p_project_id IN NUMBER,

Line 1036: insert into pa_bc_packets (

1032: IF P_DEBUG_MODE = 'Y' THEN
1033: pa_fck_util.debug_msg('MAINTAIN_BAL_FCHK: ' || 'Before inserting VIERBTC');
1034: END IF;
1035: FORALL m in l_ExpProjTab.FIRST..l_ExpProjTab.LAST
1036: insert into pa_bc_packets (
1037: PACKET_ID,
1038: PROJECT_ID,
1039: TASK_ID,
1040: EXPENDITURE_TYPE,

Line 1108: pa_bc_packets_s.nextval,

1104: l_ExpEntCrTab(m),
1105: l_ExpAcctDrTab(m),
1106: l_ExpAcctCrTab(m),
1107: p_budget_version_id,
1108: pa_bc_packets_s.nextval,
1109: 'B',
1110: --PA.M insert parent bc pkt as -99 for CWK BTC EIs
1111: --null,
1112: l_ExpParBcPktIdTab(m),

Line 1159: -- procedure to load all commitment transactions in pa_bc_packets for funds check

1155: RAISE;
1156: END INSERT_VI_ER_BTC_TXNS;
1157: ---------------------------------------------------------------------------------------------
1158:
1159: -- procedure to load all commitment transactions in pa_bc_packets for funds check
1160: PROCEDURE INSERT_COMMITMENT_TXNS(
1161: p_packet_id IN NUMBER,
1162: p_sob_id IN NUMBER,
1163: p_project_id IN NUMBER,

Line 1367: --pa_bc_packets. Also if budget is linked then consider only open period

1363: exit;
1364: END IF;
1365:
1366: --If budgetary control type is CC, then load only contract commitment transactions into
1367: --pa_bc_packets. Also if budget is linked then consider only open period
1368: --transactions else consider all transactions.
1369: IF P_DEBUG_MODE = 'Y' THEN
1370: pa_fck_util.debug_msg('MAINTAIN_BAL_FCHK: ' || 'No. of rec in c_bc_comm = '|| l_ProjTab.count);
1371: END IF;

Line 1388: insert into pa_bc_packets (

1384: IF P_DEBUG_MODE = 'Y' THEN
1385: pa_fck_util.debug_msg('MAINTAIN_BAL_FCHK: ' || 'Bdgt Intg Flag = Y');
1386: END IF;
1387: FORALL i in l_ProjTab.FIRST..l_ProjTab.LAST
1388: insert into pa_bc_packets (
1389: PACKET_ID,
1390: PROJECT_ID,
1391: TASK_ID,
1392: EXPENDITURE_TYPE,

Line 1509: insert into pa_bc_packets (

1505: pa_fck_util.debug_msg('MAINTAIN_BAL_FCHK: ' || 'Bdgt Intg Flag = N');
1506: END IF;
1507:
1508: FORALL j in l_ProjTab.FIRST..l_ProjTab.LAST
1509: insert into pa_bc_packets (
1510: PACKET_ID,
1511: PROJECT_ID,
1512: TASK_ID,
1513: EXPENDITURE_TYPE,

Line 1620: --(AP, PO, REQ, Contract Payments) into pa_bc_packets.

1616: END IF;
1617: PA_DEBUG.Reset_Err_Stack; --3912094
1618:
1619: --If budgetary control type is GL, then load all commitment transactions
1620: --(AP, PO, REQ, Contract Payments) into pa_bc_packets.
1621: --Also check if budget is linked then consider only open period
1622: --transactions else consider all transactions.
1623: ELSIF (p_bdgt_ctrl_type = ('GL')) THEN
1624:

Line 1640: insert into pa_bc_packets (

1636:
1637: --For Other commitment transactions (AP,PO,REQ,CC_P_PAY,CC_C_PAY)
1638: --when there is a link
1639: FORALL k in l_ProjTab.FIRST..l_ProjTab.LAST
1640: insert into pa_bc_packets (
1641: PACKET_ID,
1642: PROJECT_ID,
1643: TASK_ID,
1644: EXPENDITURE_TYPE,

Line 1762: insert into pa_bc_packets (

1758:
1759: --For Other commitment transactions (AP,PO,REQ,CC_C_PAY,CC_P_PAY)
1760: --when there is a link
1761: FORALL l in l_ProjTab.FIRST..l_ProjTab.LAST
1762: insert into pa_bc_packets (
1763: PACKET_ID,
1764: PROJECT_ID,
1765: TASK_ID,
1766: EXPENDITURE_TYPE,

Line 1944: --pa_bc_packets

1940: /* =============================================================================================== +
1941: FOLLOWING CODE MOVED TO PA_BUDGET_FUND_PKG (PABBFNDB.pls)
1942:
1943: --Before start of baselining call sweeper to sweep approved packets sitting in
1944: --pa_bc_packets
1945: --Bug 2779986: Run sweeper irrespective of the p_bdgt_ctrl_type
1946: --Revert Bug 2779986 fix: Sweeper process is to be run only the first time this API is
1947: --called from PA_BUDGET_FUNDS_PKG. There are 2 calls to this API, first for
1948: --for p_bdgt_ctrl_type = GL and then for p_bdgt_ctrl_type = CC, hence running the

Line 2002: -- lying in pa_bc_packets and sweeper will clean the 'R' and 'T' status records.

1998: -- if user rebaselines.
1999: -- With new architecture baselining is performed before fundscheck and fundscheck
2000: -- is fired only during baselining for the newly baselined version.If fundscheck fails
2001: -- then baselining will be rolled back and hence there wont be any 'B' status data
2002: -- lying in pa_bc_packets and sweeper will clean the 'R' and 'T' status records.
2003:
2004: -- R12 Funds Management Uptake : Removed check of 'IF fc required'
2005:
2006: -- Get a new packet id

Line 2015: -- Insert commitments into PA_BC_PACKETS

2011: END IF;
2012:
2013: PA_DEBUG.set_err_stack('M:Create Dir Cost');
2014:
2015: -- Insert commitments into PA_BC_PACKETS
2016: IF P_DEBUG_MODE = 'Y' THEN
2017: pa_fck_util.debug_msg('MAINTAIN_BAL_FCHK: ' || 'Calling Insert Commitment Txns');
2018: END IF;
2019:

Line 2122: -- R12 Funds Management Uptake : Added below update for updating pa_bc_packets with

2118:
2119: -- R12 Funds Management Uptake : Deleted call to PA_FUNDS_CONTROL_PKG.upd_bdgt_encum_bal
2120: -- as it will be fired during tieback .
2121:
2122: -- R12 Funds Management Uptake : Added below update for updating pa_bc_packets with
2123: -- uncommited newly created budget version id.
2124:
2125: If l_return_status not in ('F','T') then
2126:

Line 2127: UPDATE pa_bc_packets

2123: -- uncommited newly created budget version id.
2124:
2125: If l_return_status not in ('F','T') then
2126:
2127: UPDATE pa_bc_packets
2128: SET budget_version_id = p_baselined_budget_version_id
2129: WHERE packet_id = l_packet_id
2130: AND budget_version_id = p_budget_version_id;
2131: