Results for “igs_ad_unit_ou_stat”

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

Overview

IGS_AD_UNIT_OU_STAT is a reference (lookup) table within the Oracle E-Business Suite Student System module, product code IGS. It stores user-defined admission unit outcome statuses and maps each one to a corresponding system-level admission outcome status. In practice, this table acts as the configuration bridge between institution-specific terminology and the seeded statuses that drive admissions processing logic. The table is documented in ETRM 12.1.1 as owned by the IGS schema with 10 columns, and it is flagged as not implemented in the reference database and is part of the obsolete Student System footprint in 12.1.1 and 12.2.2. Its primary key is IGS_AD_UNIT_OU_STAT_PK, defined on the ADM_UNIT_OUTCOME_STATUS column, and a unique index IGS_AD_UNIT_OU_STAT_U1 covers the same column, confirming it as the business key. Based on the foreign-key structure (a single, stable key column consumed by a downstream transactional table), the metadata's heuristic classification suggests modeling this object as a hub-leaning entity in a Data Vault context, since it functions as a durable reference source rather than a transactional or link record.

Key Information Stored

The table is narrow and reference-oriented. The most significant columns documented in the ETRM metadata are:

• ADM_UNIT_OUTCOME_STATUS — the primary key column and business-key candidate (also covered by unique index IGS_AD_UNIT_OU_STAT_U1). Holds the user-defined admission unit outcome status code.
• DESCRIPTION — the descriptive text shown to users for the user-defined status.
• S_ADM_OUTCOME_STATUS — the system admission outcome status to which the user-defined status maps. This column embodies the core purpose of the table: translating institutional codes into system-recognized values.
• SYSTEM_DEFAULT_IND — indicates whether the row is the system default status for its context.
• CLOSED_IND — flag denoting whether the status is treated as closed for admissions processing purposes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns used for audit and concurrency tracking.

The primary key is a single-column surrogate on ADM_UNIT_OUTCOME_STATUS, which doubles as the business key; there is no separate numeric sequence-generated identifier documented. Consumers must reference this code column rather than any hidden row identifier.

Common Use Cases and Queries

The principal use case is resolving user-defined admission unit outcome statuses into their system equivalents for reporting and downstream processing. A join to the referencing application instance table demonstrates the mapping:

• Listing all defined statuses with their system mappings: SELECT ADM_UNIT_OUTCOME_STATUS, DESCRIPTION, S_ADM_OUTCOME_STATUS FROM IGS_AD_UNIT_OU_STAT.
• Identifying defaults or inactive entries: filter on SYSTEM_DEFAULT_IND = 'Y' or CLOSED_IND = 'Y' to drive validation and defaulting rules in admission processing.
• Resolving an applicant's unit outcome to a system status: SELECT a.ADM_UNIT_OUTCOME_STATUS, a.S_ADM_OUTCOME_STATUS FROM IGS_AD_PS_APLINSTUNT_ALL a, IGS_AD_UNIT_OU_STAT s WHERE a.ADM_UNIT_OUTCOME_STATUS = s.ADM_UNIT_OUTCOME_STATUS.

Because the table is not implemented in the reference database and belongs to the obsolete Student System, queries should be validated against the institution's actual deployment before being relied upon in reporting.

Related Objects

The documented foreign-key relationship identifies the primary dependent object:

• IGS_AD_PS_APLINSTUNT_ALL — references this table through the ADM_UNIT_OUTCOME_STATUS column, making it the main consumer of the status mapping.

Additional IGS admissions tables that store admission unit outcomes (such as application and admission-decision structures within the IGS_AD_PS series) may reference the same code by convention, though only IGS_AD_PS_APLINSTUNT_ALL is documented in the ETRM metadata. The table's dependencies are therefore shallow: it is a referenced parent, not a referencing child, which reinforces its hub-like modeling role.