Results for “offset_alias_value”

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

Overview

The view IGSFV_CAL_PRD_EVNT_OFSTS belongs to the IGS — Student System product family, identified in the ETRM repository as obsolete. It is the "full" (formula-validation) view for the entity Calendar Period Event Offset, which models the relationship between two date alias instances. In institutional calendar modelling, a date alias represents a named point or period within a calendar instance (for example, a term start, census date, or enrolment deadline). An event offset extends that concept by expressing one date alias relative to another, using day, week, month, and year offsets. The view therefore exposes both the source alias instance and the offset target alias instance, together with the offset arithmetic and derived calendar values.

In Oracle EBS reporting and integration terms, a "full view" in the IGS data model is the object used to satisfy the API layer and the generated Business Component views. It presents descriptive attributes and derived values that are not stored on the underlying intersection table, allowing forms, reports, and PL/SQL consumers to read a single denormalised row per calendar period event offset rather than joining and computing values themselves.

Underlying Base Objects

The ETRM metadata records no documented referenced base objects, and the object is flagged "Not implemented in this database" for the documented 12.2.2 environment. However, the published view text shows the definition precisely. It is built over three instances of the IGS_CA_DA_INST table (the date alias instance table), aliased DA, DA1, and DA2, joined to the offset intersection table IGS_CA_DA_INST_OFST (aliased DA in the FROM clause position of the offset table, which supplies the offset columns).

Join predicates establish three relationships: DA (the offset row) is matched to DA1 on date alias, sequence number, calendar type, and calendar instance sequence number; and to DA2 on the corresponding OFFSET_* columns. In other words, the offset record links two date alias instances, and the view resolves both sides to their full instance rows. The view is declared WITH READ ONLY.

Key Columns

• DATE_ALIAS, DATE_ALIAS_INST_SEQ_NUM, CALENDAR_TYPE, CAL_INST_SEQ_NUM — identify the source date alias instance (from DA1).
• OFFSET_DATE_ALIAS, OFFSET_DATE_ALIAS_INST_SEQ_NUM, OFFSET_CALENDAR_TYPE, OFFSET_CAL_INST_SEQ_NUM — identify the target (offset) date alias instance (from DA2).
• NUMBER_OF_DAY_OFFSET, NUMBER_OF_WEEK_OFFSET, NUMBER_OF_MONTH_OFFSET, NUMBER_OF_YEAR_OFFSET — the relative offset amounts defined between the two aliases.
• OFST_OVERRIDE — flag permitting the offset to be overridden at instance level.
• ABSOLUTE_VALUE, DERIVED_VALUE, ALIAS_VALUE — the absolute value of the source alias and its derived/alias-resolved value, produced via IGS_CA_GEN_002.CALS_CLC_DT_FROM_DAI and IGS_CA_GEN_001.CALP_SET_ALIAS_VALUE.
• OFFSET_ABSOLUTE_VALUE, OFFSET_DERIVED_VAL — the equivalent absolute and derived values for the offset target alias.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical use cases include validating calendar date arithmetic, driving scheduling or deadline logic in student administration, and auditing which aliases are offset from one another within a calendar instance. The stored functions IGS_CA_GEN_002 (date calculation from a date alias instance) and IGS_CA_GEN_001 (alias value resolution) are the key dependencies, which is why a search for igs_ca_gen_002 surfaces this view.

A representative query retrieves offsets for a calendar instance:

SELECT date_alias, cal_type, cal_inst_seq_num,
       offset_date_alias, number_of_day_offset,
       derived_value, offset_derived_val
FROM   igsfv_cal_prd_evnt_ofsts
WHERE  cal_type = :p_cal_type
AND    cal_inst_seq_num = :p_seq_num;

Because the object is obsolete and not implemented in the documented database, its use should be limited to legacy 11i/12.1 environments; new development should rely on the current IGS calendar APIs and the underlying IGS_CA_DA_INST and IGS_CA_DA_INST_OFST tables directly.