Search Results igs_en_spi_rconds




Overview
Explore in AI Chat

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

Overview

IGS_EN_SPI_RCONDS is a transactional table within the IGS (Student System) product family of Oracle E-Business Suite, holding Student Program Intermission Return Conditions. In functional terms, the table records the conditions that must be satisfied by a student who returns from an intermission (a formal leave of absence or interruption) on a specific program of study. Each row binds a person, a course or program, an intermission start date, a logical delete marker, and a return condition code into a single association, together with lifecycle attributes such as approval status and audit columns. The object carries a status of VALID and resides in the IGS schema, and it is documented in ETRM for both the 12.1.1 and 12.2.2 releases.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is modeled as a link: it resolves several independent business keys — the student program intermission and the return condition definition — into a single relationship record, rather than storing descriptive attributes of a single parent entity. This is a modeling suggestion only; the physical implementation remains a standard Oracle EBS relational table.

Key Information Stored

The documented physical schema contains thirteen columns. The most significant are the following:

The surrogate primary key is IGS_EN_SPI_RCONDS_PK, which is a composite unique index over PERSON_ID, COURSE_CD, START_DT, LOGICAL_DELETE_DATE, and RETURN_CONDITION. Because the key is composite and derived from business attributes rather than a system-generated identifier, those five columns effectively function as the business-key candidate for uniqueness. The inclusion of LOGICAL_DELETE_DATE in the unique index is notable: it permits a student to have an active and a logically deleted condition for the same person, course, start date, and condition code without violating the constraint.

Common Use Cases and Queries

The table is typically queried to determine which conditions a returning student must fulfil, and whether those conditions have been approved. A typical lookup for a single student joins the intermission header and the condition definition:

  • Listing active conditions for a person: SELECT r.return_condition, r.status_code, r.approved_dt FROM igs_en_spi_rconds r WHERE r.person_id = :p_person AND r.logical_delete_date IS NULL AND r.status_code = 'ACTIVE'.
  • Reporting all students with outstanding, unapproved conditions by program and start date for registrar follow-up.
  • Resolving condition descriptions by joining RETURN_CONDITION to IGS_EN_INTM_RCONDS to translate codes into user-facing text.
  • Auditing changes over time by deliberately including rows where LOGICAL_DELETE_DATE is populated.

Reporting extracts commonly filter on STATUS_CODE and APPROVED_DT for compliance reporting, while operational forms rely on the who-columns for change tracking. Because LOGICAL_DELETE_DATE participates in the primary key, queries that ignore it may return historical rows, so it should be constrained explicitly in most operational retrievals.

Related Objects

The most significant related objects are those named in the documented foreign keys:

  • IGS_EN_STDNT_PS_INTM — the student program intermission header; joined on PERSON_ID, COURSE_CD, START_DT, and LOGICAL_DELETE_DATE.
  • IGS_EN_INTM_RCONDS — the return condition definition (code lookup); joined on RETURN_CONDITION.
  • IGS_EN_SPI_RCONDS_PK — the composite primary key/unique index that enforces the business-key uniqueness described above.

Additional related objects include the student and person entities reached through PERSON_ID, the course catalog reached through COURSE_CD, and the standard Oracle Applications audit infrastructure referenced by CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.