Search Results setup_data_element_id




Overview
Explore in AI Chat

Overview

The IGS_PE_STUP_DATA_EMT_ALL table is a core setup and configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle's former Higher Education product) module. It functions as a master repository for defining and managing data elements associated with different person types in the system. Its primary role is to establish business rules that dictate which data elements are required or mandatory for specific classifications of persons, such as students, instructors, or alumni. The table supports multi-organization architecture, as indicated by the ORG_ID column, allowing for distinct setups across different operating units. This configuration is fundamental for enforcing data integrity and completeness during person-related transactions and processes.

Key Information Stored

The table stores the relationships between person types, their associated data elements, and the governing rules for those elements. The most critical columns include:

  • SETUP_DATA_ELEMENT_ID: The primary key, serving as a unique system-generated identifier for each configuration record.
  • PERSON_TYPE_CODE: A foreign key referencing the code (e.g., 'STUDENT', 'FACULTY') that categorizes the person.
  • DATA_ELEMENT: A foreign key referencing the name of the specific data attribute or field being configured.
  • VALUE: Defines a specific permissible value for the associated DATA_ELEMENT, allowing for value-specific rules.
  • REQUIRED_IND: A flag (typically 'Y' or 'N') that indicates whether a value for the DATA_ELEMENT is mandatory for the given PERSON_TYPE_CODE.
  • ORG_ID: The operating unit identifier, enabling the table to store different configuration rules for different business units within a single installation.

Common Use Cases and Queries

This table is primarily accessed for configuration validation, data quality reporting, and setup audits. A common operational use case is to determine all mandatory data elements for a specific person type during data entry or import processes. For reporting, administrators often query the table to audit setup rules across operating units. The following sample SQL patterns illustrate these use cases:

  • Retrieve all mandatory data elements for the 'STUDENT' person type: 
    SELECT DATA_ELEMENT, VALUE FROM IGS_PE_STUP_DATA_EMT_ALL WHERE PERSON_TYPE_CODE = 'STUDENT' AND REQUIRED_IND = 'Y';
  • Audit setup differences between operating units (e.g., ORG_ID 101 and 102): 
    SELECT PERSON_TYPE_CODE, DATA_ELEMENT, VALUE, REQUIRED_IND, ORG_ID FROM IGS_PE_STUP_DATA_EMT_ALL WHERE ORG_ID IN (101,102) ORDER BY ORG_ID, PERSON_TYPE_CODE;
  • Standard query to extract the full setup, as provided in the ETRM: 
    SELECT SETUP_DATA_ELEMENT_ID, PERSON_TYPE_CODE, DATA_ELEMENT, VALUE, REQUIRED_IND, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ORG_ID FROM IGS.IGS_PE_STUP_DATA_EMT_ALL;

Related Objects

The table maintains defined relationships with other key setup tables in the IGS module, ensuring referential integrity for person types and data elements. Based on the provided relationship data:

  • Primary Key: The table is uniquely identified by the constraint IGS_PE_SETUP_DATA_ELEMENT_PK on the column SETUP_DATA_ELEMENT_ID.
  • Foreign Key References (This table references):
    • IGS_PE_PERSON_TYPES: Via the PERSON_TYPE_CODE column. This validates that the configured person type is defined in the master person types table.
    • IGS_PE_DATA_ELEMENT: Via the DATA_ELEMENT column. This ensures the configured data element name exists in the master data elements table.
  • Referenced By: The ETRM indicates the table is referenced by an APPS synonym named IGS_PE_STUP_DATA_EMT_ALL, which is the standard access point for EBS application code.