Results for “igs_ad_imp_batch_det”

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

Overview

IGS_AD_IMP_BATCH_DET is a transactional control table within the IGS (Student System) schema of Oracle E-Business Suite, documented as VALID in ETRM 12.1.1 and 12.2.2. Its described purpose is the "Import Process Batch Description table" — it stores one row per batch identifier used by the Admissions (AD) import/concurrent process infrastructure, holding the descriptive label assigned to each batch. Rather than storing student records themselves, the table acts as the batch registry that other interface-staging tables point to, allowing imported admission data to be grouped, labeled, and traced back to the originating process run.

The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. In modeling terms, this suggests treating IGS_AD_IMP_BATCH_DET as a hub: its single-column primary key, BATCH_ID, is a stable, non-repeating business identifier that other tables reference. The descriptive and audit columns would then be carried as hub attributes or pushed to a satellite, while IGS_AD_INTERFACE_CTL functions as a link/satellite referencing the hub.

Key Information Stored

The documented physical schema contains 11 columns. The most significant are:

• BATCH_ID — the surrogate primary key and sole column of the unique index IGS_AD_IMP_BATCH_DET_PK. This is the value propagated to dependent interface tables.
• BATCH_DESC — the human-readable description or label for the batch; the principal business attribute of the row and the field most often surfaced in reports and LOVs.
• REQUEST_ID — the concurrent request that created the batch, enabling traceability from a batch back to its submission.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — identify the concurrent program definition that populated the batch.
• PROGRAM_UPDATE_DATE — the date stamp maintained by the concurrent manager of the responsible program.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "WHO" audit columns recording row creation and last modification.

BATCH_ID is the only documented unique index; no additional business-key candidate is defined, so uniqueness of the batch is guaranteed by the primary key alone, and BATCH_DESC should be treated as descriptive rather than a key.

Common Use Cases and Queries

Typical usage centres on identifying and reporting on import batches, resolving batch descriptions from foreign-key values, and auditing which concurrent request produced a batch.

• Resolving a description from a dependent table: SELECT b.BATCH_ID, b.BATCH_DESC FROM igs.igs_ad_imp_batch_det b, igs.igs_ad_interface_ctl c WHERE c.batch_id = b.batch_id;
• Auditing batch creation by request: SELECT batch_id, batch_desc, request_id, creation_date FROM igs.igs_ad_imp_batch_det WHERE request_id = :p_request_id;
• Reporting recent batches by program: filtering on PROGRAM_ID or PROGRAM_APPLICATION_ID joined to FND_CONCURRENT_PROGRAMS.

Because the table is narrow and key-driven, queries generally perform well when driven by BATCH_ID or by the audit and program columns, which support date- and process-based reporting.

Related Objects

• IGS_AD_INTERFACE_CTL — references this table via IGS_AD_INTERFACE_CTL.BATCH_ID. This is the documented dependent, joining interface control rows to their batch description.
• FND_CONCURRENT_REQUESTS — joins on REQUEST_ID to retrieve request status and timing for a batch.
• FND_CONCURRENT_PROGRAMS — joins on PROGRAM_APPLICATION_ID and PROGRAM_ID to identify the populating program.
• FND_USER — joins on CREATED_BY / LAST_UPDATED_BY to resolve user names.
• FND_APPLICATION — resolves PROGRAM_APPLICATION_ID to the owning application short name.

Access to IGS_AD_IMP_BATCH_DET should be read-only from reporting and integration layers; batches are created and maintained through the seeded IGS import concurrent programs.