Results for “func_billed_amt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGC_CC_DET_PF_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGC.IGC_CC_DET_PF_V. It belongs to the Oracle Enterprise Trade Management (ETRM) product family and specifically supports the Contract Commitment detail payment forecast functionality. In Oracle's documented object model the view is explicitly designated as a "supplementary view used to simplify forms coding," carrying the standard Oracle warning that it is not intended as a public query or DML interface and may change substantially between minor or major releases.

Functionally, the view presents detail-level payment forecast rows enriched with commitment accounting context. Where the base detail payment forecast table (IGC_CC_DET_PF) holds the raw forecast line records, this view joins accounting-line information from IGC_CC_ACCT_LINES and derives computed amounts through the IGC_CC_COMP_AMT_PKG package, producing a consolidated projection suitable for form display and, in practice, for reporting on committed versus billed amounts. The column most frequently referenced by implementers—CC_DET_PF_FUNC_BILLED_AMT—exposes the functional-currency billed portion of each payment forecast line, which is the figure users typically reconcile against invoice and payment activity.

Underlying Base Objects

The documented dependency list for IGC_CC_DET_PF_V identifies three referenced objects:

• IGC_CC_DET_PF (synonym) — the primary detail payment forecast base table supplying the line identifiers, entered and functional amounts, forecast dates, encumbrance attributes, and the descriptive flexfield context and attribute columns (ATTRIBUTEn, 150 characters each).
• IGC_CC_ACCT_LINES (synonym) — the commitment accounting line source, providing the CC_ACCT_LINE_ID / CC_ACCT_LINE_NUM linkage and parent account line relationships used to tie forecast lines to their accounting distribution.
• IGC_CC_COMP_AMT_PKG (package) — the PL/SQL package invoked to compute derived commitment amounts such as the comparable functional amount (CC_DET_PF_COMP_FUNC_AMT, documented as the "detail payment forecast functional line amount").

Because the view resolves through synonyms, it depends on the underlying IGC base tables rather than on private copies, and any structural change to those tables propagates directly to the view definition.

Key Columns

• CC_DET_PF_LINE_ID / CC_DET_PF_LINE_NUM — unique and sequential identifiers for the detail payment forecast line; the parent variants (PARENT_DET_PF_LINE_ID, PARENT_DET_PF_LINE_NUM) establish the hierarchy for rolled-up forecasts.
• CC_ACCT_LINE_ID / CC_ACCT_LINE_NUM / PARENT_ACCT_LINE_ID — the link into commitment accounting lines, enabling reconciliation of forecast amounts to accounted distributions.
• CC_DET_PF_ENTERED_AMT, CC_DET_PF_FUNC_AMT, CC_DET_PF_COMP_FUNC_AMT — entered-currency amount, functional-currency amount, and the package-computed comparable functional amount respectively.
• CC_DET_PF_BILLED_AMT and CC_DET_PF_FUNC_BILLED_AMT — the billed portion of the line in entered and functional currency; the functional billed amount is the column most commonly targeted when users need to compare forecasted spend against actual billed commitment.
• CC_DET_PF_UNBILLED_AMT — the residual unbilled balance of the forecast line, computed as forecast less billed.
• CC_DET_PF_ENCMBRNC_AMT, CC_DET_PF_UNENCMBRD_AMT, CC_DET_PF_ENCMBRNC_DATE, CC_DET_PF_ENCMBRNC_STATUS — encumbrance and unencumbered balances together with the encumbrance date and status, supporting funds-check analysis.
• CC_DET_PF_DATE — the forecast date used for period and cash-flow bucketing.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments, each VARCHAR2(150), allowing site-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — standard WHO audit columns identifying the last change to the row.

Common Use Cases and Queries

Typical scenarios include payment forecast reporting by period, billed-versus-forecast variance analysis, and encumbrance reconciliation for commitment-controlled contracts. Because the view is a forms-support view, queries should be read-only and version-pinned to the current release.

Sample query retrieving billed amounts and unbilled balances by forecast date:

• SELECT cc_det_pf_line_num, cc_det_pf_date, cc_det_pf_func_amt, cc_det_pf_func_billed_amt, cc_det_pf_unbilled_amt FROM apps.igc_cc_det_pf_v WHERE cc_det_pf_encmbrnc_status = 'O' ORDER BY cc_det_pf_date;

A variance query comparing functional forecast to functional billed amount:

• SELECT cc_det_pf_line_num, cc_det_pf_func_amt - cc_det_pf_func_billed_amt AS variance FROM apps.igc_cc_det_pf_v WHERE cc_det_pf_func_billed_amt IS NOT NULL;

Joining back to accounting lines for distribution-level detail:

• SELECT v.cc_det_pf_line_num, v.cc_acct_line_num, v.cc_det_pf_func_billed_amt FROM apps.igc_cc_det_pf_v v WHERE v.cc_acct_line_id IS NOT NULL;

For production reporting, Oracle recommends building custom extracts against the underlying IGC base tables via the supported public APIs, reserving IGC_CC_DET_PF_V for diagnostic and form-equivalent queries only.