Results for “bottom_text”

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

Overview

IGS_DA_OUT_USR_DEF is a table in the Oracle E-Business Suite IGS – Student System schema, now classified as obsolete in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to store outgoing institution-specific information that must be transmitted for each student within a Degree Audit Request. In practice, the table serves as a staging and persistence layer for the personalized text and user-defined exceptions that an institution appends to degree audit output before it is delivered to a student or advisor.

Within the ETRM metadata, the table is described as not implemented in the current database, meaning its physical presence depends on whether the Degree Audit customization was ever deployed. The heuristic Data Vault classification is satellite-leaning, which suggests modeling this object as a satellite entity attached to a parent request-student key, rather than as an independent hub or a link. This modern-modeling suggestion aligns with the table's role: it holds descriptive attributes keyed by an existing business relationship.

Key Information Stored

The table carries 30 documented columns in the 12.1.1 schema, grouped into business payload, descriptive flexfield, and standard WHO audit columns. The most significant columns are:

• BATCH_ID and PERSON_ID — the composite primary key (IGS_DA_OUT_USR_DEF_PK) and the unique business-key candidate (IGS_DA_OUT_USR_DEF_U1). Together they identify one institution-specific output record for a student within a degree audit batch.
• TOP_TEXT and BOTTOM_TEXT — free-form institution text rendered at the top and bottom of the outgoing degree audit document.
• USER_EXCPT1 through USER_EXCPT5 — five institution-defined exception fields used to flag or annotate special conditions in the outgoing audit.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield segment set, allowing each institution to extend the table with additional context-specific data without schema changes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard WHO audit columns, enabling traceability of when and by whom each record was created or modified.

The surrogate primary key is therefore IGS_DA_OUT_USR_DEF_PK, while the unique index IGS_DA_OUT_USR_DEF_U1 (BATCH_ID, PERSON_ID) represents the business-key candidate that enforces one record per student per batch.

Common Use Cases and Queries

Because the table stores institution-specific audit output, typical usage centers on generating, reviewing, and troubleshooting degree audit documents. Common scenarios include verifying that institution text was persisted for a batch, auditing which students received customized exceptions, and extracting audit content for reporting or archival.

A representative query retrieving output for a specific batch is:

• SELECT batch_id, person_id, top_text, bottom_text, user_excpt1, user_excpt5 FROM igs_da_out_usr_def WHERE batch_id = :batch_id;
• SELECT person_id, COUNT(*) FROM igs_da_out_usr_def GROUP BY person_id HAVING COUNT(*) > 1; to validate the uniqueness enforced by IGS_DA_OUT_USR_DEF_U1.
• Joins to IGS_DA_REQ_STDNTS on BATCH_ID and PERSON_ID to reconcile institutional output with the underlying student degree audit request.

Reporting use cases include producing batch exception summaries and extracting TOP_TEXT/BOTTOM_TEXT for document reconstruction.

Related Objects

The documented foreign key relationship links this table to the degree audit request student table. Significant related objects include:

• IGS_DA_REQ_STDNTS — referenced by IGS_DA_OUT_USR_DEF.BATCH_ID and PERSON_ID; the parent student request table for the batch.
• IGS_DA_OUT_USR_DEF_PK — the primary key constraint over BATCH_ID and PERSON_ID.
• IGS_DA_OUT_USR_DEF_U1 — the unique index enforcing one output record per student per batch.
• Degree audit request and output tables within the IGS schema that share the batch/student key model.

As an obsolete object, IGS_DA_OUT_USR_DEF should be treated as a legacy artifact; any new development should confirm physical existence before relying on it in queries or integrations.