Search Results program_version




Overview
Explore in AI Chat

Overview

The IGS_DA_REQ_WIFPRGS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Global Systems (IGS) module. Its primary function is to store "what-if" program details associated with a student's degree audit request. This table captures the hypothetical academic programs a student is considering for evaluation, allowing advisors to model different academic pathways. As indicated in the documentation, this storage is intended for information only during single, non-batch request types. Notably, the metadata explicitly labels this table as "Obsolete," signaling that its use may be deprecated in favor of newer data models or processes within the application.

Key Information Stored

The table's columns are designed to uniquely identify a request and the specific academic program scenario being evaluated. The primary key is a composite of BATCH_ID and PROGRAM_CODE, enforced by the unique index IGS_DA_REQ_WIFPRGS_U1. Key data elements include:

  • BATCH_ID: A unique numeric identifier linking the record to a specific degree audit request.
  • PROGRAM_CODE & PROGRAM_VERSION: Together, these columns define the precise academic course or program code and its version number being analyzed in the "what-if" scenario, directly addressing the user's search term.
  • PROGRAM_CATALOG: Identifies the catalog year or effective dates governing the program's requirements.
  • ORG_UNIT_PROG: The organizational unit responsible for the program.
  • PRG_CAL_TYPE & PRG_CI_SEQ_NUM: Store the academic calendar type and sequence number attached to the program for correct term-based tracking.
  • Standard WHO Columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for audit trails.

Common Use Cases and Queries

The primary use case is retrieving the "what-if" program selections for a specific degree audit request to support academic advising sessions. A typical query would join this table to a master request table (not specified in the provided dependencies) using BATCH_ID. For reporting, one might aggregate these records to analyze the frequency of certain program codes being explored in hypothetical scenarios. A fundamental query pattern is:

SELECT PROGRAM_CODE, PROGRAM_VERSION, PROGRAM_CATALOG
FROM IGS.IGS_DA_REQ_WIFPRGS
WHERE BATCH_ID = :request_id
ORDER BY PROGRAM_CODE;

Given the "Obsolete" status, common operational use cases likely involve data migration, historical reporting, or supporting legacy interfaces rather than new development.

Related Objects

Based on the provided dependency information, the direct relationships are limited. The table does not reference any other database objects. However, it is referenced by an object within the APPS schema named IGS_DA_REQ_WIFPRGS. This is likely a public synonym (APPS.IGS_DA_REQ_WIFPRGS) that points to the IGS.IGS_DA_REQ_WIFPRGS base table, which is a standard EBS architecture pattern for granting application access. The absence of foreign key metadata suggests joins to parent tables like a degree audit request header would be performed via the BATCH_ID column, though those specific tables are not listed in the excerpt.