Results for “igc_cc_periods_v”

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

Overview

The IGC_CC_PERIODS_V view is a reporting and inquiry object owned by the APPS schema within the Oracle E-Business Suite Contract Commitment (IGC) product family. In both release 12.1.1 and 12.2.2, this view exposes a denormalized, human-readable representation of the accounting periods that have been enabled or tracked for the Contract Commitment process. Contract Commitment functionality allows an organization to capture, track, and report on commitments against contracts before they are converted into actual accounting transactions; those commitments must be associated with a valid accounting period. This view answers the question "for which GL periods is Contract Commitment activity permitted, and what is the current status of each period?"

The view joins period definitions maintained in the General Ledger period calendar to the Contract Commitment-specific period status records, and additionally decodes the period status code into its user-facing meaning. This layering allows forms, concurrent programs, and third-party integrations to consume a single queryable source without needing to understand the underlying normalization or join logic. Because it is a view rather than a table, it carries no independent storage and reflects the current committed state of its base objects at query time.

Underlying Base Objects

The documented base objects referenced by IGC_CC_PERIODS_V are:

• IGC_CC_PERIODS — the core Contract Commitment period table that stores which periods are recognized by the IGC process and their status codes. This is the driving table of the view.
• GL_PERIODS — the General Ledger period definitions, supplying the period number, period year, start date, and end date. The join is performed on the combination of PERIOD_SET_NAME and PERIOD_NAME.
• FND_LOOKUPS — the Oracle Application Object Library lookup values view, used to translate the internal status code into its display meaning. The join uses an outer join ((+)) on lookup type 'IGC_CC_PERIOD_STATUS'.

These are joined inside the view definition, so consumers interact only with the view name. Note that GL_PERIODS and IGC_CC_PERIODS are documented as synonyms in the ETRM metadata, and FND_GLOBAL is referenced through package functions such as ORG_ID, which supplies the organization context.

Key Columns

The view exposes the following columns, each carrying a specific reporting meaning:

• ROW_ID — the ROWID of the underlying IGC_CC_PERIODS row, used for updates from the view.
• ORG_ID — the operating unit (organization) to which the period status record belongs; multi-org security filters on this column.
• PERIOD_SET_NAME — the accounting period set (calendar) name, such as a user-defined GL calendar.
• PERIOD_NAME — the specific period identifier, such as "JAN-2024".
• PERIOD_NUM and PERIOD_YEAR — the numeric period sequence and its year, sourced from GL_PERIODS.
• START_DATE and END_DATE — the absolute calendar dates bounding the period.
• CC_PERIOD_STATUS — the internal status code for the Contract Commitment period, joined to the IGC_CC_PERIOD_STATUS lookup type.
• CC_PERIOD_STATUS_DESC — the decoded, user-friendly meaning of the status (for example, Open, Closed, or Never Opened), returned from FND_LOOKUPS.MEANING.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard audit columns describing who created and last modified the record and when.

Common Use Cases and Queries

Typical uses of this view include validating the period a user selects when entering a commitment, restricting or defaulting date ranges in IGC forms, and feeding period status into reporting extracts and integrations. A representative query returns all currently open Contract Commitment periods for a given organization and calendar:

• SELECT period_name, period_num, period_year, start_date, end_date, cc_period_status_desc FROM igc_cc_periods_v WHERE org_id = :p_org_id AND period_set_name = :p_period_set AND cc_period_status = 'O' ORDER BY period_year, period_num;
• Integration extracts frequently select only the essential columns: SELECT org_id, period_set_name, period_name, start_date, end_date, cc_period_status FROM igc_cc_periods_v;
• Auditing and reconciliation queries select the audit columns alongside the status to identify who last changed a period and when.

Because the view is defined in APPS and joins base synonyms, standard Oracle EBS multi-org and security conventions apply: callers should supply or respect the appropriate ORG_ID and rely on the decoded CC_PERIOD_STATUS_DESC column for display purposes rather than joining to FND_LOOKUPS again.