Search Results offset_calendar_type




Overview
Explore in AI Chat

Overview

IGSBV_CAL_PRD_EVNT_OFST_CONS is a read-only base view owned by the APPS schema within the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes the entity known as the Calendar Period Event Offset Constraint, which defines the rules applied when an offset is used to derive one date alias instance value from another date alias instance. In practical terms, the view answers the question: given a source date alias instance and an offset expressed in days, weeks, months, or years, what additional constraints must hold before the resulting date alias instance value can be generated or accepted?

Because the object is defined WITH READ ONLY, it functions purely as a query surface. It carries no DML capability and is intended for reporting, validation, and integration logic rather than transactional maintenance. Users searching on date_alias_inst_seq_num are typically locating the sequence key that identifies a specific instance of a date alias, enabling joins from a calendar date alias instance to its associated offset constraints across the same calendar type and calendar instance.

Underlying Base Objects

The ETRM metadata documents no separately registered base objects, but the view text reveals its composition precisely. IGSBV_CAL_PRD_EVNT_OFST_CONS is defined over two IGS calendar tables, joined on their full composite key:

  • IGS_CA_DA_INST_OFCNT DA — the date alias instance offset constraint table, supplying the constraint type, condition, and resolution attributes.
  • IGS_CA_DA_INST_OFST DA1 — the date alias instance offset table, supplying the numeric day, week, month, and year offset values plus the override flag.

The join matches all eight key columns: DT_ALIAS, DAI_SEQUENCE_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER, OFFSET_DT_ALIAS, OFFSET_DAI_SEQUENCE_NUMBER, OFFSET_CAL_TYPE, and OFFSET_CI_SEQUENCE_NUMBER. This ensures that each constraint row is paired with the offset definition applying to the same source and target alias instances. The outer object is read-only, so all maintenance must be performed against the two underlying tables.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which constraints govern date alias derivation, diagnosing why a derived date failed to resolve, and extracting offset configuration for migration or reconciliation. A representative query filters by the alias instance of interest:

  • SELECT date_alias, date_alias_inst_seq_num, offset_date_alias, offset_date_alias_inst_seq_num, date_alias_ofst_cons_typ, constraint_condition, constraint_resolution FROM igsbv_cal_prd_evnt_ofst_cons WHERE date_alias_inst_seq_num = :seq;
  • SELECT calendar_type, cal_inst_seq_num, number_of_day_offset, number_of_week_offset, number_of_month_offset, number_of_year_offset, ofst_override FROM igsbv_cal_prd_evnt_ofst_cons WHERE offset_date_alias = :source_alias;

Because the view joins both base tables, its cost is proportional to the matching key sets; filtering on DATE_ALIAS, CALENDAR_TYPE, or the sequence columns before joining large calendars preserves performance.