Search Results cc_det_pf




Overview
Explore in AI Chat

Overview

The APPS.IGC_CC_REP_YEP_PVT package body is a private (PVT-classified) PL/SQL implementation within the Oracle EBS Contracts and Commitments module (IGC). It supports the Commitment Control reporting and year-end processing (YEP) logic, which validates the state of commitments against their associated procurement and payables transactions. The package header declares a set of private helper routines that are not intended for direct customer invocation; they are called internally from other packages within the IGC suite. Environment-specific behaviour is controlled through the IGC_DEBUG_ENABLED profile option, which gates debug output, and internal counters such as g_line_num. The most recent source revision referenced is 120.7.12000000.10, dated 06-Dec-2007.

Key Procedures and Functions

The documented package exposes six procedures/functions:

  • LOCK_CC — Applies a locking operation against a commitment control header record, ensuring that concurrent year-end or reporting processes do not modify the same commitment simultaneously.
  • LOCK_PO — Provides the equivalent lock semantics for purchase order related records used in the commitment evaluation.
  • VALIDATE_CC — Performs validation of a commitment control record, checking that the underlying data is consistent before processing continues.
  • INVOICE_CANC_OR_PAID — Determines whether the invoices linked to a commitment have been cancelled or paid. The internal cursor c_invoices joins AP_INVOICE_DISTRIBUTIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL and IGC_CC_HEADERS, and the function counts cancelled versus approved invoices and distributions.
  • ENCUMBER_CC — Handles encumbrance-related processing for the commitment, interacting with the budget control parameters.
  • GET_BUDG_CTRL_PARAMS — Retrieves budget control parameters used to determine whether budget checking is enabled and how encumbrance should be treated.

Tables Accessed

The package reads and writes through APPS synonyms. Reference and transaction data are drawn from IGC_CC_HEADERS, IGC_CC_ACCT_LINES, IGC_CC_DET_PF, and IGC_CC_INTERFACE. Payables side data comes from AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL, while procurement data comes from PO_DISTRIBUTIONS_ALL and PO_HEADERS_ALL. Configuration and control settings are read from FINANCIALS_SYSTEM_PARAMS_ALL, IGC_CC_BC_ENABLE (budget control enablement), and IGC_CC_PROCESS_DATA. Exception records generated during processing are written to IGC_CC_PROCESS_EXCEPTIONS. The join between payables distributions and purchase order distributions via po_distribution_id, and then to PO_HEADERS_ALL using segment1 matched against cc_num, is central to the invoice evaluation logic.

Usage Notes

Because this is a private package, it is not exposed through standard Oracle EBS forms or concurrent program parameters. It is invoked indirectly by the five dependent packages that reference it. Typical execution paths are year-end commitment reporting or commitment control reconciliation routines, which call the locking, validation, encumbrance and invoice-evaluation routines in sequence. Deployments with custom extensions should call the public wrapper packages rather than this private body. Debug tracing can be enabled by setting the IGC_DEBUG_ENABLED profile option, which activates the internal debug line counter. The p_process_type parameter introduced in INVOICE_CANC_OR_APPROVED reflects a historical enhancement (bug 2098010) to allow the caller to distinguish processing contexts.