Search Results igc_ccp_pk

Overview

IGC_CC_PERIODS is a table within the Oracle E-Business Suite IGC – Contract Commitment module. It stores contract commitment period statuses, establishing the accounting period context associated with contract commitment records. The table acts as the period-level dimension for IGC contract commitment processing, allowing commitments to be segmented, validated, and reported against the General Ledger period calendar of a specific operating unit.

The ETRM metadata classifies this object heuristically, based on its foreign key structure, as a link table in Data Vault modeling terms. This classification is a modeling suggestion rather than a physical design statement: the table connects a period reference (through GL_PERIODS) to an organization (through HR_ALL_ORGANIZATION_UNITS), functioning as an associative entity between period definitions and organizational units. In a Data Vault build, this pattern would typically be implemented as a link table capturing the relationship between the period hub and the organization hub.

Key Information Stored

Because IGC_CC_PERIODS is documented with a composite primary key rather than a single surrogate column, its business key is the primary key itself. The most significant columns are:

• IGC_CCP_PK – The documented primary key constraint for the table. In EBS technical dictionaries, the constraint name (rather than a separate surrogate column) is often cited as the PK reference; the actual key is the composite of the columns below.
• ORG_ID – Identifies the operating unit / organization. This is a mandatory key column and a foreign key to HR_ALL_ORGANIZATION_UNITS. It enforces multi-org security and segmentation.
• PERIOD_SET_NAME – The name of the accounting period set (calendar) to which the period belongs. Foreign key to GL_PERIODS.
• PERIOD_NAME – The specific accounting period name. Together with PERIOD_SET_NAME, qualifies the period within the General Ledger calendar. Foreign key to GL_PERIODS.

The composite business key is thus (ORG_ID, PERIOD_SET_NAME, PERIOD_NAME). No separate surrogate ID column is documented. Note that the metadata states this table is not implemented in this database; the structure and relationships below reflect the documented ETRM data model, and installations that do not use the IGC Contract Commitment period feature will not find a populated object.

Common Use Cases and Queries

Typical scenarios include validating that an accounting period is open for a given operating unit before posting or recognizing contract commitments, and reporting commitment activity by period and organization.

Example: list commitment period statuses for an operating unit.

• SELECT org_id, period_set_name, period_name FROM igc_cc_periods WHERE org_id = :p_org_id;

Example: join to the GL period calendar to retrieve start and end dates.

• SELECT c.org_id, c.period_set_name, c.period_name, p.start_date, p.end_date FROM igc_cc_periods c, gl_periods p WHERE c.period_set_name = p.period_set_name AND c.period_name = p.period_name;

Example: restrict to open periods for a specific organization (open-flag logic depends on the GL period status API in the release). These patterns support commitment-period availability reporting, close-cycle reconciliation, and multi-org security filtering.

Related Objects

The most significant objects related to IGC_CC_PERIODS are those defined by its documented foreign keys:

• GL_PERIODS – Referenced through IGC_CC_PERIODS.PERIOD_SET_NAME and IGC_CC_PERIODS.PERIOD_NAME. Supplies the calendar definition and period dates.
• HR_ALL_ORGANIZATION_UNITS – Referenced through IGC_CC_PERIODS.ORG_ID. Provides the operating unit / organization context and drives multi-org security.
• IGC_CC_PERIODS (self, via PK IGC_CCP_PK) – The primary key definition on (ORG_ID, PERIOD_SET_NAME, PERIOD_NAME) anchors joins from dependent contract commitment tables that carry the same period columns.

As the table is not implemented in the reference database, other IGC Contract Commitment entities that would join on the period key are not enumerated in the supplied metadata. In practice, commitment headers and lines, and any period-status driven processing, reference this table through the composite period key and are best confirmed against the IGC module's delivered DDL.