Results for “enrolment_ovr_step_type”

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

Overview

IGS_EN_ELGB_OVR_SYS_STEP_V is a reporting view in the Oracle E-Business Suite Student System (formerly Oracle Student System, now part of the Oracle Higher Education product family). It exposes eligibility override step records together with the decoded meaning of the override step type, drawing on the underlying transactional table IGS_EN_ELGB_OVR_STEP and the lookup view IGS_LOOKUPS_VIEW. The view is owned by the APPS schema and is intended for read-only consumption by reporting, integration, and inquiry processes rather than for direct DML.

The view's principal purpose is to present the override step type in business-friendly terminology. Because the raw table IGS_EN_ELGB_OVR_STEP stores only the coded value STEP_OVERRIDE_TYPE, consumers of the view rely on the join to the lookup view to obtain the MEANING and STEP_GROUP_TYPE descriptors associated with the lookup type ENROLMENT_OVR_STEP_TYPE. This is the lookup type the user searched on, and it governs the valid set of values that may appear in the STEP_OVERRIDE_TYPE column.

Underlying Base Objects

The view is defined over two documented base objects:

• IGS_EN_ELGB_OVR_STEP (aliased EOS) — the eligibility override step table, which holds individual step-level override records tied to an eligibility override (ELGB_OVERRIDE_ID). This is the driving table of the view.
• IGS_LOOKUPS_VIEW (aliased LKV) — the standard lookups view that decodes lookup codes into their meanings. The join is made on LKV.LOOKUP_CODE = EOS.STEP_OVERRIDE_TYPE with the lookup type restricted to ENROLMENT_OVR_STEP_TYPE.

The join also filters on LKV.CLOSED_IND = 'N', meaning that only active (non-closed) lookup codes are included. Override step records whose STEP_OVERRIDE_TYPE refers to a closed or invalid lookup value will therefore be excluded from the view's result set. The join is effectively an inner join, so no rows are produced for step types that cannot be resolved through the lookups view.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_EN_ELGB_OVR_STEP row, useful for identifying the exact physical row.
• ELGB_OVR_STEP_ID — the unique identifier of the eligibility override step record.
• ELGB_OVERRIDE_ID — the parent eligibility override to which the step belongs. This is the key for linking the step back to the override header.
• STEP_OVERRIDE_TYPE — the coded override step type. This is the column that joins to the lookup code for lookup type ENROLMENT_OVR_STEP_TYPE.
• MEANING — the decoded, user-facing description of the override step type from IGS_LOOKUPS_VIEW.
• STEP_GROUP_TYPE — the grouping classification of the override step, obtained from the lookups view.
• STEP_OVERRIDE_DT — the date on which the step override takes effect or applies.
• STEP_OVERRIDE_LIMIT — the limit value associated with the step override.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard Oracle EBS who-did-what audit information.

Common Use Cases and Queries

The view is typically used to list the override steps applied to a given eligibility override, showing readable step type descriptions. A representative query is:

• SELECT elgb_override_id, step_override_type, meaning, step_group_type, step_override_dt, step_override_limit FROM apps.igs_en_elgb_ovr_sys_step_v WHERE elgb_override_id = :p_override_id;
• Reporting on the distribution of override step types: SELECT step_override_type, meaning, COUNT(*) FROM apps.igs_en_elgb_ovr_sys_step_v GROUP BY step_override_type, meaning;
• Integration extracts that need the decoded meaning rather than the code, for example exporting override steps to an external eligibility engine.

Because the view is not documented with public base-object mappings beyond the join shown in its definition, consumers should treat it as a read-only convenience layer and avoid assuming referential completeness if lookup codes are later closed.