Results for “igc_cc_comp_amt_pkg”

50+ results




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

Overview

IGC_CC_COMP_AMT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports Oracle Grants/Contracts (IGC) award and contract billing computations. Its central purpose is to derive billed and functional billed amounts for cost-to-cost (CC) processing lines used by the Contract Commitment and award billing engines. The package resolves amounts at three distinct levels of granularity: the project funding detail line (PF line), the accounting line, and the header, and returns both transactional currency and functional currency values.

The package is classified as API category "OTHER" in the ETRM repository. It provides a functional abstraction layer over IGC burden, billing, and distribution data, so callers do not need to reconstruct the joins between award cost lines, purchasing distributions, and invoice distributions. A characteristic of this package is the return-value function pattern: each documented entry point is a FUNCTION rather than a procedure, and the pragma lines in the source indicate the original intent to declare restricted purity (WNDS, WNPS), which confirms that these functions are intended to be side-effect-free read routines. The header comment identifies the source file as IGCCCBAS.pls, version 120.4.

Key Procedures and Functions

The package exposes seven documented functions, organized by the amount dimension they compute.

  • COMPUTE_PF_BILLED_AMT — Returns the billed amount for a given project funding detail line, identified by the PF line ID, PF line number, and the associated accounting line. This is the base transactional-currency billed amount at the PF-line level.
  • COMPUTE_PF_FUNC_BILLED_AMT — Returns the functional (ledger) currency equivalent of the PF-line billed amount. This is the function most commonly associated with the search term the user submitted and is the functional-currency counterpart to COMPUTE_PF_BILLED_AMT.
  • COMPUTE_ACCT_BILLED_AMT — Returns the billed amount aggregated to the accounting line level. It accepts only the accounting line identifier.
  • COMPUTE_ACCT_FUNC_BILLED_AMT — Returns the functional currency billed amount at the accounting line level.
  • COMPUTE_FUNCTIONAL_AMT — Converts an amount supplied with a contract header identifier into functional currency, using the header's currency and rate attributes. This is the general-purpose currency conversion helper used by the other functions.
  • COMPUTE_PF_BILL_AMT_CURR — Returns the PF-line bill amount expressed in a specified or derived currency, supporting multi-currency awards.
  • COMPUTE_ACCT_BILLED_AMT_CURR — Returns the accounting-line billed amount in its transactional currency, parallel to COMPUTE_ACCT_BILLED_AMT for functional display.

Tables Accessed

The package reads several base and grants-specific tables through APPS synonyms. On the purchasing side, it references PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL to retrieve the committed and distributed purchasing amounts that underlie the billed quantity. On the payables side, AP_INVOICE_DISTRIBUTIONS_ALL supplies the invoice-matched amounts that constitute actual billed cost. The IGC-specific tables IGC_CC_HEADERS, IGC_CC_DET_PF, and IGC_CC_ACCT_LINES provide the header, project funding detail, and accounting line structures that define the CC computation context and link the purchasing and payables data to the award.

Usage Notes

This package is invoked by the IGC cost-to-cost billing engine and is referenced by nine other packages in the ETRM repository, indicating it is a shared utility rather than a standalone API. It is typically called from concurrent programs and forms that display or process award billing amounts, and from custom extensions requiring functional-currency billed amounts for a PF or accounting line. Because the functions are read-only by design, they are safe to call from reporting and inquiry code. Consumers should treat all entry points as internal, as they are not published APIs and their signatures may change across releases. Under 12.1.1 and 12.2.2, behavior is consistent; the primary 12.2 consideration is the Online Patching editioning model applied to the APPS schema, which is transparent to callers.