Results for “regenerate_position_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.HR_POSITION_API is the supported PL/SQL application programming interface for creating, maintaining, and deleting position records in Oracle E-Business Suite Human Resources. It is the single point of entry through which both Oracle-delivered and customer-written code should manipulate the HR_ALL_POSITIONS_F and PER_ALL_POSITIONS entities. By encapsulating the business rules that govern positions — validation of the position definition, grade and job relationships, name generation, security profile access, and the writing of the multiple underlying tables — the package ensures that data entered programmatically conforms to the same rules enforced by the Professional User Interface forms. In EBS 12.1.1 and 12.2.2 the package is installed in the APPS schema and reports a VALID status, with the package specification and body both present. It participates in the standard HR API framework, sharing the common HR_API and HR_UTILITY dependencies and honouring the date-tracked, multi-lingual, and security models used throughout the HR product family.

Key Procedures and Functions

• CREATE_POSITION — Creates a new position record, validating the supplied definition, generating the position name, and inserting the corresponding rows into the position tables.
• UPDATE_POSITION — Modifies an existing position, applying the same validation and date-track logic as the create path and inserting a new effective-dated row where required.
• DELETE_POSITION — Removes or end-dates a position, subject to the standard referential and security checks performed by the API.
• LCK — Performs the locking operation used to serialize concurrent activity against a position record during maintenance.
• REGENERATE_POSITION_NAME — Rebuilds the display name of a single position from the current definition and language settings.
• REGENERATE_POSITION_NAMES — Performs the same name regeneration in bulk across multiple positions.

The documented interface exposes ten procedures and functions in total. The remaining documented members follow the same validation and name-generation pattern applied during position maintenance.

Tables Accessed

The package reads and writes HR_ALL_POSITIONS_F through its PER_ALL_POSITIONS synonym, the core date-tracked position entity. It uses PER_POSITION_DEFINITIONS to resolve the position definition and naming rules, PER_JOBS and PER_VALID_GRADES for job and grade validation, and PER_SHARED_TYPES for shared type lookups. PER_SECURITY_PROFILES supports security profile enforcement, FND_ID_FLEX_SEGMENTS supplies key flexfield segment information, and FND_LANGUAGES supports multi-lingual name generation. PER_MM_POSITIONS and PQH_POSITION_TRANSACTIONS are touched for mass-position and transactional position-change processing, while DUAL is used for singleton lookups. HR_SECURITY and HR_UTILITY provide the underlying security and utility routines invoked during these operations.

Usage Notes

HR_POSITION_API is normally invoked from the Professional User Interface position forms through the HR_POSITION_SWI and related switches, from HRMS Data Pump routines such as HRDPP_CREATE_POSITION, HRDPP_UPDATE_POSITION, and HRDPP_DELETE_POSITION, and from mass-move and refresh processes including HR_MASS_MOVE_API and PER_REFRESH_POSITION. It is also invoked from the GHR-position and SF52 regulatory interfaces. The package is referenced by thirteen other packages in total. Custom and third-party code should call the supported procedures rather than writing directly to the position tables, because the API handles effective dating, name generation, security, and cleanup of dependent rows. The REGENERATE_POSITION_NAME and REGENERATE_POSITION_NAMES routines are typically used in corrective or data-fix scripts where position names must be rebuilt after definition changes.