Results for “igs_en_bat_sua_ints”

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

Overview

IGS_EN_BAT_SUA_INTS is a control table within the Oracle E-Business Suite IGS (Student System) module, historically used to store batch header information for Student Unit Attempt (SUA) upload processing. Its functional purpose is to hold one row per upload batch, providing the metadata required by a concurrent program that imports or processes student unit attempt records. The row must exist before the concurrent program is executed for that batch, making this table a prerequisite control structure rather than a transactional staging table in the conventional sense.

The object is documented in ETRM 12.1.1 with an owner of IGS and a total of seven physical columns. In the Oracle EBS 12.1.1 and 12.2.2 context, the IGS product line is flagged as obsolete; therefore this table appears primarily in historical or legacy schemas. Notably, the ETRM implementation metadata records that the table is not implemented in the reference database, so in many environments it will only exist where the Student System was originally licensed and deployed.

Applying a Data Vault heuristic to the documented foreign key topology, this table is classified as hub-leaning. It behaves as a business hub because it holds a stable, uniquely identified batch entity keyed by BATCH_ID, and other tables reference it rather than the reverse. This classification is a modeling suggestion derived from the foreign key structure, not a statement about how Oracle physically designed the table.

Key Information Stored

The documented schema consists of seven columns. The most significant are:

• BATCH_ID — the single-column primary key, defined by the unique index IGS_EN_BAT_SUA_INTS_PK. It is the surrogate identifier that uniquely distinguishes each upload batch and is the column referenced by all child tables.
• BATCH_DESC — the descriptive attribute that gives the batch a human-readable name or purpose, used to identify a batch in concurrent program parameters and inquiry screens.
• CREATED_BY — the standard EBS WHO column capturing the application user who created the batch record.
• CREATION_DATE — the timestamp for row creation, supporting audit and ageing analysis of pending batches.
• LAST_UPDATED_BY — the user who most recently modified the batch header.
• LAST_UPDATE_DATE — the modification timestamp, used to track batch edits and to drive incremental extracts.
• LAST_UPDATE_LOGIN — the login/session identifier associated with the last update, completing the standard EBS audit signature.

In this table, BATCH_ID serves simultaneously as primary key and as the only documented unique business-key candidate; there is no separate natural or alternate key column recorded in the metadata. The remaining six columns are descriptive and audit attributes rather than identifiers.

Common Use Cases and Queries

The principal use case is identifying and validating a batch before launching the SUA upload concurrent program. A prerequisite check confirms that a header row exists for the batch identifier supplied as a program parameter. Typical query patterns include retrieving a batch description for display, listing all batches created within a date range, and auditing batches that have not been updated since creation.

• Batch lookup: SELECT batch_id, batch_desc FROM igs_en_bat_sua_ints WHERE batch_id = :p_batch_id;
• Recent batch listing: SELECT batch_id, batch_desc, creation_date FROM igs_en_bat_sua_ints WHERE creation_date >= :p_from_date ORDER BY creation_date DESC;
• Audit trail: SELECT batch_id, created_by, creation_date, last_updated_by, last_update_date FROM igs_en_bat_sua_ints WHERE batch_id = :p_batch_id;

Reporting use cases centre on batch volume and throughput: counting batches per creation date or per creating user, and reconciling header records against their child detail rows.

Related Objects

The documented relationship metadata identifies one dependent table, with the foreign key defined on the child side:

• IGS_EN_BLK_SUA_INTS — the detail or block-level SUA staging table, joined via IGS_EN_BLK_SUA_INTS.BATCH_ID = IGS_EN_BAT_SUA_INTS.BATCH_ID. This is the primary child of the batch hub and the object most frequently joined in reconciliation queries.

Beyond the documented foreign key, the concurrent program responsible for the SUA upload consumes this header, and EBS standard audit columns link back to the FND_USER and session infrastructure. Because the IGS product is obsolete and the table is not implemented in the reference database, downstream custom reports and interfaces should be verified per environment before relying on join results.