Results for “program_ver_num”

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

Overview

IGS_EN_BLK_SUA_INTS is a staging (interface) table within the Oracle E-Business Suite Student System module (IGS), which is documented as obsolete in current releases. The table holds Student Unit Attempt information destined for import into the IGS_EN_SI_ATTEMPT_ALL table, which stores current unit attempts. It functions as an intermediate holding area: rows are loaded into this table, validated, and then processed by the Student System import routines before final persistence in the production attempt tables.

Every row in IGS_EN_BLK_SUA_INTS must correspond to a batch defined in IGS_EN_BAT_SUA_INTS. This batch-level grouping allows a set of student unit attempt records to be uploaded, validated, and committed as a logical unit of work, with error information captured per row. The documented physical schema under ETRM 12.1.1 records the owner as IGS with 28 columns.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table carries descriptive and status attributes tied to a parent batch, with the UPLOAD_ID acting as the unique business key rather than a pure hub identifier. This classification is a heuristic suggestion only and should be validated against the intended integration model.

Key Information Stored

The primary key constraint IGS_EN_BLK_SUA_INTS_PK is defined on UPLOAD_ID, making it both the surrogate primary key and the sole documented unique index (business-key candidate) for the table. Key columns include:

• UPLOAD_ID — primary key; uniquely identifies each staged upload record.
• BATCH_ID — foreign key referencing IGS_EN_BAT_SUA_INTS; groups rows into an import batch.
• PERSON_NUMBER — identifies the student associated with the unit attempt.
• PROGRAM_CD, PROGRAM_VER_NUM — program code and version for the student's enrolment.
• UNIT_CD, UNIT_VER_NUM — the unit (course) being attempted and its version.
• LOCATION_CD, UNIT_CLASS, ALTERNATE_CD — delivery location, class, and alternate code for the attempt.
• STATUS_FLAG, AUDIT_FLAG, UPDATE_CORE_FLAG — processing state indicators used during validation and post-import handling.
• GRADING_SCH_CD, GRADING_SCH_VER_NUM, VARIABLE_CR_POINT — grading scheme and credit point data.
• ERROR_TXT — captures validation or import error messages for the row.
• REQUEST_ID — links the row to the concurrent request that processed it.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle who-columns for audit.

Common Use Cases and Queries

Typical use cases centre on batch import, error triage, and reconciliation of staged versus imported attempts. Because the user search term was "upload_id," the most frequent query pattern filters or joins on this column:

• Retrieve all staged rows for a batch: SELECT * FROM IGS_EN_BLK_SUA_INTS WHERE BATCH_ID = :batch_id;
• Locate a specific upload record: SELECT * FROM IGS_EN_BLK_SUA_INTS WHERE UPLOAD_ID = :upload_id;
• Identify failed rows for correction: SELECT UPLOAD_ID, PERSON_NUMBER, UNIT_CD, ERROR_TXT FROM IGS_EN_BLK_SUA_INTS WHERE ERROR_TXT IS NOT NULL;
• Trace rows to the concurrent request that processed them via REQUEST_ID.
• Reconcile staged attempts against IGS_EN_SI_ATTEMPT_ALL using PERSON_NUMBER, UNIT_CD, and UNIT_VER_NUM.

Related Objects

• IGS_EN_BAT_SUA_INTS — parent batch table; joined via IGS_EN_BLK_SUA_INTS.BATCH_ID = IGS_EN_BAT_SUA_INTS.BATCH_ID.
• IGS_EN_SI_ATTEMPT_ALL — target table receiving validated current unit attempts.
• IGS_EN_BLK_SUA_INTS_PK — primary key constraint on UPLOAD_ID.
• Standard concurrent request and error logging objects referenced through REQUEST_ID and ERROR_TXT.