Search Results offset_date_alias




Overview
Explore in AI Chat

Overview

IGSFV_CAL_PRD_EVNT_TYPE_OFSTS is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema, registered under the FND Design Data application IGS (the Student Systems / Higher Education product family built on the Oracle Student System data model). It belongs to the calendar and scheduling foundation that governs how academic calendar events, date aliases, and period rollups are calculated.

The view is documented as a Business Intelligence System view — that is, a full, denormalized read layer intended for reporting, extract, and integration consumption rather than for transactional maintenance. It presents the entity "Calendar Period Event Type Offsets," which describes the offset relationship between two date aliases. Within ETRM this record is the mechanism by which the system derives one date alias automatically from another: an offset row states that a context date alias falls a defined number of days, weeks, months, or years away from a related (source) date alias, and the offset may be positive or negative.

The user search term offset_date_alias maps directly to the OFFSET_DATE_ALIAS column, the core identifying attribute of the offset rule captured by this view.

Underlying Base Objects

The ETRM metadata supplied for 12.2.2 documents no referenced base objects for this view, and therefore no join or table lineage can be asserted from the source documentation. What is documented is the column projection: the view exposes the full attribute set of the Calendar Period Event Type Offsets entity together with the standard Oracle Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY) that track row creation and amendment.

The view is registered in FND Design Data as IGS.IGSFV_CAL_PRD_EVNT_TYPE_OFSTS with status VALID. Because no base objects are published, the practical relationship to underlying storage should be confirmed against the IGS application schema in the target instance; the naming convention (IGSFV prefix) indicates a "full view" over the corresponding IGS base entity, with the additional description columns resolved from the referenced date alias definitions.

Key Columns

  • DATE_ALIAS (VARCHAR2(10)) — Name of the event or context date alias being derived.
  • OFFSET_DATE_ALIAS (VARCHAR2(10)) — The related date alias from which the context alias is offset. Creating such offsets lets the system automatically derive a date alias instance from its relationship to another alias. This is the column matched by the search term offset_date_alias.
  • NUMBER_OF_DAY_OFFSET (NUMBER) — Day component of the offset; positive or negative, combinable with WEEK, MONTH, and YEAR offsets.
  • NUMBER_OF_WEEK_OFFSET (NUMBER) — Week component; positive or negative, combinable with DAY, MONTH, and YEAR offsets.
  • NUMBER_OF_MONTH_OFFSET (NUMBER) — Month component; positive or negative, combinable with DAY, WEEK, and YEAR offsets.
  • NUMBER_OF_YEAR_OFFSET (NUMBER) — Year component; positive or negative, combinable with DAY, WEEK, and MONTH offsets.
  • DATE_ALIAS_DESCRIPTION and OFFSET_DATE_ALIAS_DESCRIPTION (VARCHAR2(60)) — Descriptive text for the context and related aliases respectively, provided so reports need not join back to the alias definition.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY — Standard Who audit columns.

Common Use Cases and Queries

Typical uses include auditing the offset rules configured for a calendar, validating the derivation chain between aliases before running a calendar build, and feeding downstream extracts that need alias-relationship metadata. A basic listing of offset rules reads:

SELECT date_alias, offset_date_alias, number_of_day_offset, number_of_week_offset, number_of_month_offset, number_of_year_offset FROM apps.igsfv_cal_prd_evnt_type_ofsts ORDER BY date_alias, offset_date_alias;

To locate every rule that derives from a specific source alias:

SELECT date_alias, offset_date_alias, date_alias_description FROM apps.igsfv_cal_prd_evnt_type_ofsts WHERE UPPER(offset_date_alias) = UPPER(:p_source_alias);

To identify compound offsets — aliases defined by more than one unit of measure — use a filter on the non-zero offset components, for example WHERE number_of_day_offset <> 0 AND number_of_year_offset <> 0. Such rules warrant closer review because they can shift a derived date by both a fixed day count and a calendar-year boundary. All queries should be qualified with the APPS schema and, where the view is consumed by external tools, accessed through a read-only reporting responsibility or a synonym granted to the integration user.