Results for “rel_detail_pf_entered_amount”

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

Overview

The view APPS.IGCFV_CC_REL_DET_PAY_FORECASTS is a reporting and integration object within the Oracle E-Business Suite (EBS) Contract Commitment module (product code IGC). It presents payment forecast records that represent release-level detail lines tied to their corresponding parent commitment lines. In the Contract Commitment data model, a parent account line may generate one or more released (child) detail payment forecast lines as commitments are drawn down, billed, or otherwise relieved against a contract. This view isolates those child records and simultaneously exposes both the child and parent identifiers, enabling downstream consumers to reconcile a release against the commitment from which it originated.

Because the view is defined WITH READ ONLY, it functions purely as a query surface — no DML is permitted through it. This makes it suitable for concurrent report programs, Discoverer workbooks, Oracle Business Intelligence Publisher (BI Publisher) data templates, and outbound integration extracts where a stable, read-consistent projection of release payment forecasts is required. The fact that it is owned by APPS and exposed as a documented ETRM object confirms it is treated as a supported interface rather than an incidental internal construct.

Underlying Base Objects

The view is constructed over two documented base objects, both referenced through APPS synonyms:

• IGC_CC_DET_PF — the Contract Commitment detail payment forecast table, which stores dated monetary forecast amounts at the detail line level.
• IGC_CC_ACCT_LINES — the Contract Commitment account line table, which anchors detail forecast lines to accounting distributions.

The underlying SQL self-joins IGC_CC_DET_PF to itself (aliased here as CCDPF for the release/child and CCDPFP for the parent), and joins IGC_CC_ACCT_LINES twice as well (IGCCAL for the release account line, IGCCALP for the parent account line). The join conditions enforce that a release line is only returned when it has a non-null PARENT_ACCT_LINE_ID and a non-null PARENT_DET_PF_LINE_ID, effectively filtering the result set to genuine parent-child relationships and excluding standalone forecast lines.

Key Columns

• RELEASE_DETAIL_PF_LINE_NUMBER / RELEASE_DETAIL_PF_LINE_ID — the line number and primary key of the child (release) payment forecast line.
• RELEASE_DETAIL_PF_DATE — the forecast date carried on the release line, typically the period against which the amount is projected.
• REL_DETAIL_PF_ENTERED_AMOUNT, REL_DET_PF_FUNCTIONAL_AMOUNT, REL_DETAIL_PF_BILLED_AMOUNT, REL_DET_PF_UNBILLED_AMOUNT — the entered, functional, billed, and unbilled monetary values of the release forecast, allowing currency-aware and billing-status-aware analysis.
• RELEASE_ACCOUNT_LINE_NUMBER / RELEASE_ACCOUNT_LINE_ID — the account line to which the release forecast belongs.
• PARENT_DETAIL_PF_LINE_NUMBER / PARENT_DETAIL_PF_LINE_ID and PARENT_ACCOUNT_LINE_NUMBER / PARENT_ACCOUNT_LINE_ID — the identifiers of the originating parent forecast and account line, enabling upward reconciliation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns for lineage and change tracking.
• "_DF" — a descriptive flexfield discriminator literal (_DF:IGC:IGC_CC_DET_PFS:CCDPF) used by the EBS framework to resolve the correct DFF context for the detail payment forecasts entity.

Common Use Cases and Queries

Typical scenarios include reconciling released amounts against parent commitments, reporting unbilled versus billed forecast balances, and extracting release-level forecasts into a data warehouse.

SELECT release_detail_pf_line_number,
       release_detail_pf_date,
       rel_det_pf_functional_amount,
       rel_det_pf_billed_amount,
       rel_det_pf_unbilled_amount,
       parent_detail_pf_line_number,
       parent_account_line_number
  FROM apps.igcfv_cc_rel_det_pay_forecasts
 WHERE release_detail_pf_date BETWEEN :p_from_date AND :p_to_date
 ORDER BY parent_account_line_number, release_detail_pf_date;

A second common pattern aggregates unbilled exposure by parent commitment:

SELECT parent_detail_pf_line_number,
       SUM(rel_det_pf_unbilled_amount) total_unbilled
  FROM apps.igcfv_cc_rel_det_pay_forecasts
 GROUP BY parent_detail_pf_line_number;

All queries should filter or join on the parent identifiers, since the view already restricts output to release lines with valid parents. Given the APPS ownership and read-only nature of the view, it is safe to query directly from custom reports and integration jobs without risk of mutating contract commitment data.