Search Results delete_person_type_usage




Overview
Explore in AI Chat

Overview

APPS.HR_PERSON_TYPE_USAGE_API is a PL/SQL package body belonging to the Oracle E-Business Suite Human Resources (HR) product family. It exposes the application programming interface that governs the assignment of person types to people within the PER schema. In Oracle HRMS, a person type classifies an individual in relation to the enterprise — for example as an employee, an applicant, a contingent worker, or a contact — and a person may legitimately hold more than one such classification at the same time. The PER_PERSON_TYPE_USAGES_F entity records each of these individual associations, and this package is the supported programmatic gateway for creating, maintaining, validating and removing them.

Because it is registered in ETRM with an API classification, the package is intended to be called rather than bypassed. It encapsulates the business rules, row-level validation and datetrack semantics that must be honoured for person type usage data to remain internally consistent, allowing both Oracle's own forms and customer extensions to manipulate the data safely.

Key Procedures and Functions

Five documented entry points are exposed by the package:

  • CREATE_PERSON_TYPE_USAGE — Inserts a new association between a person and a person type. It is the primary entry point for attaching an additional classification to an existing person record.
  • UPDATE_PERSON_TYPE_USAGE — Modifies an existing person type usage row. The documented signature shows a rich parameter set covering the surrogate identifier, effective date, datetrack mode, object version number for optimistic locking, and the full range of descriptive flexfield attribute columns (attribute_category plus attribute1 through attribute21).
  • DELETE_PERSON_TYPE_USAGE — Removes a person type usage record, subject to the same datetrack and version-number discipline as the update routine.
  • CHECK_PERSON_TYPE — A validation routine that verifies whether a given person type may be applied in the current context before any write is attempted.
  • CHECK_PERSON_EX_TYPE — The validation routine most directly associated with the search term. It confirms whether a specific person already holds, or is permitted to hold, a particular person type usage, and is typically invoked ahead of create or update operations to prevent duplication or invalid combinations.

Tables Accessed

The package operates against three documented tables, all reached through APPS synonyms:

  • PER_PERSON_TYPE_USAGES_F — The datetrack-enabled intersection table that physically stores each person-to-person-type association. This is the principal insert, update and delete target.
  • PER_PERSON_TYPES — The definition table for person types. It is read to confirm that the requested type exists, is active, and is valid for the business group.
  • PER_ALL_PEOPLE_F — The datetrack-enabled person record. It is referenced to confirm that the subject person exists and is effective on the supplied effective date, and to support lookups such as CHECK_PERSON_EX_TYPE.

Usage Notes

HR_PERSON_TYPE_USAGE_API is normally invoked indirectly. The Person Type Usages window and other Oracle HRMS forms call the package to maintain classifications, and it is referenced by at least one other package within the applications schema, which delegates its person-type-usage maintenance to this API rather than writing to the tables directly.

Custom code should follow the same pattern. Pass p_validate as true to perform a validation-only run that rolls back all changes, and set it to false for the committing execution. Supply p_effective_date and p_datetrack_mode to control how the change is applied across the datetrack timeline, and always carry p_object_version_number in and out to preserve optimistic locking. The defaults of hr_api.g_number and hr_api.g_varchar2 indicate that unspecified parameters are treated as "no change" rather than nulled, which is important when updating only a subset of attributes or flexfield segments. Call CHECK_PERSON_TYPE and CHECK_PERSON_EX_TYPE before the write procedures to surface validation errors to the user in a controlled manner.