Results for “igcbv_cc_releases”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGCBV_CC_RELEASES is a read-only reporting view owned by the APPS schema within Oracle E-Business Suite, delivered as part of the IGC – Contract Commitment module. It presents contractual release records — the subordinate contract commitments that descend from a controlling parent agreement — in a denormalized, business-friendly form. The view filters the contract commitment header table to rows whose type code equals 'R', meaning only releases are exposed, excluding master or standalone commitments.

Because it carries the APPS prefix and is defined WITH READ ONLY, the view is intended strictly for query, reporting, and integration consumption rather than transactional maintenance. It serves as a stable interface layer through which ETRM and downstream reporting tools can retrieve release header attributes without navigating the underlying base table structure directly.

Underlying Base Objects

The view is defined over IGC_CC_HEADERS (documented in ETRM 12.2.2 metadata as the synonym IGC_CC_HEADERS_ALL). The defining query selects from IGC_CC_HEADERS aliased as IGC_CCH and applies two predicates: CC_TYPE = 'R' to isolate release records, and a security predicate on ORG_ID to enforce operating unit access. This security filter is expressed as '_SEC:IGC_CCH.ORG_ID' IS NOT NULL, which Oracle's application security framework resolves at runtime to restrict rows to the operating units the querying responsibility is permitted to see. The view is documented as VALID in the APPS schema across both 12.1.1 and 12.2.2 releases.

Key Columns

• RELEASE_CONTRACT_NUMBER — maps to CC_NUM, the user-visible release contract number.
• RELEASE_VERSION_NUMBER — maps to CC_VERSION_NUM, identifying the version of the release record. This column is the direct answer to the common search term "release_version_number"; it is the version dimension of the release contract.
• RELEASE_CONTRACT_COMMITMENT_ID — maps to CC_HEADER_ID, the primary key of the release header.
• PARENT_CONTRACT_COMMITMENT_ID — maps to PARENT_HEADER_ID, linking the release back to its governing parent commitment.
• _LA:RELEASE_CONTROL_STATUS, _LA:RELEASE_APPROVAL_STATUS, _LA:TYPE, _LA:STATE — these are label (translation) columns resolved through FND_LOOKUPS against IGC_CC_CONTROL_STATUS, IGC_CC_APPROVAL_STATUS, IGC_CC_TYPE, and IGC_CC_STATE, returning the MEANING of the stored lookup code.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the CC_START_DATE and CC_END_DATE of the release.
• ORGANIZATION_ID, VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, TERM_ID, LOCATION_ID, SET_OF_BOOKS_ID, CURRENCY_CODE, CONVERSION_TYPE — commercial and accounting attributes of the release.
• PREPARER_USER_ID, OWNER_USER_ID — the users who prepared and own the release.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical uses include listing releases for a parent agreement, auditing version history, and driving supplier-facing reports of approved releases. Because the _LA columns return translated meanings, they are convenient for reports requiring descriptive status text rather than codes.

Sample query listing releases with their version and status:

• SELECT RELEASE_CONTRACT_NUMBER, RELEASE_VERSION_NUMBER, "_LA:RELEASE_CONTROL_STATUS", "_LA:TYPE", START_EFFECTIVE_DATE FROM APPS.IGCBV_CC_RELEASES WHERE PARENT_CONTRACT_COMMITMENT_ID = :parent_id ORDER BY RELEASE_VERSION_NUMBER;

A second common pattern joins the view to IGC_CC_HEADERS for parent details, or filters by ORGANIZATION_ID to scope results to a single operating unit. Note that the security predicate is automatically applied, so results are limited to organizations accessible to the current responsibility.