Search Results choice_no




Overview
Explore in AI Chat

Overview

The IGS_UC_OLD_OUSTAT table is a historical audit table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle Student Management) product family. Its primary role is to archive previous admission outcome statuses for applications processed through the Universities and Colleges Admissions Service (UCAS) interface. This table serves as a critical data retention object, preserving a record of an applicant's choice status before it was updated to a new outcome. This historical tracking is essential for audit trails, compliance, and troubleshooting within the student admissions lifecycle. The object is designated for internal Oracle application use, and direct data manipulation outside of standard EBS programs is unsupported.

Key Information Stored

The table's structure is designed to capture the core elements of a past admission decision for a specific UCAS application choice. The combination of APP_NO (UCAS application number) and CHOICE_NO (UCAS application choice number) forms a unique identifier for each historical record, as enforced by the IGS_UC_OLD_OUSTAT_U1 index. The central audit data includes the OLD_OUTCOME_STATUS, which holds the previous admission status code, and the DECISION_DATE when that status was applied. The table also captures contextual decision metadata via foreign key columns DECISION_REASON_ID and DECISION_MAKE_ID, which likely reference lookup tables for decision reasons and administrative personnel. Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide a full audit of the record's creation and maintenance within the system.

Common Use Cases and Queries

The primary use case is auditing the history of an applicant's choices. For instance, support or administrative personnel may query this table to understand the sequence of status changes for a specific application and choice, which is vital for resolving applicant inquiries or system issues. A typical query would join the historical data with current application information to present a complete timeline. Given the user's search for "choice_no," a common reporting pattern would involve filtering or grouping by this column to analyze status history across multiple choices.

Sample Query: Retrieve full audit history for a specific application choice:
SELECT APP_NO, CHOICE_NO, OLD_OUTCOME_STATUS, DECISION_DATE
FROM IGS.IGS_UC_OLD_OUSTAT
WHERE APP_NO = <application_number>
AND CHOICE_NO = <choice_number>
ORDER BY DECISION_DATE DESC;

Sample Query: Identify all choices where a particular old status was recorded:
SELECT APP_NO, CHOICE_NO, DECISION_DATE, CREATION_DATE
FROM IGS.IGS_UC_OLD_OUSTAT
WHERE OLD_OUTCOME_STATUS = '<status_code>';

Related Objects

Based on the provided dependency information, the IGS_UC_OLD_OUSTAT table is a standalone entity that does not reference other database objects. However, it is referenced by an object within the APPS schema named IGS_UC_OLD_OUSTAT. This APPS schema object is likely a public synonym or a view that provides a controlled access point to the underlying IGS table for use within the standard EBS application code. The DECISION_REASON_ID and DECISION_MAKE_ID columns imply logical relationships to decision reason and decision maker lookup tables, respectively, though these are not listed as formal dependencies in the provided metadata.