Search Results igc_cc_copy_pkg




Overview
Explore in AI Chat

Overview

IGC_CC_COPY_PKG is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the copy operation for cost collection / cost collection header records within the Oracle Enterprise Trade Management (formerly Oracle Grants/Contracts, ETRM) product. In Oracle EBS 12.1.1 and 12.2.2 the package is declared with AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking user and relies on APPS synonyms for object resolution rather than definer's rights. The package is classified as an "OTHER" API under the ETRM documentation model, indicating that it is an internal utility API rather than a fully published, externally supported interface. Its primary purpose is to duplicate an existing cost collection header — and the dependent detail records that belong to it — into a newly created header, preserving the business structure of the source document while allowing a new document number and type to be assigned.

Key Procedures and Functions

The package exposes a single documented procedure, HEADER_COPY. As the name implies, it performs the header-level copy operation for a cost collection document. The procedure accepts standard Oracle EBS API control parameters (API version, message list initialization, commit flag, and validation level) together with the source and target header identifiers, a new cost collection number, and a new cost collection type. It returns the conventional API status outputs: return status, message count, and message data.

  • HEADER_COPY — Copies the attributes of an existing cost collection header (identified by the old header ID) into a new header, applying the supplied cost collection number and type and returning the new header identifier and API status information. Because the parameter list includes both the old and new header IDs, the procedure is intended to be called after the target header record has been established or as part of a coordinated insert-and-copy flow.

No additional public procedures or functions are documented for this package; any further logic is contained within the package body and is not part of the documented interface.

Tables Accessed

The package operates on the core cost collection tables and their associated detail tables, resolved through APPS synonyms:

  • IGC_CC_HEADERS — the primary cost collection header table. The source header is read and the new header is written or updated.
  • IGC_CBC_JE_LINES — journal entry lines associated with the cost collection, copied to maintain the accounting distribution of the source document.
  • IGC_CC_ACCESS — access control records that determine which users or responsibilities may view or modify the cost collection; copied so that the new document inherits the same security profile.
  • IGC_CC_ACCT_LINES — cost collection account lines, which carry the account-level detail for the document.
  • IGC_CC_DET_PF — the cost collection detail profile table, holding detail-level profile or distribution information.

Together these tables represent the header, accounting, security, and detail layers of a cost collection document, confirming that HEADER_COPY performs a full structural duplication rather than a simple header insert.

Usage Notes

IGC_CC_COPY_PKG is not referenced by any other documented package, which is consistent with its role as a low-level utility invoked directly from the ETRM application layer. Typical invocation points include the cost collection entry form, where a user selects a "copy" or "duplicate" action, and custom or extension code that needs to replicate an existing cost collection. Because the package is declared AUTHID CURRENT_USER, callers must have the necessary privileges on the underlying IGC tables. The presence of standard FND_API parameters allows the caller to control transaction commit and validation behavior, so it can be safely composed into larger API-driven transactions. Developers integrating with this package should treat it as an internal ETRM API and validate behavior against the specific 12.1.1 or 12.2.2 release in use, since the header comment indicates the source was last revised in 2007 and the interface is not published as a supported public API.