Search Results per_person_type_usages_upgrade

Overview

The table PER_PERSON_TYPE_USAGES_UPGRADE is a specialized technical object within the Oracle E-Business Suite (EBS) Human Resources (HR) module. Its primary function is to facilitate the upgrade of the person type usage model during a system upgrade or patch application. This table is not part of the standard transactional data model used by the application in its day-to-day operation. Instead, it serves as a staging or mapping table that assists in the data migration and transformation of person type assignments when moving from an older data model to a newer one, specifically between releases such as 12.1.1 and 12.2.2. The ETRM metadata explicitly notes it is "Not implemented in this database," indicating it is typically empty or non-existent in a production environment post-upgrade and is used only during the upgrade process itself.

Key Information Stored

The table's structure is designed to map and upgrade relationships between persons and their assigned person types. Based on the provided metadata, the core columns are foreign keys linking to the master person type table, PER_PERSON_TYPES. The primary key column is PERSON_TYPE_ID. The other critical columns are APP_PERSON_TYPE_ID and EMP_PERSON_TYPE_ID. These columns likely store identifiers for specific categories of person types—such as Applicant (APP) and Employee (EMP)—that require special handling during the upgrade. The table's purpose is to hold the mapping logic or transitional data that defines how legacy person type usages are converted to the usage model in the upgraded system.

Common Use Cases and Queries

Direct interaction with this table by developers or DBAs is rare outside the upgrade context. Its use cases are almost exclusively tied to upgrade scripts run by the Oracle-provided upgrade utilities. Administrators might query it during an upgrade to verify mapping rules or troubleshoot data conversion issues. A sample diagnostic query, to be run in a pre-upgrade or mid-upgrade environment, would be:

• SELECT person_type_id, app_person_type_id, emp_person_type_id FROM per_person_type_usages_upgrade WHERE person_type_id = <ID>;

This would reveal the mapped target person type IDs for a given source type. Reporting against this table in a live production system is not a standard practice, as it should contain no data post-upgrade.

Related Objects

As indicated by the foreign keys, this upgrade table has a direct and exclusive relationship with the PER_PERSON_TYPES table, which is the master repository for all person type definitions (e.g., Employee, Applicant, Contingent Worker). The upgrade process likely involves the PER_PERSON_TYPE_USAGES table, which is the permanent transactional table storing which person types are assigned to each person (party_id). The PER_PERSON_TYPE_USAGES_UPGRADE table acts as the bridge between the old and new state of this data. It is also intrinsically linked to the Oracle HRMS upgrade scripts and the AD (Applications DBA) upgrade utilities that manage the overall EBS upgrade path.