Results for “val_meaning”

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

Overview

IGS_PE_USR_AVAL_V is a self-service reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. Its documented description is "Describes the Self Service User Activity Setup Details." In practice, the view exposes the configuration records that govern how enrolment or self-service user activity validations behave for a given person type — whether a validation denies or merely warns, whether it can be overridden, the date on which an override took effect, and any step-level override limits.

The view is defined with a join between the base activity-validation table and the standard lookups view, so that the meaning and step-group type of each validation are resolved at query time rather than being stored redundantly. Because the view filters out closed lookups, it returns only currently active validation configuration, which makes it suitable for direct use in concurrent programs, OAF-based self-service pages, and ad-hoc reporting without additional lookup filtering. The view carries a VALID status in 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two objects: the base table IGS_PE_USR_AVAL (aliased UAV) and IGS_LOOKUPS_VIEW (aliased LKV). Although ETRM documentation lists no referenced base objects, the view text itself is definitive.

• IGS_PE_USR_AVAL — supplies all configuration columns, including the primary key USR_ACT_VAL_ID and ROW_ID, the audit columns, and the override-related attributes.
• IGS_LOOKUPS_VIEW — joined on LKV.LOOKUP_CODE = UAV.VALIDATION, restricted to lookup types 'ENROLMENT_STEP_TYPE_EXT' and 'ENROLMENT_OVR_STEP_TYPE', and excluding records where CLOSED_IND = 'Y'. This join resolves the descriptive meaning and step-group classification of each validation code.

Because one validation code maps to a single active lookup, the join is effectively many-to-one and does not multiply rows for a given configuration record.

Key Columns

• USR_ACT_VAL_ID / ROW_ID — surrogate identifier and row locator for each activity-validation setup record.
• PERSON_TYPE — the person type to which the validation applies.
• VALIDATION — the raw lookup code identifying the validation step.
• VAL_MEANING — the displayed meaning of the validation code, resolved from the lookups view.
• STEP_GROUP_TYPE — classifies the validation step into its group/type.
• DENY_WARN — indicates whether a failed validation denies the activity or only issues a warning.
• OVERRIDE_IND — flag indicating whether the validation may be overridden by an authorised user or process.
• OVERRIDE_DT — the effective override date associated with the record. This is the column users most often search for when investigating when an override became effective or whether an override date has been populated for a given validation and person type.
• STEP_OVERRIDE_LIMIT — the maximum number of overrides permitted at step level.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include reviewing which validations are overridable for a person type, auditing override dates, and verifying whether a validation warns or denies before enabling self-service activity.

SELECT person_type, validation, val_meaning, deny_warn,
       override_ind, override_dt, step_override_limit
FROM   apps.igs_pe_usr_aval_v
ORDER BY person_type, validation;

SELECT person_type, validation, val_meaning, override_dt
FROM   apps.igs_pe_usr_aval_v
WHERE  override_ind = 'Y'
AND    override_dt IS NOT NULL;

SELECT v.validation, v.val_meaning, v.step_group_type,
       v.deny_warn, v.override_dt
FROM   apps.igs_pe_usr_aval_v v
WHERE  v.person_type = :person_type;

These queries are read-only and safe for reporting; maintenance of the underlying configuration should be performed through the Student System setup forms rather than direct DML.