Results for “choice_no”

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

Overview

IGS_UC_APP_CHO_CNDS is a table within the Oracle E-Business Suite Student System (IGS) product family, classified in the Electronic Technical Reference Manual (ETRM) as belonging to an obsolete module. The table stores non-academic conditions attached to an applicant's university or college choice — for example, requirements such as proof of English proficiency, references, or health declarations that must be satisfied independently of the applicant's academic qualifications. Each row associates one condition with a single applicant choice.

The table is not implemented in the current database instance, meaning the object exists in the documented schema but is absent from the running environment. This is typical of legacy or decommissioned admissions functionality that remains catalogued for reference purposes. In Oracle EBS 12.1.1 and 12.2.2, the IGS product line was largely superseded by Oracle Student Cloud and related higher-education offerings, so the table is retained primarily for historical schema documentation and any residual integration that still references it.

The metadata's heuristic Data Vault classification identifies this object as satellite-leaning. This suggests a modeling interpretation in which the table acts as a descriptive child of a parent business entity — the applicant choice — rather than as an independent hub or a pure associative link. Its foreign key to IGS_UC_APP_CHOICES reinforces that reading: the parent supplies the business context, while this table provides non-key descriptive attributes (condition type, description, satisfaction status) recorded against it.

Key Information Stored

The table carries twelve documented columns. The surrogate primary key is APP_CHOICE_COND_ID, enforced by the constraint IGS_UC_APP_CHO_CNDS_PK and backed by the unique index IGS_UC_APP_CHO_CNDS_U1. A second unique index, IGS_UC_APP_CHO_CNDS_U2, covers the composite of APP_NO, CHOICE_NO, and CONDITION_TYPE, making this triple the documented business-key candidate: it guarantees that any given condition type is recorded only once per applicant choice combination.

• APP_CHOICE_COND_ID — Surrogate primary key uniquely identifying each condition record.
• APP_CHOICE_ID — Foreign key linking the condition back to the parent row in IGS_UC_APP_CHOICES.
• APP_NO — The applicant number, part of the composite business key.
• CHOICE_NO — The choice number within the application, also part of the business key.
• CONDITION_TYPE — The category or code of the non-academic condition; completes the business key.
• CONDITION_DESC — Free-text or descriptive label explaining the condition.
• SATISFIED — Status flag indicating whether the condition has been met.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each record and when.

Common Use Cases and Queries

Typical reporting scenarios include tracking outstanding non-academic conditions for admissions processing, identifying applicants blocked from confirmation by unmet conditions, and auditing condition satisfaction rates by condition type. Because the table is obsolete and unimplemented, such queries are generally historical or migration-oriented.

• Joining to the parent choice to list all conditions for an applicant: SELECT c.APP_NO, c.CHOICE_NO, c.CONDITION_TYPE, c.CONDITION_DESC, c.SATISFIED FROM IGS_UC_APP_CHO_CNDS c WHERE c.APP_NO = :app_no.
• Identifying outstanding conditions: filter on SATISFIED to isolate unresolved requirements per applicant.
• Aggregating by CONDITION_TYPE to measure how frequently each condition type appears or is satisfied.
• Reconciling this satellite against its parent via APP_CHOICE_ID to detect orphaned condition rows.

Related Objects

The documented foreign key relationship anchors this table to the following significant object:

• IGS_UC_APP_CHOICES — Parent table referenced via IGS_UC_APP_CHO_CNDS.APP_CHOICE_ID. Join key: APP_CHOICE_ID.

Beyond the documented FK, related objects in the IGS admissions schema typically include the applicant header and application tables that supply APP_NO, and any views or concurrent programs that report on applicant choice conditions. Where the table is not implemented, dependent objects may also be absent, and migration efforts should confirm availability before relying on these relationships.