Search Results derive_hr_loc_address
Overview
HR_AE_UTILITY is a legislation-specific PL/SQL utility package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It encapsulates formatting and derivation logic required by the United Arab Emirates (UAE) localization of Oracle Human Resources (AE denoting the AE legislation). Rather than allowing the core HRMS forms and concurrent processes to hard-code UAE-specific name formats and address derivation rules, the localization routes those operations through this single utility. This design isolates region-specific business rules from the base product and permits the UAE legislation to evolve independently between EBS releases. The package is classified as OTHER in the ETRM 12.2.2 registry, confirming it is an internal helper library rather than a public, versioned API such as those exposed under HR_*_API naming. The header comment indicates a source version of 120.0.12020000.2 dated July 2012, aligning the file with the 12.2 code line.
Key Procedures and Functions
Two callable units are registered under this package in the ETRM metadata:
- PER_AE_FULL_NAME — Constructs a person's full name in the UAE-required display sequence. Per the inline documentation, the expected format is <First>, <Father>, <Grandfather>, <Last>, where the father's name is sourced from
PER_INFORMATION1and the grandfather's name fromPER_INFORMATION2. The function accepts the standard person name attributes (first name, middle names, last name, known as, title, suffix, pre-name adjunct) together with the full range of person information flexfield segments (PER_INFORMATION1 through PER_INFORMATION30). It builds and returns the assembled name string, skipping absent segments and normalizing whitespace through trimming and concatenation logic. The unusual breadth of the parameter list reflects that the UAE name rules may draw on any of the descriptive flexfield segments configured for the legislation. - DERIVE_HR_LOC_ADDRESS — Derives a formatted HR location address. This is the unit surfaced by the user's search term derive_hr_loc_address. It is the address-side counterpart to the name formatter: where the first function assembles UAE person names, this function assembles the location address representation needed by UAE HR processes, ensuring a consistent postal/address presentation wherever location data is consumed.
Tables Accessed
The only table documented as referenced through APPS synonyms is DUAL. This indicates that the package performs no persistent reads or writes against HR or FND base tables; all input data is supplied by the caller as parameters, and output is returned as a scalar value. The use of DUAL is consistent with an internal SELECT used to bind the concatenated string expression and return it from the function body, a common idiom in this style of PL/SQL utility code (visible at line 60 of the source excerpt). No insert, update, or delete activity is documented.
Usage Notes
Because PER_AE_FULL_NAME and DERIVE_HR_LOC_ADDRESS are internal utility functions rather than public APIs, they are typically invoked indirectly. Oracle HRMS forms and localization routines for the UAE call these functions whenever a person's full name or a location address must be rendered or transmitted. Customizations, reports, and interfaces targeting UAE legislation may call them directly from custom PL/SQL, but should do so with the understanding that ETRM classifies the package as OTHER, meaning Oracle does not guarantee API-level backward compatibility for its signatures across patches. The metadata records zero inbound references from other packages, reinforcing that the primary consumers are forms and standard HRMS code within the localization rather than dependent PL/SQL libraries.
-
PACKAGE BODY: APPS.HR_AE_UTILITY
12.2.2
-
PACKAGE: APPS.HR_JP_UTILITY
12.2.2
-
PACKAGE: APPS.HR_JP_UTILITY
12.1.1
-
PACKAGE: APPS.HR_IN_UTILITY
12.2.2
-
PACKAGE: APPS.HR_IN_UTILITY
12.1.1
-
PACKAGE: APPS.HR_AE_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HR_JP_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_JP_UTILITY
12.2.2
-
PACKAGE: APPS.HR_CN_UTILITY
12.1.1
-
PACKAGE: APPS.HR_CN_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HR_IN_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_IN_UTILITY
12.2.2
-
PACKAGE: APPS.HR_GB_UTILITY
12.1.1
-
PACKAGE: APPS.HR_GB_UTILITY
12.2.2
-
PACKAGE: APPS.HR_MX_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_CN_UTILITY
12.1.1
-
PACKAGE: APPS.HR_US_UTILITY
12.1.1
-
PACKAGE: APPS.HR_MX_UTILITY
12.2.2
-
PACKAGE: APPS.HR_US_UTILITY
12.2.2
-
PACKAGE: APPS.HR_CA_UTILITY
12.2.2
-
PACKAGE: APPS.HR_CA_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_CN_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HR_CA_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HR_CA_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_US_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HR_US_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_GB_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_GB_UTILITY
12.2.2
-
APPS.HR_AE_UTILITY dependencies on HR_AE_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HR_MX_UTILITY
12.1.1
-
PACKAGE BODY: APPS.HR_MX_UTILITY
12.2.2
-
APPS.HR_CA_UTILITY dependencies on HR_API
12.1.1
-
APPS.HR_US_UTILITY dependencies on HR_API
12.1.1
-
APPS.HR_CA_UTILITY dependencies on HR_API
12.2.2
-
APPS.HR_US_UTILITY dependencies on HR_API
12.2.2