Search Results get_emp_person_type_id




Overview
Explore in AI Chat

Overview

APPS.HR_PERSON_TYPE_USAGE_INFO is an Oracle E-Business Suite PL/SQL package that centralizes the logic governing person type usage — the rules that determine which person types (Employee, Applicant, Contingent Worker, or user-defined types) are available in a given business group, how a "user person type" is constructed from its component system person types, and which form-level actions are permitted for a person. In Oracle EBS 12.1.1 and 12.2.2, person type usage drives security, self-service eligibility, and the list of allowable actions (such as Hire, Terminate, Transfer, or Promote) exposed through the People and Assignment forms. The package is declared AUTHID CURRENT_USER and is classified under the ETRM API classification of OTHER. It is a heavily reused utility: ETRM records that it is referenced by 79 other packages, making it one of the more pervasive HRMS infrastructure units. The header identifies the schema revision as hrptuinf.pkh 120.0.12010000.2, dated 2009, and defines a g_actions_r record type pairing a restriction code with its restriction value meaning, plus a g_actions_t associative array keyed by BINARY_INTEGER for storing a list of available actions for a particular person.

Key Procedures and Functions

ETRM documents 16 procedures and functions. Note that the signature of each is not reproduced here; purposes are as documented.

  • GET_USER_PERSON_TYPE_SEPARATOR — Returns the single-character delimiter (initialized to '.') used to concatenate the distinct components of a user person type.
  • GET_DEFAULT_PERSON_TYPE_ID — Overloaded two ways: one form accepts a person type identifier, the other accepts a business group plus system person type, each returning the applicable default person type ID.
  • GET_USER_PERSON_TYPE — Derives the concatenated user person type string.
  • GET_WORKER_USER_PERSON_TYPE — Returns the user person type applicable to worker records.
  • GET_WORKER_NUMBER — Resolves the worker number for a person.
  • GET_APL_USER_PERSON_TYPE — Returns the user person type for the applicant context.
  • GET_EMP_PERSON_TYPE_ID / GET_EMP_USER_PERSON_TYPE — Return the employee person type ID and the employee user person type respectively.
  • GETSYSTEMPERSONTYPE — Returns the underlying system person type.
  • ISNONCOREHRPERSONTYPE — Indicates whether a person type falls outside core HR.
  • FUTSYSPERTYPECHGEXISTS — Detects whether a future-dated system person type change exists.
  • IS_PERSON_OF_TYPE — Tests whether a person belongs to a specified person type.
  • IS_PERSON_A_WORKER — Tests whether a person qualifies as a worker.
  • GET_PERSON_ACTIONS — The function most commonly referenced by applications and the target of the search term get_person_actions; it assembles the list of actions available for a person, populating the g_actions_t table type as restriction code / restriction value pairs.

Tables Accessed

The package reads and, where applicable, writes the following through APPS synonyms. PER_ALL_PEOPLE_F supplies current person records; PER_PERSON_TYPE_USAGES_F holds the dated usage rows that determine a person's active types; PER_PERSON_TYPES and PER_PERSON_TYPES_TL provide system person type definitions and their translated names; PER_FORM_FUNCTIONS and PAY_RESTRICTION_VALUES supply the restriction codes and meanings that populate g_actions_r for GET_PERSON_ACTIONS; PER_PERIODS_OF_PLACEMENT and PER_PERIODS_OF_SERVICE establish worker status and placement context; and PLITBLM is used for list-handling utilities.

Usage Notes

Typical invocation is from the People, Assignment, and applicant forms, from concurrent programs performing person type validation, and from custom PL/SQL that must replicate EBS person type and action derivation. Because it is AUTHID CURRENT_USER, execute grants and synonym resolution must be verified when calling from non-APPS schemas. Developers should call the documented APIs rather than querying the underlying tables directly, since the substring concatenation and defaulting rules are centralized here. When a future-dated system person type change is pending, FUNCTIONS such as FUTSYSPERTYPECHGEXISTS and IS_PERSON_OF_TYPE should be consulted before caching action lists.