Search Results per_person_type_id

Overview

The IGS.IGS_PE_PER_TYPE_MAP table is a critical integration object within Oracle E-Business Suite, specifically for implementations utilizing Oracle Student System (OSS) alongside Oracle Human Resources Management System (HRMS). Its primary role is to maintain the mapping definitions between user-defined person types in the Student System and the corresponding system-defined person types in Oracle HRMS. This mapping ensures seamless data flow and process integration between the two modules, allowing OSS to correctly identify and process individuals based on their HRMS person type classifications. The table is owned by the IGS (iGrants) schema and is a standard, valid table in both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table stores a straightforward mapping relationship with three core columns. The PERSON_TYPE_CODE holds the user-defined person type identifier from the Oracle Student System. The SYSTEM_TYPE column contains the system person type from OSS that is mapped to the user-defined type. The most significant column for integration is PER_PERSON_TYPE_ID, which stores the unique identifier (NUMBER(15)) for the corresponding Person Type as defined within Oracle HRMS tables. This ID is the foreign key link to the HRMS person type definitions. The table also includes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing. Data integrity for the mapping is enforced by the unique index IGS_PE_PER_TYPE_MAP_U1 on the combination of PERSON_TYPE_CODE and PER_PERSON_TYPE_ID.

Common Use Cases and Queries

The primary use case involves integration processes where OSS needs to retrieve or validate the HRMS person type for an individual. This is essential for enrollment, financial aid, and other student-centric processes that depend on HR classifications like 'Employee', 'Applicant', or 'Contact'. A common reporting requirement is to list all established mappings for validation or setup purposes. The fundamental query, as indicated in the ETRM, is:

SELECT PERSON_TYPE_CODE,
       SYSTEM_TYPE,
       PER_PERSON_TYPE_ID
FROM IGS.IGS_PE_PER_TYPE_MAP;

In practice, this table is often joined to HRMS person type tables (like PER_PERSON_TYPES) to get descriptive information. For instance, to resolve a specific OSS person type to its HRMS name, a developer might use:

SELECT m.PERSON_TYPE_CODE,
       m.SYSTEM_TYPE,
       m.PER_PERSON_TYPE_ID,
       p.user_person_type
FROM IGS.IGS_PE_PER_TYPE_MAP m,
     PER_PERSON_TYPES p
WHERE m.PER_PERSON_TYPE_ID = p.person_type_id;

Related Objects

While the provided dependency information states this table does not reference other objects, it is referenced by the APPS synonym IGS_PE_PER_TYPE_MAP, which allows other application modules to access it. Its most important relationship is a logical foreign key to the HRMS table PER_PERSON_TYPES via the PER_PERSON_TYPE_ID column. This table is central to the integration setup and is therefore referenced by various OSS application components and possibly custom interfaces that synchronize person data between the two systems. The unique index IGS_PE_PER_TYPE_MAP_U1 is its primary related database object.