Results for “igs_ca_da_ovd_rules”

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

Overview

The IGS_CA_DA_OVD_RULES table belongs to the IGS product family — the Oracle Student System module — and is documented in the ETRM reference for Oracle EBS 12.1.1 and 12.2.2. Its stated purpose is to store the information related to overriding the seeded system date type setup. In practical terms, the table provides a mechanism for institutions to deviate from the delivered system date configuration maintained by the calendar and date-arithmetic components of the Student System, so that institution-specific date behaviour can be enforced without modifying seeded data.

The object is not implemented in the database according to the ETRM metadata. This indicates that the table form part of the shipped, installable schema definition but was not created in the reference environment, and in current EBS releases the IGS Student System is treated as obsolete. The entity should therefore be regarded as legacy metadata rather than an active integration point.

With respect to Data Vault modelling heuristics mined from the foreign-key structure, the table is classified as satellite-leaning. This suggests that, if the object were modelled formally, it would most naturally be treated as a descriptive satellite attached to the parent configuration hub rather than a hub or link in its own right. The classification is a modelling suggestion derived from the FK topology, not a documented Oracle design statement.

Key Information Stored

The table carries ten documented columns. The primary key is defined by the constraint IGS_CA_DA_OVD_RULE_PK, whose columns are the same pair that form the unique business key: SYS_DATE_TYPE and ELEMENT_CODE. In this entity the surrogate identifier and the business key coincide rather than being separated, so join predicates and uniqueness enforcement both rely on the same two columns.

• SYS_DATE_TYPE — the system date type that is being overridden. This column is both part of the composite primary key and the foreign-key column pointing to IGS_CA_DA_CONFIGS, which establishes the parent configuration record.
• ELEMENT_CODE — the second component of the composite business key, identifying the specific element or rule within the parent system date type to which the override applies.
• SQL_VAL — the SQL expression or value that defines the override behaviour applied in place of the seeded setup.
• SQL_VAL_OVRD_FLAG — a flag indicating whether the SQL value override is active for the rule.
• CLOSED_IND — an indicator marking the rule as closed or inactive, used to suppress enforcement without physical deletion.
• CREATED_BY, CREATION_DATE — the standard Oracle EBS audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit columns recording the most recent modification, its timestamp, and the login session responsible.

Common Use Cases and Queries

The principal use case is diagnostic: determining which date types have institution-specific overrides and whether those overrides remain active. A representative query joins the overrides back to their parent configuration to present the system date type alongside its override definition:

• SELECT o.SYS_DATE_TYPE, o.ELEMENT_CODE, o.SQL_VAL, o.SQL_VAL_OVRD_FLAG, o.CLOSED_IND FROM IGS_CA_DA_OVD_RULES o WHERE o.CLOSED_IND = 'N';
• SELECT c.SYS_DATE_TYPE, o.ELEMENT_CODE, o.SQL_VAL FROM IGS_CA_DA_OVD_RULES o, IGS_CA_DA_CONFIGS c WHERE o.SYS_DATE_TYPE = c.SYS_DATE_TYPE;
• SELECT SYS_DATE_TYPE, ELEMENT_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGS_CA_DA_OVD_RULES WHERE TRUNC(LAST_UPDATE_DATE) >= :p_from_date;

Reporting scenarios include auditing which seeded date behaviours have been customised, reviewing change history via the audit columns, and confirming that closed rules no longer influence date arithmetic. Because the table is not implemented in the reference database, queries should be validated against the target instance's data dictionary before being relied upon in any migration or support activity.

Related Objects

The documented foreign-key relationship defines one clear dependency, and the surrounding configuration objects form the natural ecosystem for this entity:

• IGS_CA_DA_CONFIGS — the referenced parent table. Joined on IGS_CA_DA_OVD_RULES.SYS_DATE_TYPE = IGS_CA_DA_CONFIGS.SYS_DATE_TYPE. This is the authoritative system date type configuration that the override rules modify.
• IGS_CA_DA_OVD_RULES primary key constraint IGS_CA_DA_OVD_RULE_PK — the unique index over (SYS_DATE_TYPE, ELEMENT_CODE) that enforces business-key uniqueness.

The remaining objects in the IGS calendar and date-arithmetic area — such as the calendar type, calendar instance, and date-arithmetic setup tables that reference IGS_CA_DA_CONFIGS — should be treated as indirect dependencies via the parent configuration rather than direct referrers of this table. Because IGS is obsolete in current Oracle EBS releases and this table is not implemented in the reference database, no supported public API or view is documented for it, and any customisation touching these rules should be assessed for upgrade impact before being carried forward.