Results for “element_code”

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

Overview

The table IGS_CA_DA_OVD_VALS belongs to the IGS product family, historically known as the Oracle Student System, and is classified in the ETRM repository as part of an obsolete module. Its purpose, as stated in the ETRM documentation, is to store overridden date type information for the seeded system date types. In practical terms, this table records the site-specific or institution-specific substitutions applied against the standard date types that Oracle delivers with the Student System, allowing implementers to redefine the behavior of specific date elements without altering the seeded baseline configuration.

The heuristic Data Vault classification mined from the foreign key structure identifies this entity as a link table. Interpreted as a modeling suggestion, this implies that IGS_CA_DA_OVD_VALS functions primarily as an associative construct, connecting a system date type to an element code and its overriding value. It is not a standalone hub of business entities; rather, it resolves a relationship between reference data and the override applied to it. Because the object is not implemented in the documented database instance, its physical footprint in any particular EBS environment should be verified directly against the IGS schema before it is relied upon in a functional or reporting context.

Key Information Stored

Ten columns are documented for this table. The most significant are the following:

• OVRD_VAL_ID — the surrogate primary key defined by the constraint IGS_CA_DA_OVD_VAL_PK. This is a system-generated identifier and carries no business meaning beyond uniquely identifying each override record.
• SYS_DATE_TYPE — the seeded system date type being overridden. This column participates in the unique index IGS_CA_DA_OVD_VAL_U1 and is also documented as a foreign key column, indicating a dependency on the parent date type definition.
• ELEMENT_CODE — the identifier of the element whose value is being overridden. Together with SYS_DATE_TYPE and ELEMENT_CODE_VALUE, this column forms the composite business key IGS_CA_DA_OVD_VAL_U1.
• ELEMENT_CODE_VALUE — the specific value associated with the element code within the override relationship, completing the unique business key.
• DATE_ALIAS — the alias by which the overridden date type is referenced, providing a descriptive or institution-specific label for the override.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns capturing who created and last modified each row, when, and from which login session.

The distinction between the surrogate key and the business key is important: OVRD_VAL_ID guarantees row-level uniqueness, while IGS_CA_DA_OVD_VAL_U1 enforces the business rule that a given system date type and element combination may only be overridden once.

Common Use Cases and Queries

Typical usage centers on diagnosing discrepancies between seeded date behavior and observed date behavior in a Student System implementation. A common reporting pattern retrieves all overrides for a given date type:

SELECT ovrd_val_id, sys_date_type, element_code, element_code_value, date_alias
FROM igs_ca_da_ovd_vals
WHERE sys_date_type = :p_date_type;

Auditing queries frequently filter on the audit columns to determine when an override was introduced or changed, for example restricting on LAST_UPDATE_DATE between two dates. Data migration and comparison scripts join the override values back to the parent date type definitions to produce a before-and-after listing of effective configuration. Because the table is documented as obsolete and not implemented, any query should first confirm existence via ALL_TABLES before execution, and results should be treated as legacy configuration evidence rather than active functional data.

Related Objects

The documented foreign key metadata shows self-referencing relationships within IGS_CA_DA_OVD_VALS, where SYS_DATE_TYPE and ELEMENT_CODE each point back to columns in the same or closely associated IGS constructs. The following objects are the most significant to consider alongside this table:

• IGS_CA_DA_OVD_VALS (self-referencing) — the SYS_DATE_TYPE foreign key relationship documented against the parent date type definition.
• IGS_CA_DA_OVD_VALS (self-referencing) — the ELEMENT_CODE foreign key relationship documented against the element definition.
• IGS_CA_DA_OVD_VAL_PK — the primary key constraint enforcing uniqueness on OVRD_VAL_ID.
• IGS_CA_DA_OVD_VAL_U1 — the unique index enforcing the SYS_DATE_TYPE, ELEMENT_CODE, ELEMENT_CODE_VALUE business key.

Because the ETRM extract does not resolve the foreign key targets to named external tables, the safest authoritative reference remains the IGS schema itself. Consultants working with this object should treat it as a legacy artifact of the Student System date-type override framework and confirm its presence and current relationship targets directly in the target database.