Search Results absolute_val




Overview
Explore in AI Chat

Overview

IGSBV_CAL_PRD_EVNT_PAIRS is a read-only Oracle EBS view owned by the APPS schema and delivered as part of the Student Systems / Oracle Student System calendar (IGS) module. It presents the relationship between pairs of date aliases within a calendar instance, resolving each alias to an actual date value. Its role is primarily reporting and integration: it exposes the internal pairing structure maintained in IGS_CA_DA_INST_PAIR, together with the calculated date returned by the calendar generation logic, so that downstream reports, concurrent programs, and interfaces can consume resolved dates without directly invoking the calendar PL/SQL APIs.

The view is significant because it surfaces the function IGS_CA_GEN_002.CALS_CLC_DT_FROM_DAI, which is the calendar date derivation routine. The dependency on this function is why a search for the term igs_ca_gen_002 leads to this view: the view cannot be compiled or validated without IGS_CA_GEN_002 being present and valid in the database.

Underlying Base Objects

Although the delivered metadata records no documented base objects, the view text unambiguously shows three source objects:

  • IGS_CA_DA_INST_PAIR (aliased DA) — the pairing table that stores, for a given calendar instance and date alias, the related date alias and its sequence number. This is the driving table.
  • IGS_CA_DA_INST (aliased DA1) — the calendar instance date record for the primary alias, supplying ABSOLUTE_VAL, the stored offset value.
  • IGS_CA_DA_INST (aliased DA2) — the calendar instance date record for the related alias, supplying its corresponding ABSOLUTE_VAL.

The joins are made on the composite key of DT_ALIAS, DAI_SEQUENCE_NUMBER (matched to SEQUENCE_NUMBER), CAL_TYPE, and CI_SEQUENCE_NUMBER, ensuring each alias resolves within the same calendar category and calendar instance. The view is created with the READ ONLY clause, so it cannot be used as a DML target.

Key Columns

  • DT_ALIAS, DAI_SEQUENCE_NUMBER — the primary date alias and its instance sequence number.
  • CAL_TYPE, CI_SEQUENCE_NUMBER — the calendar type and calendar instance to which the aliases belong; these qualify all lookups.
  • RELATED_DT_ALIAS, RELATED_DAI_SEQUENCE_NUMBER — the paired (related) alias and sequence number.
  • RELATED_CAL_TYPE, RELATED_CI_SEQUENCE_NUMBER — the calendar type and instance of the related alias, which may differ from the primary side.
  • ABSOLUTE_VAL (from DA1 and DA2) — the stored offset value for each alias.
  • CALS_CLC_DT_FROM_DAI(...) — the calculated calendar date for each alias, derived by IGS_CA_GEN_002 from CI_SEQUENCE_NUMBER, CAL_TYPE, DT_ALIAS, and SEQUENCE_NUMBER.
  • CALP_SET_ALIAS_VALUE(...) — the value returned by IGS_CA_GEN_001 for the resolved date, used to normalise or set the alias value.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns inherited from IGS_CA_DA_INST_PAIR.

Common Use Cases and Queries

Typical scenarios include reporting the offset between a teaching period start and its related census or end date, verifying that calendar instance pairs were generated consistently, and feeding interfaces that expect resolved dates rather than relative aliases.

To retrieve resolved dates for a calendar instance:

  • SELECT dt_alias, related_dt_alias, cal_type, ci_sequence_number, absolute_val FROM apps.igsbv_cal_prd_evnt_pairs WHERE ci_sequence_number = :ci_seq;

To isolate a specific alias pairing:

  • SELECT * FROM apps.igsbv_cal_prd_evnt_pairs WHERE dt_alias = :alias AND cal_type = :cal_type;

To diagnose calendar generation issues, query for pairs where the derived date is null, which can indicate a stale or invalid IGS_CA_GEN_002 function state, or a mismatched CI_SEQUENCE_NUMBER.