Search Results program_ref_code

Overview

The IGS_DA_OUT_PRG_REF table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2, specifically for the Institutional Global Systems (IGS) modules. Its primary role is to store outgoing program reference information for students selected in a given batch request. This table acts as a staging or output area, capturing reference codes associated with a student's requested or officially declared academic program, which are then typically used for reporting or integration with third-party systems. It is critical to note that the provided ETRM documentation explicitly marks this table as "Obsolete," indicating it may be part of a legacy process or subject to deprecation in future releases. The table resides in the APPS_TS_INTERFACE tablespace, further underscoring its function as an interface or output staging table.

Key Information Stored

The table's structure is designed to uniquely identify a student's program reference within a specific batch. The mandatory columns form a composite primary key and define the core business data. The BATCH_ID links all records to a parent data request. PERSON_ID uniquely identifies the student. PROGRAM_SEQ_NUM provides a sequence to link a primary program to associated majors, minors, or tracks. The PROGRAM_REF_CODE_TYPE is a user-defined classification for the reference code, while PROGRAM_REF_CODE holds the actual meaningful code for users or external software. Standard Oracle EBS "Who" columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are present for auditing. The unique index IGS_DA_OUT_PRG_REF_U1 enforces data integrity on the primary key columns.

Common Use Cases and Queries

The primary use case for this table is extracting student program reference data for a completed batch process, often for external reporting or system feeds. A common query would retrieve all reference codes for students within a specific batch. For example, to audit all program references generated by a request, one might execute:

SELECT PERSON_ID, PROGRAM_REF_CODE_TYPE, PROGRAM_REF_CODE
FROM IGS.IGS_DA_OUT_PRG_REF
WHERE BATCH_ID = :p_batch_id
ORDER BY PERSON_ID, PROGRAM_SEQ_NUM;

Another typical pattern involves joining to person or program tables (though not directly referenced in the provided metadata) to enrich the output with descriptive names. Given the table's obsolete status, development of new interfaces or reports should avoid direct dependencies on this table, and existing integrations should be reviewed for modernization.

Related Objects

Based on the provided relationship data, this table has defined dependencies within the IGS schema. Its primary key is named IGS_DA_OUT_PRG_REF_PK. Crucially, it references another table via a foreign key relationship: the BATCH_ID column is a foreign key to the IGS_DA_OUT_PRG table. This establishes that IGS_DA_OUT_PRG_REF is a child table, storing detailed reference codes for the broader program output records housed in IGS_DA_OUT_PRG. The dependency information also confirms that an APPS synonym named IGS_DA_OUT_PRG_REF exists, which is the standard method for granting access to the underlying IGS table from the APPS schema within Oracle EBS.