Results for “igs_da_in_prg”

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

Overview

IGS_DA_IN_PRG is a transactional table in the IGS (Student System) product schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It serves as the staging and storage structure for inbound program-level information supplied by third-party systems in connection with a Degree Audit Request. When external degree-audit engines or partner institutions transmit program enrollment, completion, and performance data for a student, that payload is decomposed into the degree audit request header, the student line, and the program detail rows persisted in this table.

Under the heuristic Data Vault classification mined from its foreign key topology, IGS_DA_IN_PRG is satellite-leaning. The pattern is characteristic of a satellite: the table carries a surrogate primary key (PRGM_SEQ_IN_ID) plus descriptive, time-stamped attributes, and it hangs off a parent request/student structure through a batch identifier rather than acting as an independent business hub or as a pure many-to-many link. Modelers treating the degree audit inbound interface as a Data Vault would therefore position this object as a satellite attached to the request-student parent, with the batch and person keys supplying the parent reference.

Key Information Stored

The table is documented with 17 columns. The most significant are:

• PRGM_SEQ_IN_ID — the surrogate primary key, enforced by IGS_DA_IN_PRG_PK and also by unique index IGS_DA_IN_PRG_U1. It uniquely identifies each inbound program record.
• BATCH_ID — identifies the inbound load batch and links the row to the degree audit request/student context.
• PERSON_ID — the student to whom the program record belongs.
• PROG_CODE and PROG_VERSION — the academic program and its version, the core business identifiers for the program being reported.
• PROG_COMP_IND — indicates whether the program is complete.
• PROG_COMP_DATE and PROG_COMP_SRC — the completion date and the source of that completion determination.
• DEGREE_DATE — the degree conferral date associated with the program record.
• PROG_EARNED_CR_PTS, PROG_EARNED_GPA, and PROG_EARNED_GPA_PTS — earned credit points, grade point average, and grade point totals attributed to the program.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the inbound row.

Two unique indexes are documented: IGS_DA_IN_PRG_U1 on PRGM_SEQ_IN_ID and IGS_DA_IN_PRG_U2 on the composite (BATCH_ID, PERSON_ID, PROG_CODE, PROG_VERSION). The second is the meaningful business-key candidate, guaranteeing that a given student has at most one inbound program row per program and version within a batch.

Common Use Cases and Queries

Typical usage centers on reconciling what a third party reported against the institution's own program and completion records, and on diagnosing inbound degree audit loads. Common access patterns include retrieving all inbound programs for a batch or student, and comparing reported completion and GPA figures to internal values.

• Retrieve all inbound program rows for a student in a batch:
  SELECT prgm_seq_in_id, prog_code, prog_version, prog_comp_ind, prog_comp_date, prog_earned_gpa FROM igs.igs_da_in_prg WHERE batch_id = :batch_id AND person_id = :person_id;
• List completed programs reported inbound:
  SELECT person_id, prog_code, prog_version, prog_comp_date FROM igs.igs_da_in_prg WHERE prog_comp_ind = 'Y' ORDER BY person_id, prog_code;
• Audit stale or recently refreshed inbound rows using the audit columns:
  SELECT prgm_seq_in_id, last_updated_by, last_update_date FROM igs.igs_da_in_prg WHERE last_update_date >= :since;
• Detect duplicates or business-key violations across the composite key (BATCH_ID, PERSON_ID, PROG_CODE, PROG_VERSION) before they collide with IGS_DA_IN_PRG_U2.

Reporting extracts commonly join this table to the request-student parent to present a per-student view of third-party program outcomes during degree audit processing.

Related Objects

The documented foreign keys establish the principal relationships for this table:

• IGS_DA_REQ_STDNTS — parent table referenced via IGS_DA_IN_PRG.BATCH_ID; provides the degree audit request/student context for each inbound program row.
• IGS_DA_IN_USET — child/dependent table that references this table through its PRGM_SEQ_IN_ID column, carrying the associated inbound usage or detail set records.
• IGS_DA_IN_PRG_PK — the primary key constraint on PRGM_SEQ_IN_ID that anchors row identity.
• IGS_DA_IN_PRG_U1 — unique index on PRGM_SEQ_IN_ID.
• IGS_DA_IN_PRG_U2 — composite unique index on (BATCH_ID, PERSON_ID, PROG_CODE, PROG_VERSION).

These objects should be treated together when tracing a degree audit inbound load from request header through student line to program detail and its usage detail, since the batch identifier is the common thread binding the inbound request structure to the program-level rows stored here.