Search Results unit_set_code_description

Overview

The view IGS_RC_I_P_UNITSETS_V belongs to the IGS – Student System product family within Oracle E-Business Suite, and is classified in the ETRM metadata as Obsolete for releases 12.1.1 and 12.2.2. Its purpose is to expose a restricted projection of interest-code and unit-set data drawn from the Oracle Student System (OSO) public view AS_INTEREST_CODES_VL. The documentation states explicitly that the view "will be based on OSO public view AS_INTEREST_CODES_VL" and that only those attributes required by the OSS (Oracle Student System) integration layer are surfaced. As a result, the view functions as an integration and reporting façade rather than a primary data source, presenting a narrow, denormalized slice of admissions interest-code and unit-set configuration for downstream consumption.

The ETRM metadata records the view as Not implemented in this database, meaning that although the definition is documented, the object is not physically deployed in the reference environment. This is consistent with its Obsolete classification.

Underlying Base Objects

The documented view text establishes two referenced base objects:

• AS_INTEREST_CODES_VL — the OSO public view supplying the primary columns. It is aliased as IPU in the defining SQL and provides interest-code identifiers, codes, descriptions, audit columns, and the MASTER_ENABLED_FLAG.
• IGS_RC_I_ENT_STATS — aliased as RES, joined to obtain the interest type identifier and the inquiry entry status identifier.

The metadata lists "Referenced base objects: none documented," but the embedded view text authoritatively identifies the two objects above. The join condition is an equi-join on interest type:

IPU.INTEREST_TYPE_ID = RES.INTEREST_TYPE_ID

An additional filter restricts the result set to rows where IPU.PARENT_INTEREST_CODE_ID IS NOT NULL, ensuring only child-level interest codes (that is, unit sets associated with a parent program code) are returned. Because AS_INTEREST_CODES_VL is a "VL" (view with translation) object, description values may be language-dependent.

Key Columns

• ROW_ID — the ROWID of the underlying AS_INTEREST_CODES_VL row, exposed for row-level addressing.
• INQ_PROG_UNIT_SET_ID — the interest code identifier (mapped from INTEREST_CODE_ID); identifies the inquiry program unit set.
• INQ_PROG_CODE_ID — the parent interest code identifier (from PARENT_INTEREST_CODE_ID), linking the unit set to its program code.
• INTEREST_TYPE_ID — the interest type, also used as the join key to IGS_RC_I_ENT_STATS.
• INQ_ENTRY_STAT_ID — the inquiry entry status, sourced from IGS_RC_I_ENT_STATS.
• INQ_UNIT_SET_CODE — the interest/unit-set code (from CODE).
• UNIT_SET_CODE_DESCRIPTION — the descriptive text (from DESCRIPTION).
• MASTER_ENABLED_FLAG — the enabled/disabled indicator passed through from the base view; the column matched by the user’s search term.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage involves validating that only enabled unit sets are presented to downstream admissions or integration processes. A representative query filtering on the searched column is:

SELECT INQ_UNIT_SET_CODE, UNIT_SET_CODE_DESCRIPTION, INQ_PROG_CODE_ID, MASTER_ENABLED_FLAG FROM IGS_RC_I_P_UNITSETS_V WHERE MASTER_ENABLED_FLAG = 'Y';

Because the object is Obsolete and not deployed, such SQL should be validated against the environment before reliance, and integration code should be reviewed for a supported replacement view.