Results for “abbreviation_code”

9 results




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

Overview

IGSFV_UC_CONDITION_DETAILS is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the IGS (Student System) product family. It presents the full set of condition details that together constitute an offer extended to an applicant within the Universities and Colleges admissions functionality. In Oracle EBS reporting and integration terms, the view provides a denormalized, human-readable projection of the underlying admissions condition data, joining condition detail records to their parent offer conditions and resolving coded values into descriptive text.

The view is defined with a WITH READ ONLY clause, confirming that it is intended strictly for query, reporting, and integration consumption rather than for DML. It is valid in both the 12.1.1 and 12.2.2 releases of the E-Business Suite.

Underlying Base Objects

The view is defined over four base objects within the IGS schema, joined as follows:

The inner joins to IGS_UC_OFFER_CONDS ensure that only condition details with a valid parent offer condition are returned, while the outer joins to the two reference tables tolerate missing abbreviation or subject lookups.

Key Columns

Common Use Cases and Queries

The view is typically used to report on the composition of admissions offers, to drive applicant-facing correspondence, and to feed decision-status reconciliation into downstream systems.

A representative query listing offer conditions with resolved status for a given condition category:

SELECT CONDITION_CATEGORY,
       CONDITION_NAME,
       ABBREVIATION_CODE,
       ABBREVIATION_TEXT,
       SUBJECT_TEXT,
       GRADE_MARK,
       POINTS,
       STATUS,
       _LA:STATUS_DESC,
       DECISION
  FROM APPS.IGSFV_UC_CONDITION_DETAILS
 WHERE CONDITION_CATEGORY = :p_category
 ORDER BY CONDITION_NAME, CONDITION_LINE;

Because the view already resolves abbreviation, subject, and status lookups, it eliminates the need for application-side decoding and is well suited to BI Publisher reports, concurrent-program extracts, and interface staging. As the view is read-only, all maintenance must be performed against the underlying base tables.