Results for “program_version”

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

Overview

IGS_DA_REQ_WIFPRGS is a transaction table within the IGS (Student System) product family of Oracle E-Business Suite, appearing in both 12.1.1 and 12.2.2 environments with a VALID status in the IGS schema. The table stores "What-If" program selections associated with a Degree Audit request submitted for a student. The description explicitly limits the applicability of these records: What-If program storage is permitted only for Single Request types, not for Batch processing. This constraint reflects the interactive, exploratory nature of What-If degree audits, in which a student or advisor simulates academic progress against an alternate program of study outside the normal batch audit cycle.

From a modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. The table behaves as a satellite capturing descriptive, context-dependent attributes attached to a parent request hub or link, rather than as an independent hub of business entities. Its promotion to hub status is not warranted because its identity is largely derived from the parent Degree Audit request.

Key Information Stored

The physical schema documents twelve columns. The most significant are listed below.

• BATCH_ID — Identifier of the parent Degree Audit request record. This column is part of the composite primary key and the primary foreign key path to IGS_DA_RQST.
• PROGRAM_CODE — Code of the What-If program the student wishes to simulate. Part of the composite primary key and a business-key candidate.
• PROGRAM_VERSION — Version identifier for the selected program, allowing audit against a specific catalog version.
• PROGRAM_CATALOG — Catalog reference under which the program is defined.
• ORG_UNIT_PROG — Owning organizational unit for the program.
• PRG_CAL_TYPE — Calendar type associated with the program (for example, academic versus standard calendar).
• PRG_CI_SEQ_NUM — Calendar instance sequence number tying the program to a specific calendar instance.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard EBS audit columns tracking who created and last modified the record and when.

The surrogate-level primary key is IGS_DA_REQ_WIFPRGS_PK, defined over (BATCH_ID, PROGRAM_CODE). A unique index, IGS_DA_REQ_WIFPRGS_U1, is documented over the identical column pair, confirming that the combination of request identifier and program code is the definitive business-key candidate. No additional surrogate column beyond these two is present; identity is therefore intrinsic to the request-plus-program pairing.

Common Use Cases and Queries

The principal use case is retrieving the What-If programs captured for a given Degree Audit request so that the audit engine can evaluate the student against them. A typical query joins to the parent request header:

• Listing What-If programs for a request: SELECT w.PROGRAM_CODE, w.PROGRAM_VERSION, w.PROGRAM_CATALOG FROM IGS_DA_REQ_WIFPRGS w WHERE w.BATCH_ID = :batch_id;
• Reporting which programs students most frequently simulate, grouping by PROGRAM_CODE and counting distinct BATCH_ID values.
• Validating that no What-If rows exist for Batch-type requests, enforcing the documented restriction that What-If data is allowed only for Single Request types.
• Reconciling What-If program selections against the primary major rows in IGS_DA_REQ_WIFMJRS for the same BATCH_ID.

Related Objects

• IGS_DA_RQST — Parent Degree Audit request header. Join via IGS_DA_REQ_WIFPRGS.BATCH_ID = IGS_DA_RQST.BATCH_ID.
• IGS_DA_REQ_WIFMJRS — What-If major rows for the same request. Join via BATCH_ID and PROGRAM_CODE.
• IGS_DA_REQ_WIFPRGS_PK — Primary key constraint on (BATCH_ID, PROGRAM_CODE).
• IGS_DA_REQ_WIFPRGS_U1 — Unique index reinforcing the business-key candidate.
• Program definition and catalog tables referenced through PROGRAM_CODE, PROGRAM_VERSION, and PROGRAM_CATALOG for descriptive lookups.