Search Results igc_cc_headers_s




Overview

The APPS.IGC_CC_INT_CC_REL_PUB package body is a public (PUB-classified) PL/SQL API within the Oracle E-Business Suite Contracts Intelligence (IGC) application, specifically the Contracts Commitment (CC) module. Its principal business function is to create and persist contract commitment release records from validated interface staging data, thereby converting transient commitment-invoice relationships into durable, queryable transactions within the IGC commitment schema. In the context of Oracle EBS 12.1.1 and 12.2.2, this package acts as the finalization layer that writes commitment header, accounting line, and detail distribution records that downstream inquiry forms, funds-check logic, and reporting rely upon.

The object is documented as VALID and holds a status characteristic of a shipped, supported Oracle-delivered package. It is not referenced by any other database object, indicating it is invoked as an entry point rather than as an internal dependency — typically from concurrent processing or from calling PL/SQL in the commitment integration flow associated with the IGC_CC_HEADERS_S and related _S (sequence/interface) objects that the search term references.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package:

  • CREATE_RELEASES — The sole documented entry point. It is responsible for creating contract commitment release records. In practice, this procedure consumes previously staged commitment data, resolves the associated accounting and detail distributions, and inserts the resulting release rows into the commitment tables. Parameter lists are not enumerated in the documented metadata and are therefore not reproduced here; the procedure should be treated as the packaged API surface for commit-release creation rather than as a row-level utility.

Tables Accessed

The package reads and writes a documented set of tables accessed through APPS synonyms:

Supporting infrastructure dependencies include FND_API, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, and FND_LOG, which together provide the standard EBS API error-handling, message-stack, profile, and debug logging framework. IGC_CC_PO_INTERFACE_PKG is also referenced, indicating integration with the commitment-to-Purchase-Order interface flow.

Usage Notes

This package is invoked programmatically rather than interactively. Typical callers are concurrent programs and internal IGC integration routines that process commitment release transactions imported from external systems or generated by Payables/Procurement activity. Custom extensions should call CREATE_RELEASES through the standard FND_API conventions, initializing the message stack (via FND_MSG_PUB) before invocation and inspecting the returned API status rather than relying on exceptions. Because the package is not referenced by any other database object, it is safe to treat it as a top-level API entry point; however, since it writes to core commitment tables, it should never be called outside a committed transaction boundary without explicit savepoint management. Debug output can be enabled through the FND_LOG/FND_PROFILE logging facilities for troubleshooting release-creation failures.