Results for “igcbv_cc_rel_sum_pay_forecasts”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view IGCBV_CC_REL_SUM_PAY_FORECASTS is a read-only reporting object owned by the APPS schema within the Oracle E-Business Suite IGC – Contract Commitment product family. It presents aggregated, release-level payment forecast amounts for contract commitments, rolled up by GL period year, parent contract commitment, parent account line, release contract commitment, and release account line. The view is intended for inquiry and reporting rather than transaction processing; its definition concludes with WITH READ ONLY, which raises an exception on any attempted DML against it.
Functionally, the view answers the question: for a given release of a contract commitment, how much has been forecast at the entered, functional, billed, unbilled, and encumbered levels within each accounting period? Analysts searching for the column token rel_sum_pf_functional_amount will find that it corresponds to the view column REL_SUM_PF_FUNCTIONAL_AMOUNT, the functional-currency sum of the detail payment forecast amounts. This makes the view a convenient single source for period-level commitment forecasting totals without joining and re-aggregating the underlying detail tables manually.
Underlying Base Objects
Per the documented metadata, the view is defined over the following referenced objects, all exposed through APPS synonyms:
- IGC_CC_DET_PF (aliased CCDPF) – the contract commitment detail payment forecast table. This is the primary source of all monetary measures and also supplies the date used to resolve the GL period.
- IGC_CC_ACCT_LINES (aliased IGCCAL) – the contract commitment account lines. It provides
PARENT_HEADER_ID,CC_HEADER_ID, and the account-line join key. - IGC_CC_PERIODS_ALL (aliased CCP) – the contract commitment periods, supplying the period name, period set name, and organization identifier that constrain the GL period lookup.
- GL_PERIODS – the General Ledger period calendar. It supplies
PERIOD_YEARand the start and end dates used to bound payment forecast dates.
The joins are: CCDPF.CC_ACCT_LINE_ID = IGCCAL.CC_ACCT_LINE_ID; CCDPF.CC_DET_PF_DATE BETWEEN GL_PERIODS.START_DATE AND GL_PERIODS.END_DATE; and CCP.PERIOD_NAME = GL_PERIODS.PERIOD_NAME together with CCP.PERIOD_SET_NAME = GL_PERIODS.PERIOD_SET_NAME. The result set is grouped by organization, period year, parent header, parent account line, release header, and release account line.
Key Columns
- REL_SUMMARY_PF_ENTERED_AMOUNT – sum of entered-currency payment forecast amounts.
- REL_SUM_PF_FUNCTIONAL_AMOUNT – sum of functional-currency payment forecast amounts; the token
rel_sum_pf_functional_amountmaps here. - REL_SUMMARY_PF_BILLED_AMOUNT – sum of billed forecast amounts.
- REL_SUMMARY_PF_UNBILLED_AMOUNT – sum of unbilled forecast amounts.
- RELEASE_SUM_PF_ENCUMBER_AMOUNT – sum of encumbered forecast amounts for the release.
- PERIOD_YEAR – GL period year derived from GL_PERIODS, enabling year-level rollups.
- PARENT_CONTRACT_COMMITMENT_ID, PARENT_ACCOUNT_LINE_ID – identify the parent commitment and its account line.
- RELEASE_CONTRACT_COMMITMENT_ID, RELEASE_ACCOUNT_LINE_ID – identify the release-level commitment and account line being summarized.
- ORGANIZATION_ID – operating unit / organization context taken from IGC_CC_PERIODS_ALL.
Common Use Cases and Queries
Typical uses include commitment release reporting, period-by-period forecast analysis, encumbrance reconciliation, and feeds into custom dashboards or extracts. A representative query filtering by release and year:
- Release forecast by functional amount:
SELECT release_contract_commitment_id, period_year,
rel_sum_pf_functional_amount, release_sum_pf_encumber_amount
FROM apps.igcbv_cc_rel_sum_pay_forecasts
WHERE organization_id = :p_org_id
AND period_year = :p_year
ORDER BY release_contract_commitment_id, period_year; - Parent-level rollup: aggregate
REL_SUM_PF_FUNCTIONAL_AMOUNTgrouped byPARENT_CONTRACT_COMMITMENT_IDandPERIOD_YEARto compare parent commitments across periods. - Billed versus unbilled reconciliation: compare
REL_SUMMARY_PF_BILLED_AMOUNTandREL_SUMMARY_PF_UNBILLED_AMOUNTper release account line to validate forecast consumption.
Because the view pre-aggregates at the documented grouping level, joins back to IGC_CC_ACCT_LINES or IGC_CC_DET_PF should be performed on the matching identifier combinations to avoid fan-out.
-
APPS.IGCBV_CC_REL_SUM_PAY_FORECASTS·↳ GL_PERIODS·↳ IGC_CC_ACCT_LINES·↳ IGC_CC_DET_PF·Explore IGC module →
-
APPS.IGCBV_CC_REL_SUM_PAY_FORECASTS·↳ GL_PERIODS·↳ IGC_CC_ACCT_LINES·↳ IGC_CC_DET_PF·Explore IGC module →
-
SYNONYM: APPS.IGC_CC_DET_PF 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.IGC_CC_DET_PF 12.1.1
-
SYNONYM: APPS.GL_PERIODS 12.2.2
-
SYNONYM: APPS.GL_PERIODS 12.1.1
-
eTRM - IGC Tables and Views 12.2.2
System parameters for contracts
-
eTRM - IGC Tables and Views 12.1.1
System parameters for contracts
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGC Tables and Views 12.1.1
System parameters for contracts
-
eTRM - IGC Tables and Views 12.2.2
System parameters for contracts