Search Results hr_person_type_usage_api




Overview
Explore in AI Chat

Overview

The APPS.HR_PERSON_TYPE_USAGE_API package is a public PL/SQL API in Oracle E-Business Suite that governs the assignment of person types to people and, where applicable, to person type groups. Person type usage records define which person types (for example, Employee, Applicant, Contingent Worker, or Party) are valid for a given person, and how those usages are sequenced and constrained based on system person type and person type group membership. In Oracle EBS 12.1.1 and 12.2.2 this package functions as the supported interface for creating, updating, validating, and removing person type usage rows, thereby insulating external callers from the underlying tables PER_PERSON_TYPE_USAGES_F, PER_PERSON_TYPES, and PER_ALL_PEOPLE_F.

The package is classified as an API in the ETRM repository, owned by the APPS schema, and its status is VALID. It depends on APPS.HR_API for common error handling, message retrieval, and business-group resolution, and on SYS.STANDARD for base PL/SQL constructs.

Key Procedures and Functions

  • CREATE_PERSON_TYPE_USAGE — Inserts a new person type usage record, associating a person with a permitted person type and, where relevant, a person type group. This is the primary entry point for establishing a usage that did not previously exist.
  • UPDATE_PERSON_TYPE_USAGE — Modifies an existing person type usage record, such as adjusting the primary flag, date-tracked attributes, or the group/type pairing. Validation is normally performed before the row is changed.
  • DELETE_PERSON_TYPE_USAGE — Removes a person type usage record. This is used when a person should no longer be associated with a given person type or group combination.
  • CHECK_PERSON_TYPE — Validation routine that confirms a supplied person type is a permissible, active person type for the person or business group in question, applying the system person type rules maintained in PER_PERSON_TYPES.
  • CHECK_PERSON_EX_TYPE — Validation routine that confirms the combination of person type and person type group (or related extended type attribute) is valid before a usage row is created or updated.

Tables Accessed

  • PER_PERSON_TYPE_USAGES_F — The primary date-tracked table that stores person type usage rows. The API inserts, updates, and logically deletes records here.
  • PER_PERSON_TYPES — Holds the definition of each person type, including system person type and group. The check routines read this table to validate that a requested type is permitted.
  • PER_ALL_PEOPLE_F — The date-tracked person (employee/applicant) record. The API references it to confirm the person exists and to resolve person-level context for usages.

Usage Notes

This package is typically invoked from Oracle HRMS forms (such as the Person and Person Type Usages windows), from concurrent programs that migrate or load person data, and from custom PL/SQL code that must programmatically maintain person type usages. The migration program PER_PTU_DFF_MIG references this package for descriptor-flexfield migration of person type usage data.

As with other HR_API-based packages, callers should supply the standard p_validate, business group, and effective date parameters where the signature requires them, and are expected to commit or roll back the transaction themselves. Because the underlying table is date-tracked, updates and deletes must respect effective date logic; calling the validation procedures first is good practice to surface HR_API errors before performing the DML.