Results for “program_seq_num”

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

Overview

The IGS_DA_OUT_PRG_CGRY table belongs to the IGS (Student System) product family in Oracle E-Business Suite, a module that Oracle has designated as obsolete in current 12.1.1 and 12.2.2 environments. Its narrow business purpose is to hold the outgoing program categories associated with the programs identified for the students who were selected when a Degree Audit or related IGS data-extraction request was executed. In effect, it is a staging or outbound results table populated by a batch process, retaining the category classifications that accompany each student-to-program pairing produced by that run.

The ETRM metadata classifies this object, as a heuristic Data Vault modeling suggestion, as satellite-leaning. That classification is consistent with its shape: the table does not introduce a new business entity of its own but carries descriptive, context-dependent attributes attached to a parent program row. Its grain is defined by the combination of batch, person, program sequence, and category, making it an attribute-bearing child of the batch/program structure rather than an independent hub or an associative link between two distinct entities.

Key Information Stored

The documented physical schema contains nine columns. The following are the most significant for understanding and querying the table:

• BATCH_ID — Identifier of the request or batch run that produced the outgoing rows. This is the leading component of the primary key and the column that ties every record back to the parent batch.
• PERSON_ID — The student for whom the program and category were captured. It forms the second component of the primary key.
• PROGRAM_SEQ_NUM — The sequence number that distinguishes among multiple programs found for the same student within a batch. This is the column most frequently targeted by the search term “program_seq_num,” and it is the third component of the primary key and of the unique index.
• PROGRAM_CATEGORY — The outgoing program category value itself, the descriptive payload of the row and the final component of the primary key.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns recording insert and update audit information.

The surrogate primary key is defined by IGS_DA_OUT_PRG_CGRY_PK over (BATCH_ID, PERSON_ID, PROGRAM_SEQ_NUM, PROGRAM_CATEGORY). A separate unique index, IGS_DA_OUT_PRG_CGRY_U1, covers exactly the same four columns, confirming that this combination is also the business-key candidate and that no row may duplicate a category for a given batch, student, and program sequence.

Common Use Cases and Queries

Because this is a batch-output table, typical access patterns center on reconstructing the results of a specific run or auditing the categories applied to a student’s programs. A common query retrieves all categories for one batch and student:

• SELECT program_seq_num, program_category FROM igs_da_out_prg_cgry WHERE batch_id = :batch_id AND person_id = :person_id ORDER BY program_seq_num;
• Joining to the parent table on the full foreign-key set (BATCH_ID, PERSON_ID, PROGRAM_SEQ_NUM) to return program detail alongside its categories.
• Aggregating categories per batch for reconciliation, for example counting distinct PROGRAM_CATEGORY values by BATCH_ID to verify that an extraction produced the expected distribution.
• Auditing WHO columns to determine when a given batch output was last refreshed, using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Reporting use cases include validating downstream extracts, comparing category assignments across successive batches for the same student, and troubleshooting missing or duplicate program categories following a Degree Audit request.

Related Objects

The FK metadata documents a single parent relationship, but it is the most important one for any join:

• IGS_DA_OUT_PRG — The parent table, referenced through the composite foreign key on (BATCH_ID, PERSON_ID, PROGRAM_SEQ_NUM). It holds the outgoing program rows to which these categories belong and must be joined using all three columns.
• IGS_DA_OUT_PRG_CGRY_PK / IGS_DA_OUT_PRG_CGRY_U1 — The primary-key constraint and unique index that enforce uniqueness of the batch, person, program sequence, and category combination and support indexed lookups on those columns.
• Other IGS Degree Audit outbound staging tables populated by the same batch process, which share the BATCH_ID and PERSON_ID conventions and are commonly queried alongside this table for a complete picture of a request run.

Because the module is marked obsolete, implementers should confirm whether the table is actually instantiated in a given database; the ETRM metadata notes that it is not implemented in the reference database, and the presence or absence of data will determine whether any of the queries above return results in a specific 12.1.1 or 12.2.2 instance.