Search Results igs_pe_usr_aval_all

Overview

The table IGS_PE_USR_AVAL_ALL is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS). Its primary role is to manage the configuration for enrollment validations performed through the self-service user interface. Specifically, it defines which validation rules are applicable to different types of students (person types) within a multi-organization (multi-org) environment. This setup table acts as a control mechanism, enabling administrators to tailor the enrollment validation experience. It is important to note that the metadata explicitly categorizes the IGS Student System as "Obsolete," indicating this table is part of a legacy module that may be deprecated or replaced in modern implementations of Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to link validation activities with user classifications and organizational context. The primary identifier is the USR_ACT_VAL_ID column. The table's unique key constraint (IGS_PE_USR_AVAL_ALL_UK1) highlights the most critical business columns: PERSON_TYPE, which classifies the student (e.g., undergraduate, graduate); VALIDATION, which specifies the rule or activity to be performed; and ORG_ID, which ties the configuration to a specific operating unit, enforcing the multi-org architecture standard in Oracle EBS. This combination ensures that validation rules can be uniquely defined per person type and organization.

Common Use Cases and Queries

A primary use case involves querying the active validation setup for a specific student type during the enrollment process. For instance, a self-service page or a concurrent program might query this table to determine which validations to execute. A typical reporting query would join to the person types table for descriptions.

• Sample Query for Configuration Review:
  SELECT aval.person_type, pt.description person_type_desc, aval.validation, aval.org_id
  FROM igs_pe_usr_aval_all aval,
  igs_pe_person_types pt
  WHERE aval.person_type = pt.person_type
  AND aval.org_id = :p_org_id
  ORDER BY aval.person_type, aval.validation;
• Validation Check Logic: Application code would likely use a query based on the UK1 columns to check if a specific validation is active for a given person type and operating unit before proceeding with the validation logic.

Related Objects

The table has defined relationships with other key entities in the Student System. Its primary foreign key relationship is with the IGS_PE_PERSON_TYPES table, via the PERSON_TYPE column, ensuring that only defined person types can be used in the validation setup. As a table with an ALL suffix and an ORG_ID column, it follows the standard Oracle EBS multi-org design pattern. Consequently, it is almost certainly associated with a corresponding security view (likely named IGS_PE_USR_AVAL) that filters records based on the user's current MO: Security Profile, making it the safe object for application queries. The existence of a primary key (IGS_PE_USR_AVAL_ALL_PK) and a unique key (IGS_PE_USR_AVAL_ALL_UK1) also implies potential dependencies from other application tables or program units that enforce referential integrity.