Results for “igs_da_in_rslt_unts”

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

Overview

The IGS_DA_IN_RSLT_UNTS table is an inbound staging and persistence structure within the Oracle E-Business Suite Student System (IGS) module. It stores resultant unit information received from a third-party degree audit engine concerning the units (courses, modules, or credit-bearing components) attributed to students who are the subject of a Degree Audit request. In the ETRM 12.1.1 and 12.2.2 documentation set, the object is classified as Obsolete, and implementation records indicate it is not implemented in the current database; nevertheless, its schema remains documented for upgrade, migration, and historical reference purposes.

The module owns the table under the IGS schema, and the documented physical schema at 12.1.1 lists 51 columns. From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This suggests that the table functions primarily as a descriptive attribute container attached to a parent business key rather than as an independent hub of unique business entities. The parent relationship is expressed through the foreign key to IGS_DA_REQ_STDNTS via BATCH_ID and PERSON_ID, implying the table records the detailed outcomes associated with each student row produced for a degree audit request batch.

Key Information Stored

The surrogate primary key of the table is RSLT_UNIT_ID, enforced by the constraint IGS_DA_IN_RSLT_UNTS_PK and reinforced by the unique index IGS_DA_IN_RSLT_UNTS_U1. Because RSLT_UNIT_ID appears both as the PK and as the sole unique index column, it is the only documented business-key candidate; no composite natural key is exposed in the metadata.

The most operationally significant columns are:

• BATCH_ID and PERSON_ID — together forming the association to the parent degree audit request student record in IGS_DA_REQ_STDNTS.
• RESLT_UNIT_CODE, RESLT_UNIT_CODE_VERSION, and RESLT_UNIT_TITLE — the identified unit, its version, and its descriptive title.
• RESLT_UNIT_INST_ID and RESLT_UNIT_ALT_INST_ID — institutional identifiers for the awarding or referenced institution.
• RESLT_UNIT_EARNED_CRED, RESLT_UNIT_GRADE, RESLT_UNIT_GPA_PTS, and RESLT_UNIT_QUAL_PTS_EARNED — the academic outcome measures returned by the third party.
• RESLT_UNIT_LEVEL, RESLT_UNIT_LEVEL_TITLE, and RESLT_UNIT_TEACH_PERIOD — the academic level and teaching period context.
• RESLT_UNIT_PSEUDO_FLAG and the numbered RESLT_UNIT_FLAG1 through RESLT_UNIT_FLAG5 columns — indicator flags used to qualify how the unit should be interpreted.
• The repeated RESLT_DA_UNIT_CODE1 through RESLT_DA_UNIT_CODE12 columns — a denormalized array of audit-specific unit codes.
• Standard audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The primary use case is reconstructing the third-party degree audit outcome for a student or batch. Because the table is obsolete, queries are typically confined to historical data extraction rather than live processing. A typical join retrieves all resultant units for a request student:

• SELECT u.RSLT_UNIT_ID, u.RESLT_UNIT_CODE, u.RESLT_UNIT_TITLE, u.RESLT_UNIT_EARNED_CRED, u.RESLT_UNIT_GRADE FROM IGS_DA_IN_RSLT_UNTS u WHERE u.BATCH_ID = :batch_id AND u.PERSON_ID = :person_id;
• Aggregate earned credit per student: SELECT PERSON_ID, SUM(RESLT_UNIT_EARNED_CRED) FROM IGS_DA_IN_RSLT_UNTS GROUP BY PERSON_ID;
• Detect pseudo or flagged units: SELECT * FROM IGS_DA_IN_RSLT_UNTS WHERE RESLT_UNIT_PSEUDO_FLAG = 'Y';
• Reconciliation of the twelve denormalized RESLT_DA_UNIT_CODE positions against the canonical RESLT_UNIT_CODE.

Related Objects

The documented foreign key relationship links IGS_DA_IN_RSLT_UNTS.BATCH_ID and PERSON_ID to IGS_DA_REQ_STDNTS, the parent request-student table. This is the principal dependency. Other objects of significance in the degree audit inbound flow include IGS_DA_REQ_STDNTS (parent request/student context), the degree audit request header structures that feed BATCH_ID, degree audit result header and group tables that typically sit alongside the unit results, and the Student System person and institution reference tables implied by PERSON_ID, RESLT_UNIT_INST_ID, and RESLT_REF_INST_ID. Because the object is documented as obsolete and not implemented, direct API or view dependencies are not enumerated in the ETRM metadata; joins should be validated against the deployed schema before operational use.