Results for “prior_alternate_code”

7 results




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

Overview

The IGSBV_CALENDAR_PERIODS view is the base reporting and integration object for the Calendar Periods entity within the Oracle E-Business Suite Student System (IGS) product family. In the IGS data model, a calendar period describes a concrete instance of a calendar type — for example, an academic year, term, semester, or other defined instructional period created from a calendar type definition. The view is owned by the APPS schema and holds VALID status in both the 12.1.1 and 12.2.2 releases, where the object is catalogued under the IGS - Student System module.

Because it presents calendar instances in a denormalized, read-only form, the view is used chiefly for downstream reporting, self-service and IVR display, and integration extracts. The WITH READ ONLY clause in its definition confirms that it is not intended as a DML target; all maintenance of calendar periods is performed against the underlying tables through the standard IGS forms and concurrent programs.

Underlying Base Objects

Detailed ETRM metadata for 12.2.2 documents no referenced base objects, but the view text itself identifies three source objects in the APPS schema:

  • IGS_CA_INST_ALL, aliased IN1 — the primary calendar instance table supplying the driving rows and most columns.
  • IGS_CA_INST_ALL, aliased IN2 — a self-join used to retrieve the prior calendar instance's alternate code and dates.
  • IGS_CA_TYPE, aliased TY3 — the calendar type table supplying the calendar description.

The self-join is an outer join on CAL_TYPE and SEQUENCE_NUMBER: IN1.CAL_TYPE = IN2.CAL_TYPE(+) and IN1.PRIOR_CI_SEQUENCE_NUMBER = IN2.SEQUENCE_NUMBER(+). The join to IGS_CA_TYPE is an inner join on CAL_TYPE. This structure means each row returns one calendar period enriched with attributes of the period immediately preceding it in the same calendar type sequence, when one exists.

Key Columns

The view exposes nineteen columns that map onto the three source objects:

Common Use Cases and Queries

Typical scenarios include listing all periods for a calendar type in sequence, resolving the immediately preceding period for comparison or reporting, and filtering to periods that are enabled for self-service or IVR. The following query retrieves periods for a given calendar type together with their predecessor's dates:

SELECT CALENDAR_TYPE, SEQUENCE_NUMBER, START_DATE, END_DATE, CALENDAR_STATUS, PRIOR_CAL_INST_SEQ_NUM, PRIOR_START_DATE, PRIOR_END_DATE FROM APPS.IGSBV_CALENDAR_PERIODS WHERE CALENDAR_TYPE = :p_cal_type ORDER BY SEQUENCE_NUMBER;

A second common pattern isolates periods that are visible in self-service and have a defined predecessor, which is useful when validating sequence continuity:

SELECT SEQUENCE_NUMBER, ALTERNATE_CODE, PRIOR_CAL_INST_SEQ_NUM FROM APPS.IGSBV_CALENDAR_PERIODS WHERE CALENDAR_TYPE = :p_cal_type AND SELF_SERVICE_DISPLAYED = 'Y' AND PRIOR_CAL_INST_SEQ_NUM IS NOT NULL;

Because the view is read-only and structured around a single calendar type hierarchy, it is well suited to concurrent-program extracts and BI Publisher reports that require calendar period context without navigating the full IGS_CA_INST_ALL table directly.