Search Results conferral_start_date

Overview

IGS_GR_CRMN_ROUND is an APPS-owned view registered under the FND Design Data application IGS (Student Systems / Student Records). It exposes graduation ceremony round data — the conferral and completion date windows associated with a specific graduation calendar round — to Oracle EBS reporting, concurrent processing, and validation logic. In Oracle EBS 12.1.1 and 12.2.2 the view carries VALID status and is defined as a multi-org view, meaning it applies the operating unit security predicate automatically: only rows belonging to the operating unit (ORG_ID) of the current session are returned, and data belonging to other operating units is ignored. This makes the view safe to use directly in reports and in modules where operating unit isolation is expected.

Because it is a view rather than a table, it holds no storage of its own; the view source and object metadata are versioned through the Oracle EBS Release Management (ETRM) repository, which documents the object name, owner, status, column list, and the query text used to define it.

Underlying Base Objects

The documented dependencies identify a single base object: APPS.IGS_GR_CRMN_ROUND_ALL, which holds the underlying ceremony round rows for all operating units. IGS_GR_CRMN_ROUND applies the multi-org WHERE clause against that table's ORG_ID so that only the current operating unit's rows are visible.

On the dependent side, IGS_GR_CRMN_ROUND is referenced by several objects, including the view IGS_GR_CRMN_ROUND_V, the views IGS_GR_GRD_PERD_ABBRVTN_V and IGS_GR_GRD_PERD_V, and the validation/concurrent programs IGS_GR_VAL_CRDP, IGS_GR_VAL_GAC, IGS_GR_VAL_GR, and IGS_GR_GEN_002. This dependency footprint confirms the view is a foundational source for graduation period derivation and graduation validation, not merely a presentation-layer convenience.

Key Columns

• ROW_ID (ROWID) — pseudo-column identifying the physical row in the base table; useful for direct row addressing.
• ORG_ID (NUMBER) — operating unit identifier applied by the multi-org predicate.
• GRD_CAL_TYPE / GRD_CI_SEQUENCE_NUMBER — the graduation calendar type and calendar instance sequence number that identify the ceremony round.
• START_DT_ALIAS, START_DAI_SEQUENCE_NUMBER, END_DT_ALIAS, END_DAI_SEQUENCE_NUMBER — aliases and sequence numbers of the date alias instances that bound the round.
• CONFERRAL_START_DATE / CONFERRAL_END_DATE — the window in which awards are conferred.
• COMPLETION_START_DATE / COMPLETION_END_DATE — the window in which completion is considered to occur for the round; this is the column set referenced by the search term "completion_start_date".
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include validating that a student's completion falls within the round's completion window, aligning conferral dates with graduation period definitions, and feeding graduation reports. A simple retrieval by calendar round is:

SELECT grd_cal_type, grd_ci_sequence_number, completion_start_date, completion_end_date
FROM apps.igs_gr_crmn_round
WHERE completion_start_date >= :p_from_date
AND completion_end_date <= :p_to_date;

To locate the round covering a given completion date: SELECT * FROM apps.igs_gr_crmn_round WHERE :p_completion_date BETWEEN completion_start_date AND completion_end_date;. Because the view is multi-org, callers running under an operating unit context should not add their own ORG_ID filter unless cross-org reporting is explicitly intended.