Search Results igs_pe_stup_data_emt_all

Overview

The table IGS_PE_STUP_DATA_EMT_ALL is a setup entity within the Oracle E-Business Suite (EBS) Student System (IGS), specifically designed to define and manage data elements associated with person types. Its primary role is to establish a configurable linkage between specific data elements and person type classifications, acting as a foundational setup table for data collection and validation rules within the student information module. As indicated by the ETRM metadata, this table is part of the "IGS - Student System (Obsolete)" product, signifying its functionality is associated with a legacy or superseded architecture within Oracle EBS 12.1.1 and 12.2.2. The "ALL" suffix in the table name is a standard Oracle EBS convention denoting a multi-organization access control (MOAC) enabled table, meaning it can store data partitioned by operating unit.

Key Information Stored

The table's structure centers on the relationship it defines. The primary key, SETUP_DATA_ELEMENT_ID, uniquely identifies each setup rule. The two critical foreign key columns form the core of this relationship: DATA_ELEMENT links to the IGS_PE_DATA_ELEMENT table, identifying the specific piece of information (e.g., a field or attribute), and PERSON_TYPE_CODE links to the IGS_PE_PERSON_TYPES table, specifying the category of person (such as Student, Applicant, or Instructor) for which the data element is relevant. This setup allows administrators to control which data points are required, optional, or applicable for different roles within the student system, enabling tailored data models and forms.

Common Use Cases and Queries

A primary use case is the administrative setup and maintenance of person-based data requirements. For instance, an implementation team would use this table to mandate that "Emergency Contact" (DATA_ELEMENT) is a required field for all "Students" (PERSON_TYPE_CODE) but optional for "Alumni." Common queries involve retrieving the list of data elements configured for a specific person type or validating setup rules. A typical reporting query might join to the related tables for descriptive names:

• SELECT pt.person_type_code, de.data_element_name, sde.* FROM igs_pe_stup_data_emt_all sde, igs_pe_person_types pt, igs_pe_data_element de WHERE sde.data_element = de.data_element_id AND sde.person_type_code = pt.person_type_code AND pt.person_type_code = 'STUDENT';

This setup data is foundational for downstream processes like UI rendering, data validation scripts, and compliance reporting, ensuring data integrity aligns with institutional policies.

Related Objects

This table has defined dependencies within the IGS module, as per the provided foreign key constraints. Its two primary parent tables are IGS_PE_DATA_ELEMENT, which holds the master definition of available data elements, and IGS_PE_PERSON_TYPES, the master list of valid person classifications. The primary key constraint IGS_PE_SETUP_DATA_ELEMENT_PK ensures uniqueness on the SETUP_DATA_ELEMENT_ID column. Given its nature as a setup table, it is likely referenced by various application forms and potentially by validation logic in database packages or triggers within the Student System, though the ETRM notes it is "Not implemented in this database," which may indicate it is part of a delivered data model not activated in all instances.