Results for “govt_institution_cd”

45 results




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

Overview

The table IGS_OR_INST_HIST_ALL belongs to the IGS (Student System) product family within Oracle E-Business Suite, a module now classified as obsolete across the 12.1.1 and 12.2.2 releases. The entity is documented as a historical repository describing changes to institution records maintained by the Student System, capturing the evolution of institutional attributes over time through dated history rows rather than in-place updates.

Although the ETRM documentation marks this object as "Not implemented in this database," the documented physical schema for 12.1.1 associates it with the IGS owner, a total of 24 columns, and a primary key constraint named IGS_OR_INST_HIST_PK. The heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting that the object be modeled as an independent structure rather than as a hub, link, or satellite connected to other entities within a Data Vault warehouse. This classification reflects the absence of documented foreign-key relationships to other tables in the EBS schema, notwithstanding the presence of organizational and institutional reference columns within the row.

Key Information Stored

The primary key of the table is defined by the composite constraint IGS_OR_INST_HIST_PK, comprising the columns INSTITUTION_CD and HIST_START_DT. A unique index, IGS_OR_INST_HIST_ALL_U1, is defined on the same column pair and serves as the business-key candidate, ensuring that a single institution cannot have two history records beginning on the same date.

The most significant columns include:

The HIST_WHO column captures the actor responsible for the recorded change, complementing the standard audit trail.

Common Use Cases and Queries

Typical usage centers on point-in-time and trend reporting over institutional data. A common pattern retrieves the version of an institution that was effective on a given date:

SELECT institution_cd, name, institution_status, hist_start_dt, hist_end_dt
FROM igs_or_inst_hist_all
WHERE institution_cd = :p_institution_cd
AND :p_as_of_date BETWEEN hist_start_dt AND NVL(hist_end_dt, :p_as_of_date);

Change-tracking queries compare successive versions by ordering on HIST_START_DT and examining differences in NAME, INSTITUTION_STATUS, or INSTITUTION_TYPE. Audit reporting uses HIST_WHO alongside the standard audit columns to attribute changes to users. Multi-org reporting filters on ORG_ID to restrict results to a specific operating unit. Because the ETRM note states the object is not implemented in the database, these patterns serve as reference templates rather than executable statements in environments where the table is absent.

Related Objects

The documentation classifies this entity as standalone, with no foreign-key relationships mined from the schema. Consequently, related objects must be inferred from shared business keys rather than declared constraints. The following objects are significant in that context:

Because the object is obsolete and marked as unimplemented, integrators should confirm its presence before relying on it in custom code or extracts.