Search Results deg_aud_detail_id




Overview
Explore in AI Chat

Overview

IGS_DA_DETAILS_HIST is a history (audit) table within the Oracle E-Business Suite Student System (IGS) product module. It stores the historical versions of Degree Audit details, preserving the state of degree audit unit evaluations over time. Degree audits evaluate a student's academic record against program, plan, and subplan requirements to determine progress toward graduation. The base table IGS_DA_DETAILS holds the current degree audit detail rows; IGS_DA_DETAILS_HIST retains prior versions of those rows so that changes to audit outcomes, unit flags, and comments can be reconstructed as of any point in time.

The table is owned by the IGS schema and is documented as VALID in the ETRM reference for both EBS 12.1.1 and 12.2.2, with 68 columns. Its primary key, IGS_DA_DETAILS_HIST_PK, is composed of DEG_AUD_DETAIL_ID and HIST_START_DT, and a unique index, IGS_DA_DETAILS_HIST_U1, exists on the same column pair. From a data vault modeling perspective, the metadata heuristically classifies this object as a standalone structure. Because it is a history table keyed by the source row identifier plus an effective date, it is most naturally modeled as a satellite hanging off the degree audit detail business key, rather than as a hub or link. This classification is a modeling suggestion only; the physical implementation is a conventional EBS history table with no formal foreign keys declared in the mined relationship data.

Key Information Stored

The table is organized around the effective-dating and ownership of a degree audit detail row, supplemented by unit evaluation attributes and a standard 20-column descriptive flexfield.

  • DEG_AUD_DETAIL_ID — surrogate identifier of the source degree audit detail row; part of the composite primary key and the primary business-key candidate.
  • HIST_START_DT — effective start date of the historical version; the second component of the composite primary key and unique index.
  • HIST_END_DT — effective end date of the version, defining the validity window of each historical row.
  • HIST_WHO — the user or process that created the historical version.
  • OSS_UNIT_LOCATOR — locator identifying the academic unit within the audit structure.
  • UNIT_CD, UNIT_VERSION, UNIT_LEVEL_CD, UNIT_TERM, UNIT_SEQ_CODE — the academic unit code and its version, level, term, and sequence context used in the audit evaluation.
  • DA_COUNT — count value recorded for the degree audit detail evaluation.
  • UNIT_PSEUDO_UNIT_FLG, UNIT_EVAL_LOCK — flags indicating pseudo-unit status and whether evaluation is locked.
  • DA_GROUP, DPMASK — grouping and display mask attributes used by the degree audit presentation layer.
  • DEG_AUD_COMMENTS — free-text comments associated with the audit detail.
  • REF_INST_ID, REF_INST_CODE, REF_TITLE — reference institution identifier, code, and title for transfer or external credit context.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the descriptive flexfield segment values used for client-specific extensions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row.

The surrogate/primary key is the pair (DEG_AUD_DETAIL_ID, HIST_START_DT); the unique index IGS_DA_DETAILS_HIST_U1 covers the same columns and therefore confirms this pair as the business-key candidate. Columns such as ALT_UNIT_ID1 through ALT_UNIT_ID3, the DEG_AUD_UNIT_CODE1 through DEG_AUD_UNIT_CODE12 series, and UNIT_FLAG1 through UNIT_FLAG5 store repeating audit attributes but are not part of the key.

Common Use Cases and Queries

The principal use case is temporal reconstruction of degree audit outcomes — determining what a student's audit detail looked like on a prior date, or identifying what changed between two audit runs. Typical patterns include:

  • Point-in-time retrieval: select rows where HIST_START_DT is on or before the target date and HIST_END_DT is null or after it.
  • Change analysis: compare successive versions of the same DEG_AUD_DETAIL_ID ordered by HIST_START_DT to isolate edits to DA_COUNT, flags, or comments.
  • Audit trail reporting: join to IGS_DA_DETAILS on DEG_AUD_DETAIL_ID to reconcile current versus historical rows.
  • User accountability: group by HIST_WHO, CREATED_BY, or LAST_UPDATED_BY to report who modified audit details.

A representative query selects the active historical version for a given detail identifier by filtering on the effective date window and ordering by HIST_START_DT descending. Reports typically project DEG_AUD_DETAIL_ID, HIST_START_DT, HIST_END_DT, UNIT_CD, UNIT_TERM, DA_COUNT, and DEG_AUD_COMMENTS.

Related Objects

Relationship data classifies this object as standalone with no declared foreign keys, so associations are inferred from the degree audit data model rather than enforced constraints. The most significant related objects are:

  • IGS_DA_DETAILS — the current degree audit details table, joined on DEG_AUD_DETAIL_ID.
  • IGS_DA_DETAILS_HIST_PK — the primary key constraint enforcing uniqueness of (DEG_AUD_DETAIL_ID, HIST_START_DT).
  • IGS_DA_DETAILS_HIST_U1 — the unique index on the same key columns.
  • Degree audit header and group tables in the IGS schema that key audit runs, linked through the audit detail identifiers and DA_GROUP.
  • Academic unit and unit version reference tables referenced by UNIT_CD, UNIT_VERSION, and UNIT_LEVEL_CD.
  • Institution reference objects associated with REF_INST_ID and REF_INST_CODE.
  • EBS standard who-column references (FND_USER) matched against CREATED_BY, LAST_UPDATED_BY, and HIST_WHO.

Because no formal foreign keys are documented, join relationships should be validated against the base IGS_DA_DETAILS table and the degree audit PL/SQL APIs that maintain both the current and historical rows in parallel.