Results for “igs_da_in_usr_def”

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

Overview

IGS_DA_IN_USR_DEF is a table owned by the IGS schema within the Oracle E-Business Suite Student System module. It stores incoming user-specific information captured for a student in the context of a Degree Audit Request. In the degree audit process, institutions frequently need to capture additional, institution-defined attributes — beyond the standard academic record — that influence how a student's progress toward a program requirement is evaluated. This table serves as the storage location for those user-defined data elements as they arrive from an external or upstream request payload.

From a heuristic Data Vault modeling perspective, IGS_DA_IN_USR_DEF exhibits satellite-leaning characteristics. Its primary key (BATCH_ID, PERSON_ID) aligns with the parent request-student grain rather than introducing an independent business entity, and its column set is dominated by descriptive, non-key attributes associated with a single parent context. This suggests it functions as a dependent descriptive table attached to the degree audit request-student relationship, rather than as a standalone hub or an associative link.

Key Information Stored

The table contains 28 documented columns. The composite primary key, enforced by the IGS_DA_IN_USR_DEF_PK constraint, consists of BATCH_ID and PERSON_ID. The IGS_DA_IN_USR_DEF_U1 unique index covers the same two columns, making (BATCH_ID, PERSON_ID) the business-key candidate that uniquely identifies a row. This two-column combination establishes the grain: one record per student per degree audit request batch.

• BATCH_ID — Identifier for the degree audit request batch, linking this incoming data to a specific processing run. Also a foreign key to IGS_DA_REQ_STDNTS.
• PERSON_ID — The student's person identifier within the Student System, also a foreign key to IGS_DA_REQ_STDNTS.
• USER_DEFINED1 through USER_DEFINED5 — Institution-specific fields available to capture custom values supplied with the degree audit request.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — A flexible descriptive flexfield (DFF) structure providing up to fifteen additional user-defined segments, with ATTRIBUTE_CATEGORY identifying the applicable context or structure of those segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording when and by whom each record was inserted or last modified.

The distinction between the surrogate-style PK/U1 grain on (BATCH_ID, PERSON_ID) and the descriptive flexfield columns is important: the key columns enforce uniqueness and parentage, while the USER_DEFINED and ATTRIBUTE columns hold the actual business payload of institution-defined data.

Common Use Cases and Queries

Typical usage involves extracting or validating the user-defined data submitted with a degree audit request. A common pattern joins this table to its parent to retrieve student context alongside the custom attributes:

• Retrieving all user-defined data for a specific request batch: SELECT * FROM IGS_DA_IN_USR_DEF WHERE BATCH_ID = :p_batch_id;
• Fetching a single student's record within a batch: SELECT * FROM IGS_DA_IN_USR_DEF WHERE BATCH_ID = :p_batch_id AND PERSON_ID = :p_person_id; — this leverages the IGS_DA_IN_USR_DEF_U1 unique index for a precise, single-row lookup.
• Reporting on populated flexfield values: filtering on ATTRIBUTE_CATEGORY and specific ATTRIBUTE1..15 segments to audit which institutions are supplying which custom data elements.
• Joining to the parent to correlate user-defined values with request-student records: SELECT u.* FROM IGS_DA_IN_USR_DEF u, IGS_DA_REQ_STDNTS s WHERE u.BATCH_ID = s.BATCH_ID AND u.PERSON_ID = s.PERSON_ID;
• Data-quality checks for completeness, such as counting records where all USER_DEFINED columns are null for a given batch.

Because the table shares its key columns with IGS_DA_REQ_STDNTS, batch-level and student-level reporting are natural fits, supporting both operational monitoring of degree audit submissions and downstream analytics on institution-specific criteria.

Related Objects

• IGS_DA_REQ_STDNTS — The direct parent table referenced by the foreign key on IGS_DA_IN_USR_DEF.BATCH_ID and PERSON_ID. It holds the degree audit request-student records, and every row in IGS_DA_IN_USR_DEF should correspond to a row here.
• IGS_DA_IN_USR_DEF_PK — The primary key constraint enforcing uniqueness on (BATCH_ID, PERSON_ID).
• IGS_DA_IN_USR_DEF_U1 — The unique index over (BATCH_ID, PERSON_ID), which is the usable business-key candidate for conflict detection and upsert logic.
• Degree Audit request processing logic within the IGS module — the batch identifiers originated from the degree audit request framework that populates IGS_DA_REQ_STDNTS and feeds user-defined data into this table.
• IGS_DA_* family tables — Other degree audit tables at the same request/batch grain that share BATCH_ID and PERSON_ID semantics and can be joined for broader reporting.

Because the documented foreign key metadata points solely to IGS_DA_REQ_STDNTS, that table is the most significant dependency. Any purge, archive, or reconciliation of degree audit request data must respect the parent-child relationship through BATCH_ID and PERSON_ID to preserve referential integrity.