Search Results igs_pe_per_type_map_pk

Overview

The IGS_PE_PER_TYPE_MAP table is a legacy data structure within the Oracle E-Business Suite (EBS), specifically belonging to the now-obsolete IGS (Student System) product family. Its primary function was to store mapping definitions between Oracle Student System (OSS) person types and Human Resources (HR) person types. This mapping was critical for data integration and synchronization between the student information system and the core HRMS modules, ensuring consistent person classification across different functional areas of the application. The provided ETRM metadata explicitly notes that this table was "Not implemented in this database," indicating it may have been a planned or historical component that was not deployed in standard EBS 12.1.1 or 12.2.2 instances, rendering it primarily of architectural or reference significance.

Key Information Stored

The table's structure centers on a composite primary key that defines the mapping relationship. The two key columns are PERSON_TYPE_CODE and PER_PERSON_TYPE_ID. The PERSON_TYPE_CODE column would typically store the code representing a person type within the OSS context, as defined in the related IGS_PE_PERSON_TYPES table. The PER_PERSON_TYPE_ID column would store the corresponding identifier for a person type within the HRMS module, likely referencing the PER_PERSON_TYPES table (though not listed in the provided foreign keys). Together, these columns create a direct link, or map, between a student-specific classification and an HR-specific classification for the same person entity.

Common Use Cases and Queries

Given its status as obsolete and not implemented, active operational or reporting use cases in a standard EBS environment are unlikely. Historically, its intended use case would have been to support processes requiring a unified view of a person's type across systems. For example, a data conversion or nightly interface job might query this map to correctly assign HR attributes to student records, or vice versa. A typical query to retrieve all defined mappings would leverage its primary key columns:

• SELECT person_type_code, per_person_type_id FROM igs_pe_per_type_map;

To find the HR person type ID for a specific OSS code, a query would be:

• SELECT per_person_type_id FROM igs_pe_per_type_map WHERE person_type_code = '&OSS_PERSON_TYPE';

Related Objects

Based on the documented foreign key relationship, this table has a direct dependency on the IGS_PE_PERSON_TYPES table, which defines the valid OSS person type codes. The foreign key is defined on the IGS_PE_PER_TYPE_MAP.PERSON_TYPE_CODE column, referencing IGS_PE_PERSON_TYPES. This ensures referential integrity, meaning that any PERSON_TYPE_CODE in the map must exist as a valid type in the IGS_PE_PERSON_TYPES table. The absence of a documented foreign key to an HR table (like PER_PERSON_TYPES) for the PER_PERSON_TYPE_ID column in the provided metadata suggests that relationship may have been enforced via application logic or is not captured in this excerpt. The table's primary key constraint is named IGS_PE_PER_TYPE_MAP_PK.