Results for “primary_program”

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

Overview

IGS_DA_OUT_PRG is a table in the IGS (Student System) product family of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. It stores the outgoing program information for the declared and requested program data associated with a student in a Degree Audit Request. In the degree audit process, a student's academic record is evaluated against the requirements of a declared or requested program of study; IGS_DA_OUT_PRG holds the outbound snapshot of that program context so the audit engine and downstream consumers can resolve the program the student is pursuing, its catalog version, expected completion, and standing at the time of the request.

The ETRM metadata explicitly records that this object is "Not implemented in this database." In an Oracle EBS 12.1.1 / 12.2.2 environment, the presence of this note indicates the table belongs to an obsolete or unlicensed Student System component and is not physically created in the target instance. Any reference to IGS_DA_OUT_PRG should therefore be treated as documentation-only unless the IGS product is separately installed and the table has been instantiated.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table carries a stable composite business key and is referenced by several dependent tables, which is consistent with a hub entity that other satellites and link structures would attach to. This classification is offered as a modeling heuristic rather than a statement of the physical design.

Key Information Stored

The primary key is IGS_DA_OUT_PRG_PK, defined over BATCH_ID, PERSON_ID, and PROG_SEQ_NUM. A unique index, IGS_DA_OUT_PRG_U1, covers the same three columns, making this combination the business-key candidate and the natural join path to related objects. The documented physical schema contains 54 columns; the most significant are:

• BATCH_ID, PERSON_ID, PROG_SEQ_NUM — composite identity of the outgoing program record; PERSON_ID identifies the student and PROG_SEQ_NUM distinguishes multiple program rows within a batch.
• PRM_REQUEST_TYPE — the request type governing the degree audit transaction.
• PROGRAM_CODE, PROGRAM_VER_NUM, PROGRAM_CATALOG, PROGRAM_TITLE — the program being audited and the catalog version against which requirements are evaluated.
• ORG_UNIT_PROG, LOCATION, ATTENDANCE_MODE, ATTENDANCE_TYPE — the owning academic organization unit and attendance attributes of the program.
• PRIMARY_PROGRAM, PROGRAM_ATTMPT_STATUS — flags indicating whether this is the student's primary program and its attempt status.
• NOMIN_COMPL_YEAR, NOMIN_COMPL_PERIOD, DERIVED_COMPL_YEAR, DERIVED_COMPL_PERIOD, ANTIC_PROG_COMPL_DATE — nominated, derived, and anticipated completion timing.
• REQMTS_COMPLETE, REQMTS_COMPL_DATE, REQMTS_COMPL_SOURCE — the requirement-completion outcome and its provenance.
• CUMULATIVE_GPA, CLASS_STANDING — academic performance and standing captured for the audit.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard EBS descriptive-flexfield block for client-specific extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical reporting resolves the outgoing program for each student in a degree audit batch and joins to the request header and the detail tables. A representative pattern retrieves program and completion information for a batch:

SELECT o.BATCH_ID, o.PERSON_ID, o.PROG_SEQ_NUM, o.PROGRAM_CODE, o.PROGRAM_VER_NUM, o.PROGRAM_CATALOG, o.PRIMARY_PROGRAM, o.REQMTS_COMPLETE, o.CUMULATIVE_GPA, o.CLASS_STANDING FROM IGS_DA_OUT_PRG o WHERE o.BATCH_ID = :batch_id AND o.PERSON_ID = :person_id ORDER BY o.PROG_SEQ_NUM;

Because IGS_DA_OUT_PRG.BATCH_ID references IGS_DA_REQ_STDNTS, batch-level reporting joins the two to associate outgoing programs with the requesting students. Join the child tables on BATCH_ID, PERSON_ID, and PROG_SEQ_NUM to obtain categorized program data (IGS_DA_OUT_PRG_CGRY), reference values (IGS_DA_OUT_PRG_REF), and attribute usage sets (IGS_DA_OUT_PRG_USET). Common scenarios include producing degree audit worksheets, verifying requirement-completion status prior to graduation clearance, and reconciling nominated versus derived completion terms. Organizations that have extended the table should also filter or project the ATTRIBUTE1–ATTRIBUTE20 columns.

Related Objects

The following objects are documented as directly related to IGS_DA_OUT_PRG through its foreign-key structure:

• IGS_DA_REQ_STDNTS — parent request-student table; IGS_DA_OUT_PRG.BATCH_ID references it. Provides the batch and student context for each outgoing program.
• IGS_DA_OUT_PRG_CGRY — categorized program detail; joins on BATCH_ID, PERSON_ID, and PROG_SEQ_NUM (documented as PROGRAM_SEQ_NUM in the metadata).
• IGS_DA_OUT_PRG_REF — program reference details; joins on BATCH_ID, PERSON_ID, and PROG_SEQ_NUM.
• IGS_DA_OUT_PRG_USET — attribute usage sets for the outgoing program; joins on BATCH_ID, PERSON_ID, and PROG_SEQ_NUM.
• IGS_DA_OUT_PRG_PK — the primary key constraint enforcing uniqueness over BATCH_ID, PERSON_ID, and PROG_SEQ_NUM.
• IGS_DA_OUT_PRG_U1 — the unique index supporting the same business-key columns.

Because the ETRM record states the table is not implemented, these relationships should be validated against the actual instance before they are relied upon in custom code or reports.