Search Results igs_pr_spa_complete_int_pk

Overview

IGS_PR_SPA_COMPLETE_INT is an interface (staging) table within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to receive Student Program Attempt Completion records from external source systems prior to validation and import into the core Student System schema. In the context of Oracle EBS 12.1.1 and 12.2.2, tables bearing the _INT suffix are conventionally populated by external feeds — legacy student record systems, third-party awarding bodies, or batch loaders — and then processed by concurrent programs that stage, validate, and ultimately insert or update the corresponding base entities.

The ETRM metadata classifies this object as obsolete and notes that it is not implemented in this database. Its continued documentation reflects the historical IGS data model rather than an active deployment in current 12.1.1 or 12.2.2 instances. The heuristic Data Vault classification derived from the foreign-key structure is standalone, suggesting this object behaves as an independent staging table rather than a modeled hub, link, or satellite. Under a Data Vault lens, the composite business key (batch, person, course) would typically resolve to a link connecting the student and course hubs, with completion and audit attributes forming a satellite; the metadata, however, supplies no foreign-key links to confirm that interpretation.

Key Information Stored

The documented physical schema (ETRM 12.1.1) contains 10 columns owned by IGS. The primary key, IGS_PR_SPA_COMPLETE_INT_PK, is a composite surrogate constructed from three business-key columns rather than a single generated identifier:

• BATCH_ID — identifies the inbound load batch, allowing an external feed to be grouped, reprocessed, or purged as a unit. It forms the first component of the composite primary key.
• PERSON_NUMBER — the student's person identifier used by the external source. It is a business-key candidate and the second component of the primary key. Because it is an external-facing number, it generally requires resolution against the internal person identity before import.
• COURSE_CD — the course or program-attempt code being reported as complete. It is the third component of the primary key and the principal business discriminator of the record.
• COMPLETE_DT — the date on which the program attempt was completed; this is the primary payload attribute carried by the interface row.
• ERROR_CODE — populated by the import/validation process when an interface row fails, enabling failed records to be isolated for correction and resubmission.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns, recording who created and last modified each interface row and when.

Notably, the table carries no descriptive name, status, or grade attributes in the documented schema; by design it is a thin transport structure carrying only enough information to identify the student, the course, and the completion event.

Common Use Cases and Queries

Typical usage centers on monitoring inbound feeds and diagnosing import failures. A common pattern is to inspect unprocessed or erroneous rows within a specific batch:

• SELECT * FROM igs_pr_spa_complete_int WHERE batch_id = :p_batch_id;
• SELECT * FROM igs_pr_spa_complete_int WHERE error_code IS NOT NULL; — identifies rejected rows requiring correction.
• SELECT batch_id, COUNT(*), MIN(complete_dt), MAX(complete_dt) FROM igs_pr_spa_complete_int GROUP BY batch_id; — batch-level reconciliation of volume and date range.
• SELECT person_number, course_cd, complete_dt FROM igs_pr_spa_complete_int WHERE complete_dt >= :start_date; — reporting on recent completions awaiting import.

Reporting should be restricted to operational and reconciliation purposes. Because the table is documented as obsolete and unimplemented, queries against it in a live 12.1.1 or 12.2.2 instance will typically fail with an ORA-00942 error unless a site-specific legacy object coincidentally exists.

Related Objects

The provided relationship data describes this table as standalone, with no documented foreign keys, and names only its own primary key constraint (IGS_PR_SPA_COMPLETE_INT_PK). Consequently, no authoritative join targets can be asserted. By convention within the IGS schema, an interface table of this type would feed the core Student Program Attempt tables — such as IGS_PR_SPA (Student Program Attempt) and its completion-related children — through a concurrent import program that resolves PERSON_NUMBER to the internal person identifier and COURSE_CD to the internal course/version identifier. The BATCH_ID column would likewise be associated with a batch-control entity governing concurrent processing. These relationships are architectural inferences, not documented foreign-key dependencies, and should be verified against the specific instance before use.