Results for “igs_da_out_spcl_req”

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

Overview

IGS_DA_OUT_SPCL_REQ is a table in the IGS (Student System) product schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the outgoing Special Requirements identified for a student in the context of a Degree Audit Request. In the Oracle Student System, a degree audit evaluates a student's academic record against program and graduation requirements; where a student is found to have an outstanding or condition-specific requirement, that finding is persisted in this table so it can be communicated or reported to the student and to administrative staff. The table therefore acts as the persistence layer for the "special requirement" element of the outgoing degree audit result set.

Mined from its foreign key structure, the object carries a heuristic Data Vault classification of satellite-leaning. Treated as a modeling suggestion, this indicates that the table primarily holds descriptive, context-dependent attributes that hang off a parent business key (the degree audit request/student combination) rather than defining a new hub or resolving a many-to-many link. Practically, this means the table is best understood as an extension of the degree audit request record, not as an independent entity.

Key Information Stored

The documented physical schema for 12.1.1 comprises twelve columns. The most significant for functional and integration work are:

• BATCH_ID — identifier of the degree audit request batch under which the special requirement was produced; part of the primary key and of the foreign key to IGS_DA_REQ_STDNTS.
• PERSON_ID — the student (party) for whom the outgoing special requirement was found; part of the primary key and of the foreign key to IGS_DA_REQ_STDNTS.
• SPEC_REQ_SEQ_NUM — sequence number that distinguishes multiple special requirements recorded for the same student within the same batch; completes the primary key.
• SPECIAL_REQUIREMENT — the special requirement itself (the finding or code communicated to the student in the outgoing audit).
• TERM_PERIOD — the academic term/period to which the special requirement applies.
• SPECIAL_REQ_EXPIRE_DATE — the date on which the special requirement lapses, if applicable.
• SPECIAL_REQ_REF — a reference value pointing to the source or definition of the requirement.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording who created and last modified each row and when.

The surrogate primary key is IGS_DA_OUT_SPCL_REQ_PK, defined over the composite of BATCH_ID, PERSON_ID, and SPEC_REQ_SEQ_NUM. The business-key candidates are effectively BATCH_ID plus PERSON_ID plus SPEC_REQ_SEQ_NUM in combination; no separate single-column unique index is documented. Because SPEC_REQ_SEQ_NUM participates in the key, a student may have many special requirement rows per batch.

Common Use Cases and Queries

Typical usage centres on retrieving the outgoing special requirements for a degree audit run and presenting them in student-facing or advisor-facing reports. A common query pattern joins the table back to its parent by batch and student:

• List all special requirements for a student in a given batch: SELECT special_requirement, term_period, special_req_expire_date FROM igs_da_out_spcl_req WHERE batch_id = :batch AND person_id = :person ORDER BY spec_req_seq_num;
• Identify requirements nearing expiry for follow-up communications: filter on special_req_expire_date between the current date and a horizon date.
• Reconcile outgoing requirements against the audit request roster by joining BATCH_ID and PERSON_ID to IGS_DA_REQ_STDNTS.
• Audit-trail reporting using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to track when requirements were generated or amended.

Because the table stores output (outgoing) data, it is generally read-oriented in reporting and integration extracts, with inserts driven by the degree audit processing that populates the request results.

Related Objects

The dominant relationship is to the degree audit request student roster, which supplies the parent business key:

• IGS_DA_REQ_STDNTS — joined on IGS_DA_OUT_SPCL_REQ.BATCH_ID = IGS_DA_REQ_STDNTS.BATCH_ID and IGS_DA_OUT_SPCL_REQ.PERSON_ID = IGS_DA_REQ_STDNTS.PERSON_ID; the documented foreign key target for this table.
• IGS_DA_REQ_STDNTS_PK — the primary key constraint on the parent roster that enforces the referential integrity of the above relationship.
• IGS_DA_OUT_SPCL_REQ_PK — the primary key constraint on this table (BATCH_ID, PERSON_ID, SPEC_REQ_SEQ_NUM).

Adjacent degree audit objects in the IGS schema, such as the request header, batch definition, and other outgoing result tables, are commonly referenced alongside this table in audit reporting, though the ETRM metadata documents only the IGS_DA_REQ_STDNTS relationship explicitly. Any integration or extract that reads outgoing degree audit data should treat IGS_DA_REQ_STDNTS as the mandatory driving parent for this satellite-style table.