Results for “sys_il0000327366c00014”

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

Overview

The table IGS.IGS_DA_REQ_STDNTS is a transactional data object within the Oracle E-Business Suite IGS (Student Systems / Higher Education) schema. Its documented purpose is to store the students for whom a Degree Audit request has been raised, whether that request originates from an individual inquiry or from a batch run. Each row represents a single student within a specific degree audit request batch, capturing the enrollment, program, and what-if context used by the degree audit engine when generating output.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting a standard transactional OLTP configuration. In the Oracle EBS 12.1.1 and 12.2.2 releases, this table belongs to the degree audit (DA) request pipeline that feeds third-party degree audit processing and returns reports for storage and display.

Based on the mined foreign-key topology, the table is classified heuristically as hub-leaning. From a Data Vault modeling perspective, it behaves like a hub surrounded by link and satellite dependencies: the surrogate key IGS_DA_REQ_STDNTS_ID anchors the row, while the many IGS_DA_OUT_* and IGS_DA_IN_* tables reference BATCH_ID, suggesting this object sits at the center of a fan-out of inbound and outbound result satellites. This classification is a modeling suggestion only; the physical design is a conventional normalized transactional table.

Key Information Stored

The documented schema contains twenty columns. The most operationally significant are summarized below:

• IGS_DA_REQ_STDNTS_ID — Numeric (15) surrogate primary key, sequence-generated, enforced by the unique index IGS_DA_REQ_STDNTS_PK. This is the definitive row identifier.
• BATCH_ID — Numeric (15) identifier linking the student record to a degree audit request batch. It is indexed by IGS_DA_REQ_STDNTS_N2 (composite with PERSON_ID) and is referenced by more than fifteen downstream result tables.
• PERSON_ID — Numeric (15) foreign key to the person. For batch requests, the relative ordering of PERSON_ID values reflects the sort option selected (values 1–5) during batch student criteria selection. Indexed by IGS_DA_REQ_STDNTS_N1.
• MAJOR_UNIT_SET_CD — VARCHAR2 (10) holding the major unit set code, the specific attribute most commonly searched by administrators resolving degree audit results.
• PROGRAM_CODE and WIF_PROGRAM_CODE — Enrolled program code and what-if program code respectively; the latter participates in a foreign key to IGS_PS_COURSE.
• SPECIAL_PROGRAM_CODE — VARCHAR2 (30) for special program context, also with a foreign key to IGS_PS_COURSE.
• PROGRAM_MAJOR_CODE — VARCHAR2 (30) combining program and major codes for convenience.
• WIF_ID — Numeric (15) identifier for the what-if program and unit set detail combination.
• REPORT_TEXT — CLOB holding the returned degree audit report text from the third-party engine; a LOB index (SYS_IL0000327366C00014$$) supports this column.
• ERROR_CODE — VARCHAR2 (30) capturing failures per student request.
• PERSON_NUMBER, LAST_NAME, FIRST_NAME, ALT_PERSON_NUMBER — Denormalized person identifiers now marked obsoleted in the documentation; retained for backward compatibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO audit columns.

The sole documented business-key candidate beyond the surrogate is the primary key index itself; no alternate unique constraint is recorded apart from the LOB index, which is structural rather than business-meaningful.

Common Use Cases and Queries

Typical usage centers on retrieving the student roster for a batch, filtering by program or major unit set, and joining to result tables. A representative query for locating students within a major unit set is:

SELECT s.IGS_DA_REQ_STDNTS_ID, s.PERSON_ID, s.MAJOR_UNIT_SET_CD,
       s.PROGRAM_CODE, s.PROGRAM_MAJOR_CODE
FROM   IGS.IGS_DA_REQ_STDNTS s
WHERE  s.BATCH_ID = :batch_id
AND    s.MAJOR_UNIT_SET_CD = :major_unit_set_cd;

Because BATCH_ID and PERSON_ID are indexed, batch-scoped and person-scoped lookups perform efficiently. Reporting use cases include reconciliation of requested versus processed students, error triage using ERROR_CODE, retrieval of stored report text from REPORT_TEXT for archival or display, and auditing which programs and what-if scenarios were submitted in a given batch.

Related Objects

The table participates in a dense set of relationships:

• IGS_DA_RQST and IGS_DA_REQ_WIF — parent request tables joined via BATCH_ID.
• IGS_PS_COURSE — referenced by WIF_PROGRAM_CODE and SPECIAL_PROGRAM_CODE.
• IGS_DA_OUT_PRG, IGS_DA_OUT_STDT_DEG, IGS_DA_OUT_STDNT, IGS_DA_OUT_SPCL_REQ, IGS_DA_OUT_UNT_AS, IGS_DA_OUT_UNT_EN, IGS_DA_OUT_TSTS, IGS_DA_OUT_UNIT_AH, IGS_DA_OUT_USR_DEF — outbound result tables referencing BATCH_ID.
• IGS_DA_IN_PRG, IGS_DA_IN_RSLT_UNTS, IGS_DA_IN_SRC_UNTS, IGS_DA_IN_USR_DEF — inbound processed data tables linked by BATCH_ID.
• IGS_DA_REQ_RPTS — reports table joined via BATCH_ID.

These relationships confirm the table's central role as the student-level anchor for the degree audit batch pipeline.