Search Results igc_cc_headers_pkg




Overview

The APPS.IGC_CC_HEADERS_PKG package is a core PL/SQL component within the Oracle E-Business Suite Grants Accounting / Contracts (IGC) module, providing the fundamental data manipulation layer for Contract Commitment (CC) header records. It operates against the IGC_CC_HEADERS_ALL base table and serves as the primary API through which other IGC packages and forms create, modify, lock, and delete commitment header rows. Because it encapsulates the standard insert/update/delete logic against the header table, it acts as a low-level persistence service rather than a business-rules engine; validation and workflow orchestration are handled by the higher-level packages that call it. The package is classified under the APPS schema as an "OTHER" API type and carries a VALID status in both 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The ETRM metadata documents six procedures/functions, of which four are explicitly named. These four constitute the standard CRUD interface for CC headers:

  • INSERT_ROW — Creates a new commitment header record in IGC_CC_HEADERS_ALL. It is the entry point for registering a new contract commitment header, populating the mandatory columns and returning the surrogate key used by downstream detail-level processing.
  • LOCK_ROW — Acquires a row-level lock (SELECT FOR UPDATE) on a specified commitment header. This provides concurrency protection so that multiple concurrent processes cannot simultaneously modify the same header, ensuring transactional consistency during budgetary control, revaluation, and copy operations.
  • UPDATE_ROW — Modifies an existing commitment header record. It is invoked when header attributes change, such as status transitions, amounts, or currency-related fields, and is typically preceded by LOCK_ROW.
  • DELETE_ROW — Removes a commitment header (and by convention orchestrates the removal or archiving of dependent detail records). It is called during cancellation, rollback, or cleanup processing.

The remaining two undocumented members are not enumerated in the metadata excerpt and should be reviewed in the package specification before use.

Tables Accessed

The package primarily reads from and writes to IGC_CC_HEADERS_ALL, the master table for Contract Commitment headers, accessed through an APPS synonym. The broader table list documented for the package — including IGC_CC_ACCT_LINES, IGC_CC_ACTIONS, IGC_CC_DET_PF (detail performance obligations), IGC_CC_HEADER_HISTORY, and their multi-currency (MC_) counterparts — indicates that header persistence logic touches audit history and detail alignment records to maintain referential integrity. FND_APPLICATION is referenced to resolve application context, and IGC_CC_ACCESS supports security/access determination. The FND_API dependency confirms that the package uses the standard Oracle EBS API error-handling framework (FND_API.G_RET_STS_SUCCESS, FND_MSG_PUB messaging) to return status and error messages to callers.

Usage Notes

IGC_CC_HEADERS_PKG is not intended for direct invocation by end users. It is invoked programmatically by nine other packages, including IGC_CC_BUDGETARY_CTRL_PKG, IGC_CC_COPY_PKG, IGC_CC_REVALUE_PROCESS_PKG, IGC_CC_YEP_PROCESS_PKG, IGC_CC_MPFS_PROCESS_PKG, IGC_CC_OPEN_INTERFACE_PKG, and the IGC_CC_INT_CC_REL_PUB public API. These callers drive header maintenance during budgetary control checks, commitment revaluation, year-end processing, interface conversion, and copy operations. It may also be called from Oracle Forms-based CC header maintenance screens and from concurrent programs that import or reconcile commitment data. Custom extensions should call this package rather than issuing direct DML against IGC_CC_HEADERS_ALL to preserve audit history, locking semantics, and FND_API error propagation. All changes should be committed or rolled back by the calling transaction.