Search Results lock_po




Overview
Explore in AI Chat

Overview

IGC_CC_REP_YEP_PVT is a private PL/SQL package owned by the APPS schema within the Oracle E-Business Suite. The suffix "PVT" indicates that the package is classified as private, meaning it is not exposed as a public API and is intended for internal use by other packages within the same product family. The package belongs to the IGC (Grants/Contracts/Commitment Control) module and supports Year-End Processing (YEP) activities tied to Commitment Control (CC) records.

Its business purpose is to orchestrate the validation, locking, encumbrance generation, and budgetary control verification steps required when closing or rolling forward commitment control data at fiscal year end. The package coordinates activity across Grants, Purchasing, Payables, and Financials system parameters, ensuring that encumbrances are properly identified, locked against conflicting updates, and processed under the correct budgetary control settings. Because the object is a private package, its routines are invoked by higher-level public APIs and concurrent programs rather than by end users directly.

Key Procedures and Functions

  • LOCK_CC — Acquires a lock on a commitment control header record, preventing concurrent modification during year-end processing.
  • LOCK_PO — Acquires a lock on the associated purchase order data tied to a commitment control header. This is the routine most relevant to the search term "lock_po," and it safeguards the PO record while encumbrance processing proceeds.
  • VALIDATE_CC — Validates a commitment control record for a specified process type, process phase, fiscal year, set of books, and operating unit, returning a status message. It checks the record against configuration flags such as the provisional encumbrance setting and the request identifier.
  • INVOICE_CANC_OR_PAID — Determines whether an invoice associated with the commitment control header has been cancelled or paid, a prerequisite for certain closing actions.
  • ENCUMBER_CC — Drives the encumbrance creation logic for a commitment control record, applying budgetary control flags (summary, detail, provisional, and confirmed), currency and rate information, and year start/end dates. Note that SLA uptake (Bug 6341012) removed the encumbrance type parameters, reflecting the shift to Subledger Accounting.
  • GET_BUDG_CTRL_PARAMS — Retrieves budgetary control parameters for a given set of books and operating unit, returning currency code, summary/detail control flags, provisional and confirmed encumbrance settings, and message diagnostics.

Tables Accessed

The package reads and writes across several product schemas via APPS synonyms. Core commitment control data resides in IGC_CC_HEADERS, IGC_CC_DET_PF, IGC_CC_ACCT_LINES, IGC_CC_INTERFACE, IGC_CC_PROCESS_DATA, IGC_CC_PROCESS_EXCEPTIONS, and IGC_CC_BC_ENABLE. Purchasing information is drawn from PO_HEADERS_ALL and PO_DISTRIBUTIONS_ALL to support the LOCK_PO and encumbrance routines. Payables data comes from AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL for cancelled/paid invoice determination. FINANCIALS_SYSTEM_PARAMS_ALL supplies budgetary control configuration consumed by GET_BUDG_CTRL_PARAMS.

Usage Notes

IGC_CC_REP_YEP_PVT is referenced by five other packages, indicating it is a subordinate component of a larger year-end processing flow. It is typically invoked from concurrent programs and public wrapper APIs that manage commitment control reconciliation. Custom code should not call this package directly because its interface is private and subject to change. The LOCK_PO function in particular is called during YEP to prevent concurrent PO updates while encumbrances are being adjusted. The package header carries a legacy revision string (120.3.12000000.4, dated 2007), and its design predates but has been adapted for SLA uptake in Release 12.