Results for “igs_en_unit_set_hist_all”

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

Overview

IGS_EN_UNIT_SET_HIST_ALL is a history (audit) table within the IGS – Student System module of Oracle E-Business Suite. It records the chronological history of changes made to a unit set version. Because unit sets define groupings of academic units (such as sections, courses, or program components used in enrollment and progression rules), tracking the evolution of each version is essential for audit, regulatory, and reconciliation purposes. The object is documented for ETRM 12.1.1 with an owner of IGS and 25 columns, and it is explicitly flagged as not implemented in the reference database and belonging to an obsolete product area. Its presence therefore serves primarily as a legacy/compatibility artifact rather than an active transactional structure.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as standalone. In practice, however, the combination of a version identity with effective-dated start/end timestamps and an audit actor suggests a satellite pattern — a time-variant descriptive structure keyed to a parent unit set version. The absence of documented foreign keys supports treating it as a self-contained history entity rather than a link between two hubs.

Key Information Stored

The primary key, IGS_EN_UNIT_SET_HIST_ALL_PK, is a composite business key rather than a surrogate: it comprises UNIT_SET_CD, VERSION_NUMBER, and HIST_START_DT. A unique index, IGS_EN_UNIT_SET_HIST_ALL_U1, mirrors these same three columns, confirming them as the authoritative business-key candidates. No separate single-column surrogate identifier is documented.

The most significant columns include:

• UNIT_SET_CD / VERSION_NUMBER — identify which unit set and version the history row describes.
• HIST_START_DT / HIST_END_DT — the effective-dated window for which the recorded attribute values applied.
• HIST_WHO — the user or process responsible for the change event.
• UNIT_SET_STATUS / UNIT_SET_CAT — lifecycle status and category of the unit set at that point in time.
• START_DT / REVIEW_DT / EXPIRY_DT / END_DT — key milestone dates governing the version's validity.
• TITLE / SHORT_TITLE / ABBREVIATION — descriptive labels that may change across versions.
• RESPONSIBLE_ORG_UNIT_CD / ORG_ID / RESPONSIBLE_OU_START_DT / OU_DESCRIPTION — organizational ownership context.
• ADMINISTRATIVE_IND / AUTHORISATION_RQRD_IND — control flags for administrative and approval behavior.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on point-in-time and change-audit reporting. A common pattern retrieves the state of a unit set as of a given date:

• SELECT * FROM IGS_EN_UNIT_SET_HIST_ALL WHERE UNIT_SET_CD = :code AND :as_of BETWEEN HIST_START_DT AND NVL(HIST_END_DT, :as_of);
• Change tracking by actor: filter on HIST_WHO over a date range to identify who altered status or dates.
• Version comparison: join consecutive rows ordered by HIST_START_DT to detect transitions in UNIT_SET_STATUS or EXPIRY_DT.
• Organizational reporting: group by RESPONSIBLE_ORG_UNIT_CD or ORG_ID to attribute changes to business units.

Because the object is obsolete and not implemented, these queries should be treated as reference patterns; active reporting should target the current unit set tables in the same module.

Related Objects

The metadata classifies this object as standalone with no documented foreign keys, so relationships are logical rather than enforced. The most significant associated objects are the current (non-history) unit set definition tables keyed on UNIT_SET_CD and VERSION_NUMBER, the unit set version base table from which these history rows are derived, the organizational unit definition table joined via RESPONSIBLE_ORG_UNIT_CD and ORG_ID, the reference/lookup sets underlying UNIT_SET_STATUS and UNIT_SET_CAT, and the standard EBS user/audit views resolving CREATED_BY and LAST_UPDATED_BY. Join predicates should align on UNIT_SET_CD and VERSION_NUMBER, with date-range matching on HIST_START_DT and HIST_END_DT to obtain the correct historical snapshot.