Search Results per_pl_location

Overview

PER_PL_LOCATION is a PL/SQL package in the APPS schema of Oracle E-Business Suite, classified as an "OTHER" API in the ETRM 12.2.2 metadata. Its name follows the PER (Human Resources) product prefix combined with the PL (Payroll) location convention, and it operates on the HR_LOCATION entity — the core repository of physical work locations used by HRMS, Payroll, and related applications. The package encapsulates the business rules for validating, inserting, and maintaining location records that would otherwise be handled directly against the HR_LOCATION and HR_LOCATIONS_ALL tables.

The package is recorded with VALID status and references the SYS.STANDARD package (the PL/SQL SQL standard library), indicating it is a compiled, production-ready unit. It is referenced by two other packages, HR_LOCATION_BK1 and HR_LOCATION_BK2, which are the standard Oracle Forms "block" program units generated for the HR_LOCATION form. This dependency pattern shows the package is called from the Location form's validation and post-query logic, and it also self-references, confirming internal recursion or shared utility calls. Because it is a location maintenance API, it is the programmatic gateway used whenever a location is created or changed through the EBS HRMS user interface.

Key Procedures and Functions

Three procedures are documented for this package:

• CHECK_PL_LOCATION — A validation routine. It confirms whether a location record is valid and complete before insert or update processing proceeds. This is the logic invoked when a user commits a Location form and EBS must confirm mandatory and business-rule validation succeeds.
• CREATE_PL_LOCATION — The insert routine. It writes a new location row, applying the package's defaulting logic (for example, standard address or location-code derivation) and returning the generated primary key for downstream use.
• UPDATE_PL_LOCATION — The modification routine. It applies changes to an existing location record, preserving data integrity for dependent entities such as assignments, payrolls, and organization units.

All three share the PER_PL_LOCATION prefix, confirming they belong to a single coherent API surface for the location entity.

Tables Accessed

The metadata extracts tables referenced via APPS synonyms but does not enumerate them individually. In practice, the package operates against the HR_LOCATION tables — HR_LOCATIONS_ALL and its date-tracked and translation-related siblings — reading existing rows during validation and writing on create and update. No DML is executed against SYS.STANDARD; that dependency is purely a compile-time reference to the SQL standard library. Because it is a location-maintenance API, any table writes are confined to the HR location schema and do not cross into payroll or financials tables directly.

Usage Notes

Typical invocation is from the HR_LOCATION_BK1 and HR_LOCATION_BK2 form blocks — the standard Oracle Forms PL/SQL units invoked on WHEN-VALIDATE-RECORD and related triggers. The package is also callable from custom concurrent programs, interfaces, or other PL/SQL units that need to create or amend locations without going through the form. Because it is a form-level, internal API (classified OTHER rather than PUBLIC), the supported approach is to call the documented HZ or HRMS public APIs and let the form block units call this package internally. Direct calls should be limited to custom code that must replicate exact form behavior, and should account for the date-tracked nature of location records, site and business-group security, and the fact that creating a location via this package does not automatically synchronize downstream objects.