Results for “effective_from”

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

Overview

The view IGSBV_UC_OFFER_CONDITIONS is a base view within the Oracle E-Business Suite IGS – Student System product family, specifically associated with the Universities and Colleges (UC) subsystem. Its documented purpose is to serve as the Base View for Offer Conditions in the generic condition library. In practical terms, it exposes the set of conditions that may be attached to an offer made to an applicant (for example, an academic offer of admission), together with the descriptive text, decision status, and audit information required to administer those conditions.

The view is classified in the ETRM metadata as belonging to an obsolete product context and is explicitly documented as Not implemented in this database in the supplied reference. This disposition matters for reporting and integration design: the object should not be treated as a supported, active interface in Oracle EBS 12.1.1 or 12.2.2 environments. When present, it functions as a read-only reporting surface, since the view definition is created WITH READ ONLY, meaning consumers can query the data but cannot use the view as a DML target.

The view returns one row per offer condition, keyed logically by CONDITION_CATEGORY and CONDITION_NAME, and is intended primarily for inquiry, listing, and integration extraction rather than for transactional maintenance.

Underlying Base Objects

The view is defined over a single documented base table, IGS_UC_OFFER_CONDS (aliased as CO in the view text). No additional base objects are documented. The relationship is a straightforward projection: each row in IGS_UC_OFFER_CONDS is surfaced through IGSBV_UC_OFFER_CONDITIONS with a small amount of derived content.

Two aspects of the derivation are notable:

• The column STATUS is translated into a display value via the lookup mechanism. The view text demonstrates a lookup translation expression tied to IGS_LOOKUP_VALUES using lookup type IGS_UC_COND_STATUS, returning the lookup MEANING as _LA:STATUS_DESC. This follows the standard EBS lookup-description pattern, where coded statuses are rendered as user-facing text.
• The view is materialized conceptually as a read-only query (WITH READ ONLY), reinforcing its role as a reporting object rather than an updateable entity.

Because the metadata records no other referenced base objects, any additional joins or derived logic beyond the lookup translation should be treated as undocumented.

Key Columns

The view exposes the identifying, descriptive, and audit attributes of each offer condition:

• CONDITION_CATEGORY – the classification or grouping of the condition.
• CONDITION_NAME – the name identifying the specific condition.
• EFFECTIVE_FROM / EFFECTIVE_TO – the date range during which the condition is valid.
• STATUS – the coded status of the condition.
• _LA:STATUS_DESC – the descriptive meaning of the status, derived from lookup type IGS_UC_COND_STATUS.
• MARVIN_CODE – an external or legacy reference code associated with the condition.
• SUMMARY_OF_CONDITIONS – the summarized textual description of the condition (the field most directly related to the search term "summary_of_conditions").
• LETTER_TEXT – the letter or correspondence text associated with the condition.
• DECISION – the decision outcome linked to the condition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on listing available offer conditions, retrieving the summary and decision text for a given condition, and extracting data for downstream correspondence or integration. The following query returns the core descriptive attributes:

• SELECT condition_category, condition_name, status, summary_of_conditions, decision FROM igsbv_uc_offer_conditions;
• SELECT condition_name, _LA:STATUS_DESC, effective_from, effective_to FROM igsbv_uc_offer_conditions WHERE status = 'A';
• SELECT condition_category, COUNT(*) FROM igsbv_uc_offer_conditions GROUP BY condition_category;

Because the object is documented as obsolete and not implemented, these queries should be validated against the specific 12.1.1 or 12.2.2 instance before reliance. Where the view is absent, the equivalent data can be sourced directly from IGS_UC_OFFER_CONDS with an appropriate lookup join to IGS_LOOKUP_VALUES.