Results for “summary_of_conditions”

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

Overview

IGSBV_UC_CONDITION_DETAILS is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It is delivered as part of the Oracle Student System admissions and offers functionality, where it serves as the base view for condition details that make up an offer extended to an applicant. The view exposes the individual academic conditions — subject requirements, grade marks, points, and conditional text — attached to an offer of admission, along with the overall status, summary, and decision recorded at the offer-condition level.

The object is classified as a base view, meaning it is intended as a foundation layer for further reporting, downstream views, or integration extracts rather than as an end-user inquiry screen. Because it is defined WITH READ ONLY, no DML operations are permitted through the view; all maintenance of condition data must be performed against the underlying base tables. In a 12.1.1 or 12.2.2 environment the view remains valid and is queried during offer generation, applicant self-service display of conditions, and institutional reporting on conditional offers.

Underlying Base Objects

The view joins two documented base tables in the IGS schema:

• IGS_UC_COND_DETAILS (aliased CO) — the condition detail table, supplying the condition category, condition name, condition line, abbreviation, grade mark, points, subject, and condition text.
• IGS_UC_OFFER_CONDS (aliased FT1) — the offer-level conditions table, supplying the status, Marvin code, summary of conditions, and decision attributes.

The join predicate matches on both CONDITION_CATEGORY and CONDITION_NAME, meaning a detail row is returned only where a corresponding offer-condition record exists for the same category and condition name. This composite key drives the one-to-many relationship between an offer condition and its constituent detail lines.

Key Columns

• CONDITION_CATEGORY — the user's search term; classifies the condition (for example, academic versus non-academic groupings) and forms one half of the join key.
• CONDITION_NAME — the named condition within the category; the second half of the join key.
• CONDITION_LINE — the individual detail line number within the condition.
• ABBREVIATION_CODE — short code for the condition, mapped from CO.ABBREVIATION.
• GRADE_MARK, POINTS, SUBJECT_CODE — the academic requirement values: required grade, tariff points, and subject.
• CONDITION_TEXT — free-text description of the condition.
• STATUS and _LA:STATUS_DESC — the condition status code from FT1.STATUS, plus a descriptive flexfield-style lookup attribute resolving the meaning from the IGS_LOOKUP_VALUES lookup type IGS_UC_COND_STATUS.
• MARVIN_CODE, SUMMARY_OF_CONDITIONS, DECISION — offer-condition attributes carried through for completeness.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include listing all conditions against an offer, reporting conditional offers by status, and feeding external UCAS-style extracts. The following query filters by the searched attribute:

SELECT condition_category,
       condition_name,
       condition_line,
       subject_code,
       grade_mark,
       points,
       condition_text,
       status,
       "_LA:STATUS_DESC"
FROM   apps.igsbv_uc_condition_details
WHERE  condition_category = :p_category
ORDER BY condition_name, condition_line;

To review conditions by decision status, join to the lookup meaning via the exposed descriptive column, or aggregate points against subjects:

SELECT condition_category, subject_code, SUM(points) total_points
FROM   apps.igsbv_uc_condition_details
WHERE  decision = 'C'
GROUP BY condition_category, subject_code;

Because the view is read-only and joins only two base tables, it performs efficiently for reporting and is safe for integration extracts and concurrent program output.