Results for “grade_mark”

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

Overview

IGS_UC_COND_DETAILS is a detail table within the Oracle E-Business Suite Student System (IGS) product family. It belongs to the offer library component of the admissions and recruiting schema and stores the individual conditions that together make up an offer extended to an applicant. Where the parent offer condition record defines the category and name of a condition, IGS_UC_COND_DETAILS preserves the granular line-level requirements, academic thresholds, and qualifying subject matter attached to each condition. In the EBS 12.1.1 and 12.2.2 releases the table resides in the IGS schema and is reported as VALID in the data dictionary.

From a dimensional modeling perspective, the FK topology mined from the schema suggests a link classification within a Data Vault heuristic. The table resolves relationships between the reference abbreviation entity and the offer conditions parent, meaning it behaves as an associative construct rather than a pure descriptive satellite. This is a modeling suggestion only; the physical implementation remains a conventional relational detail table.

Key Information Stored

The documented physical schema comprises thirteen columns. The most significant are:

• CONDITION_CATEGORY — classifies the condition and forms part of the composite primary key; also the FK to IGS_UC_OFFER_CONDS.
• CONDITION_NAME — the named condition within a category; the second component of the composite PK and FK.
• CONDITION_LINE — the line identifier that distinguishes individual conditions within the same category and name.
• ABBREVIATION — short code for the condition, foreign-keyed to IGS_UC_REF_OFF_ABRV.
• GRADE_MARK — the grade or mark required to satisfy the condition line.
• POINTS — tariff points associated with the condition.
• SUBJECT — the subject area to which the grade or points requirement applies.
• CONDITION_TEXT — free-text narrative of the condition as presented to the applicant.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

The surrogate primary key is IGS_UC_COND_DETAILS_PK, defined over (CONDITION_CATEGORY, CONDITION_NAME, CONDITION_LINE). A unique index, IGS_UC_COND_DETAILS_U1, is documented over (CONDITION_CATEGORY, CONDITION_LINE, CONDITION_NAME), which acts as the business-key candidate. Note the differing column ordering between PK and unique index; both enforce the same uniqueness semantics.

Common Use Cases and Queries

Typical uses involve offer letter generation, conditional offer tracking, and admissions reporting. A common query joins the detail rows to their parent condition definitions:

• Listing all condition lines for a category: SELECT condition_name, condition_line, grade_mark, points, subject FROM igs_uc_cond_details WHERE condition_category = :cat;
• Resolving the abbreviation description: join ABBREVIATION to IGS_UC_REF_OFF_ABRV to obtain the human-readable label.
• Offer composition reports that aggregate GRADE_MARK and POINTS per applicant offer.
• Data extracts feeding prospect and applicant tracking dashboards, filtered on CREATION_DATE or LAST_UPDATE_DATE for incremental loads.
• Audit reconciliation comparing CONDITION_TEXT against approved offer wording.

Related Objects

• IGS_UC_OFFER_CONDS — parent table; joined on CONDITION_CATEGORY and CONDITION_NAME.
• IGS_UC_REF_OFF_ABRV — reference table for condition abbreviations; joined on ABBREVIATION.
• IGS_UC_COND_DETAILS_PK / IGS_UC_COND_DETAILS_U1 — primary and unique index enforcing identity.
• Offer library parent objects in the IGS admissions schema that reference the condition category set.
• Student System admissions views and concurrent programs that read the offer library for applicant communications.