Results for “waitlist_status_code”

3 results




Overview
Explore in AI Chat

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

Overview

IGS_AD_DFLT_OUDTLS is a transactional configuration table in the Oracle E-Business Suite Student System (IGS) product family. Its documented description, "Default Outcome Decision Details," identifies its purpose: it stores the default values that the admissions engine applies when an admission outcome decision is recorded against an applicant. Rather than capturing an individual decision event for a single person, the table holds reusable defaults keyed by admissions outcome status, so that recruiters and admissions officers can drive consistent decision behavior across an institution's admission cycles.

The object resides in the IGS schema and is classified as VALID in the ETRM repository for both 12.1.1 and 12.2.2. The documented physical schema contains 31 columns. A heuristic Data Vault classification derived from the foreign key structure suggests this object behaves as a link: it sits between reference entities (outcome status, decision reasons, calendar instances, code classes, and trading community parties) and carries descriptive attributes of its own, notably dates, flags, and conditional-offer text. Modelers building a warehouse around admissions data should treat it as a link-satellite hybrid anchored on ADM_OUTCOME_STATUS.

Key Information Stored

The most significant columns fall into three groups. The first is identity and ownership: ADM_OUTCOME_STATUS is the primary business key, naming the outcome status the defaults apply to, and CREATED_BY is the second component of the documented unique index. Together they form the business-key candidate IGS_AD_DEF_OTCM_DEC_PK, which is distinct from the surrogate primary key constraint IGS_AD_DFLT_OUTDTLS_PK documented against the same columns.

The second group holds decision defaults. DFLT_DECISIONDATE_FLAG and DFLT_OFFERDATE_FLAG are boolean controls that tell the system whether to stamp DECISION_DATE and OFFER_DATE automatically. RECONSIDER_FLAG marks whether a reconsidered decision is permitted. DECISION_MAKER_ID and ADM_OTCM_STATUS_AUTH_PERSON_ID both reference HZ_PARTIES, identifying the default decision maker and the default authorising person respectively. DECISION_REASON_ID and PENDING_REASON_ID point to IGS_AD_CODE_CLASSES for standard reason codes, while ADM_OUTCOME_STATUS_REASON and ADM_OUTCOME_STATUS_AUTH_DATE carry the free-text reason and authorisation timestamp.

The third group covers progression and conditional offers: FUTURE_ACAD_CAL_TYPE with FUTURE_ACAD_CI_SEQUENCE_NUMBER and FUTURE_ADM_CAL_TYPE with FUTURE_ADM_CI_SEQUENCE_NUMBER reference IGS_CA_INST_ALL to default future academic and admissions calendar instances. UCAS_COND_CATEGORY and UCAS_COND_NAME join to IGS_UC_OFFER_CONDS, while ADM_CNDTNL_OFFER_STATUS links to IGS_AD_CNDNL_OFRSTAT. CNDTNL_OFFER_SATISFIED_DATE, CNDNL_OFFER_MST_BE_STSFD_FLAG, and CNDTNL_OFFER_CNDTN_TXT support conditional offer satisfaction and text. WAITLIST_STATUS_CODE, WAITLIST_RANK, PRPSD_COMMENCEMENT_DATE and OFFER_RESPONSE_DATE complete the operational payload. Standard audit columns — CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — are present.

Common Use Cases and Queries

The primary use case is verifying which defaults will be applied for a given outcome status before decisions are mass-processed. A typical query joins the status reference table to display the configured defaults:

  • SELECT d.ADM_OUTCOME_STATUS, d.DECISION_MAKER_ID, d.DECISION_REASON_ID, d.DFLT_DECISIONDATE_FLAG, d.OFFER_DATE FROM IGS.IGS_AD_DFLT_OUDTLS d WHERE d.ADM_OUTCOME_STATUS = :status;
  • SELECT d.ADM_OUTCOME_STATUS, s.DESCRIPTION, d.RECONSIDER_FLAG, d.ADM_CNDTNL_OFFER_STATUS FROM IGS.IGS_AD_DFLT_OUDTLS d, IGS.IGS_AD_OU_STAT s WHERE d.ADM_OUTCOME_STATUS = s.ADM_OUTCOME_STATUS ORDER BY d.ADM_OUTCOME_STATUS;
  • SELECT d.ADM_OUTCOME_STATUS, p.PARTY_NAME FROM IGS.IGS_AD_DFLT_OUDTLS d, HZ.HZ_PARTIES p WHERE d.DECISION_MAKER_ID = p.PARTY_ID;

Reporting scenarios include auditing who acts as default decision maker per status, identifying statuses where offer dates are auto-stamped, and reconciling conditional offer default text against UCAS offer condition templates. Because the table is small and configuration-oriented, it is commonly extracted in full for comparison across environments during implementations and upgrades.

Related Objects

The following objects are the most significant direct relationships documented through foreign keys:

  • IGS_AD_OU_STAT — joined on IGS_AD_DFLT_OUDTLS.ADM_OUTCOME_STATUS; supplies the outcome status description.
  • HZ_PARTIES — joined twice, on DECISION_MAKER_ID and ADM_OTCM_STATUS_AUTH_PERSON_ID, for person names.
  • IGS_CA_INST_ALL — joined on FUTURE_ACAD_CAL_TYPE/FUTURE_ACAD_CI_SEQUENCE_NUMBER and FUTURE_ADM_CAL_TYPE/FUTURE_ADM_CI_SEQUENCE_NUMBER.
  • IGS_AD_CODE_CLASSES — joined on DECISION_REASON_ID and PENDING_REASON_ID for standard reason codes.
  • IGS_UC_OFFER_CONDS — joined on UCAS_COND_CATEGORY and UCAS_COND_NAME for UCAS condition templates.
  • IGS_AD_CNDNL_OFRSTAT — joined on ADM_CNDTNL_OFFER_STATUS for conditional offer status values.

These relationships confirm the table's role as a central default-definition link within the IGS admissions model, and any integrated query or custom report touching admission outcome defaults should preserve these join paths.