Results for “igs_en_reg_btch_int”

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

Overview

The IGS_EN_REG_BTCH_INT table is a core staging object within the Oracle E-Business Suite IGS — Student System product. It holds batch-level header information for student registration data that is loaded into the application through concurrent processing. Rather than registering students individually, institutions can assemble a batch of registration records and submit that batch to a concurrent program for validation and processing. The table is therefore a prerequisite control object: a batch row must exist before the associated registration interface records can be processed.

Under Oracle EBS 12.1.1 the table resides in the IGS schema and is documented as VALID. The documented physical schema exposes seven columns and a single unique index. From a data-modelling perspective, the mined foreign-key structure classifies this object as standalone. In Data Vault terms it is best characterised as a hub-like candidate — it carries a single surrogate identifier with no documented parent or child relationships — although the absence of explicit parent keys means it should be modelled pragmatically as an independent batch registry rather than a fully normalised hub.

Key Information Stored

The table is deliberately narrow; it stores batch identity and standard Oracle audit metadata rather than the registration lines themselves.

• BATCH_ID — the surrogate primary key, enforced through the unique index IGS_EN_REG_BTCH_INT_PK. This is also the only documented business-key candidate, and it is the value stamped onto downstream registration interface rows to tie them back to their parent batch.
• BATCH_DESCRIPTION — a free-text descriptor that identifies the batch for users, typically encoding the institution, term, registration window, or load cycle so that operators can distinguish concurrent submissions.
• CREATED_BY — the Oracle Applications user ID of the operator who created the batch row.
• CREATION_DATE — the timestamp at which the batch was first registered in the table.
• LAST_UPDATED_BY — the user ID responsible for the most recent modification to the batch row.
• LAST_UPDATE_DATE — the timestamp of the most recent update, used for auditing and for incremental extraction.
• LAST_UPDATE_LOGIN — the login session identifier associated with the last update, supporting session-level traceability.

No other columns are documented in the ETRM extract. The audit columns follow the standard Oracle EBS WHO-column convention and are populated automatically by the Forms or concurrent-manager framework.

Common Use Cases and Queries

The primary operational use case is batch-orchestration: a registration operator inserts a batch row, attaches interface rows that reference it, and then launches the registration concurrent program with that BATCH_ID as a parameter. Because the table is small and heavily filtered, most queries are point lookups or status sweeps.

• Retrieving a specific batch: SELECT batch_id, batch_description, creation_date FROM igs_en_reg_btch_int WHERE batch_id = :p_batch_id;
• Listing recently created batches for an operator: filter on CREATED_BY and order by CREATION_DATE DESC.
• Audit reporting: compare CREATION_DATE with LAST_UPDATE_DATE to detect batches that were modified after initial load.
• Incremental extraction: use LAST_UPDATE_DATE as a high-water mark for ETL feeds into a data warehouse.
• Pre-submission validation: confirm that a batch row exists before invoking the concurrent program, since the documentation states the table is required for each batch prior to execution.

Related Objects

The metadata describes this table as standalone with no documented foreign keys, so relationships are inferred from the IGS registration interface family rather than enforced constraints.

• IGS_EN_REG_BTCH_INT child/interface tables in the IGS registration load family, joined on BATCH_ID, which carry the individual student registration lines belonging to each batch.
• The concurrent program that consumes BATCH_ID as its submission parameter, driving validation and transfer of the staged registrations.
• IGS student registration base tables, populated once the concurrent process validates and commits the staged batch.
• Oracle Applications standard audit and user tables referenced implicitly through CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• Any custom inbound interface that inserts batch rows prior to invoking the registration program.