Results for “igs_ge_s_dsb_tab_trg”

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

Overview

IGS_GE_S_DSB_TAB_TRG is a control table within the Oracle E-Business Suite IGS — Student System product family (classified as obsolete in later releases). Its purpose is administrative rather than transactional: it records the table name and session identifier for which the triggers of a given table are to be disabled. In other words, it functions as a runtime switchboard that suppresses trigger execution on a per-session basis, a technique commonly used during bulk data loads, data migrations, or patching operations where firing application logic at the row level would cause performance degradation or unintended side effects.

The table carries a standalone Data Vault classification (heuristic, mined from its foreign-key structure). As a modeling suggestion, this means the object has no parent or child relationships and would typically be represented as an isolated satellite or a small reference hub rather than as part of a link. Its lack of conformance with other IGS entities reinforces that it is a utility object, not a business entity tracking students, enrollments, or academic records.

Key Information Stored

The documented physical schema (ETRM 12.1.1) reports seven columns owned by the IGS schema. The most operationally significant are:

• TABLE_NAME — The name of the database table whose triggers are to be disabled. This is the principal business attribute.
• SESSION_ID — The Oracle session identifier under which the trigger suppression applies. This scopes the effect so that other concurrent sessions remain unaffected.
• CREATED_BY — Standard EBS WHO column identifying the user who created the row.
• CREATION_DATE — Timestamp of row creation.
• LAST_UPDATED_BY — User who last modified the record.
• LAST_UPDATE_DATE — Timestamp of the last modification.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update.

The primary key is IGS_GE_S_DSB_TAB_TRG_PK, composed of (TABLE_NAME, SESSION_ID). A unique index, IGS_GE_S_DSB_TAB_TRG_U1, covers the same two columns, confirming that the combination constitutes the natural business key. There is no separate surrogate key; the composite of table name and session id serves both as the primary identifier and the business-key candidate.

Common Use Cases and Queries

Because the table is documented as not implemented in this database for the reference environment, practical scripts should first verify its existence. Administrators use it to:

• Determine which tables currently have trigger suppression active for a running session.
• Audit which users or sessions disabled triggers, using the WHO columns.
• Clean up stale rows left behind by failed batch jobs or aborted sessions.

Representative query patterns include:

SELECT table_name, session_id
FROM   igs_ge_s_dsb_tab_trg
WHERE  session_id = SYS_CONTEXT('USERENV','SID');

SELECT table_name, created_by, creation_date
FROM   igs_ge_s_dsb_tab_trg
WHERE  creation_date > SYSDATE - 1;

Reporting use cases are limited, as the table normally holds only transient rows. A purge query removing rows for sessions no longer active is a common maintenance task.

Related Objects

The ETRM metadata identifies this object as standalone, meaning no foreign-key relationships to parent or child tables are documented. Consequently, no declared join columns exist beyond the composite primary key (TABLE_NAME, SESSION_ID). Objects that conceptually interact with it include:

• IGS_GE_S_DSB_TAB_TRG_PK — the primary key constraint enforcing uniqueness of (TABLE_NAME, SESSION_ID).
• IGS_GE_S_DSB_TAB_TRG_U1 — the unique index on the same columns.
• IGS Student System batch and interface programs that disable triggers during processing.
• Application trigger logic in the referenced TABLE_NAME that consults suppression state.

Any query joining this table to other IGS objects must be constructed manually on TABLE_NAME, since no FK constraint supplies the relationship. Given the obsolete status of the IGS Student System in EBS 12.1.1 and 12.2.2, the table should be treated as legacy and is unlikely to appear in current production data models.