Results for “absolute_value”

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

Overview

IGSFV_CALENDAR_PERIOD_EVENTS is a read-only view belonging to the IGS (Student System) product family within Oracle E-Business Suite. The "FV" prefix conventionally denotes a "full view," the most denormalized presentation layer for a base entity. In this case, the view materializes the Calendar Period Event entity, defined in the ETRM metadata as an instance of a date alias within a calendar instance. Its role is to present derived calendar dating information in a form consumable by reporting, inquiry, and integration components that require resolved calendar dates rather than the normalized identifiers held in the underlying transaction tables.

It should be noted that the IGS product family is flagged as obsolete in the 12.1.1 and 12.2.2 documentation sets. The view is documented as "Not implemented in this database," meaning it appears in the data dictionary reference but is not necessarily deployed in a standard installation. Consultants inspecting a live environment may find that the object does not exist, depending on the modules installed and the version heritage of the instance.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects, the published view text establishes the dependency chain explicitly. The view is defined over three physical tables:

• IGS_CA_DA_INST — the date alias instance table, aliased as DA. This supplies the primary rows of the view, one per date alias instance within a calendar instance.
• IGS_CA_DA — the date alias definition table, aliased as DA1. Joined on DT_ALIAS to retrieve the human-readable alias description.
• IGS_CA_INST_ALL — the calendar instance table, aliased as IN2. Joined on CAL_TYPE and CI_SEQUENCE_NUMBER to supply calendar instance dates and alternate codes.

The view also invokes two database functions, IGS_CA_GEN_002.CALS_CLC_DT_FROM_DAI and IGS_CA_GEN_001.CALP_SET_ALIAS_VALUE, which perform the date arithmetic that resolves a relative alias into a concrete calendar date. These functions embody the core logic of the calendar subsystem and are the reason the view cannot be reduced to a simple join.

Key Columns

The view exposes fifteen columns. The most significant include:

• DATE_ALIAS and DATE_ALIAS_DESCRIPTION — the alias code and its descriptive text, identifying which calendar marker (for example, a term start or census date) the row represents.
• SEQUENCE_NUMBER — orders multiple instances of the same alias within a calendar.
• CALENDAR_TYPE and CAL_INST_SEQ_NUM — the calendar category and the specific calendar instance, forming the join key to IGS_CA_INST_ALL.
• ABSOLUTE_VALUE — the offset or absolute value stored against the alias instance.
• DERIVED_VALUE and ALIAS_VALUE — the resolved date and the final displayed alias value returned by the two generation functions.
• START_DATE, END_DATE, ALTERNATE_CODE — attributes inherited from the calendar instance.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

Typical usage involves resolving calendar dates for reporting on academic periods, validating that a given alias instance falls within its calendar window, or feeding downstream integration extracts with concrete dates rather than alias codes.

SELECT DATE_ALIAS, SEQUENCE_NUMBER, CALENDAR_TYPE,
       CAL_INST_SEQ_NUM, DERIVED_VALUE, ALIAS_VALUE,
       START_DATE, END_DATE
  FROM IGSFV_CALENDAR_PERIOD_EVENTS
 WHERE CALENDAR_TYPE = :p_cal_type
   AND CAL_INST_SEQ_NUM = :p_seq_num
 ORDER BY DATE_ALIAS, SEQUENCE_NUMBER;

Because the view is declared WITH READ ONLY, it must not be targeted by DML; any maintenance occurs against the base tables. Queries should also anticipate that the slowest element is the function call per row, so filtering on calendar type and instance sequence number before aggregation is advisable.