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:
- IGC_CC_HEADERS and IGC_CC_HEADERS_S — the commitment header entities; the
_Sobject represents the interface/sequence counterpart used to source or stage header data, withIGC_CC_HEADERS_PKGproviding the surrounding business logic. - IGC_CC_ACCT_LINES, IGC_CC_ACCT_LINES_S, and IGC_CC_ACCT_LINES_PKG — commitment accounting distribution lines, including their staged/interface form and supporting package logic.
- IGC_CC_DET_PF, IGC_CC_DET_PF_S, and IGC_CC_DET_PF_PKG — commitment detail distribution (detail performance/accounting) records.
- IGC_CC_SYSTEM_OPTIONS_ALL and IGC_CC_SYSTEM_OPTIONS_PKG — system option and profile-driven configuration values that govern processing behavior.
- AP_INVOICES_ALL — the Payables invoice source, linking commitment releases to the invoices that originate or consume them.
- FND_LOGINS, FND_USER — audit/identity resolution for who initiated the release creation, supporting Oracle's who columns and logging conventions.
- DUAL — standard single-row utility access.
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.
-
SEQUENCE: IGC.IGC_CC_HEADERS_S
12.2.2
owner:IGC, object_type:SEQUENCE, object_name:IGC_CC_HEADERS_S, status:VALID,
-
SEQUENCE: IGC.IGC_CC_HEADERS_S
12.1.1
owner:IGC, object_type:SEQUENCE, object_name:IGC_CC_HEADERS_S, status:VALID,
-
SYNONYM: APPS.IGC_CC_HEADERS_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IGC_CC_HEADERS_S, status:VALID,
-
SYNONYM: APPS.IGC_CC_HEADERS_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IGC_CC_HEADERS_S, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.IGC_CC_INT_CC_REL_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:IGC_CC_INT_CC_REL_PUB, status:VALID,
-
PACKAGE BODY: APPS.IGC_CC_OPN_UPD_GET_LNK_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:IGC_CC_OPN_UPD_GET_LNK_PUB, status:VALID,
-
PACKAGE BODY: APPS.IGC_CC_INT_CC_REL_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:IGC_CC_INT_CC_REL_PUB, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.IGC_CC_OPN_UPD_GET_LNK_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:IGC_CC_OPN_UPD_GET_LNK_PUB, status:VALID,
-
PACKAGE BODY: APPS.IGC_CC_OPEN_INTERFACE_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:IGC_CC_OPEN_INTERFACE_PKG, status:VALID,
-
PACKAGE BODY: APPS.IGC_CC_OPEN_INTERFACE_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:IGC_CC_OPEN_INTERFACE_PKG, status:VALID,
-
APPS.IGC_CC_INT_CC_REL_PUB dependencies on IGC_CC_HEADERS_S
12.2.2
-
APPS.IGC_CC_INT_CC_REL_PUB dependencies on IGC_CC_HEADERS_S
12.1.1
-
APPS.IGC_CC_OPEN_INTERFACE_PKG dependencies on IGC_CC_HEADERS_S
12.1.1
-
APPS.IGC_CC_OPN_UPD_GET_LNK_PUB dependencies on IGC_CC_HEADERS_S
12.1.1
-
APPS.IGC_CC_OPN_UPD_GET_LNK_PUB dependencies on IGC_CC_HEADERS_S
12.2.2
-
APPS.IGC_CC_OPEN_INTERFACE_PKG dependencies on IGC_CC_HEADERS_S
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1