Search Results get_bg_from_person




Overview

APPS.HR_MX_UTILITY is a legislation-specific PL/SQL package that supports the Mexico (MX) localization of Oracle Human Resources in Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates Mexican statutory and business rules that govern person name formatting, legal employer derivation, tax subsidy calculation, seniority computation, and address derivation. It is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the defining schema, which is significant for packages that must be callable from forms, concurrent programs, and self-service flows under a variety of database users.

The header comment (hrmxutil.pkh 120.6.12010000.1) confirms the original design intent: the package exists primarily to support the Mexico full-name trigger. Over time it has been extended into a general utility library for Mexican HR processing, covering GRE (Global Reporting Entity / legal employer) resolution, tax subsidy percentages, work-related injury protection (WRIP), and hire anniversary and seniority calculations.

Key Procedures and Functions

The ETRM metadata documents 19 procedures and functions. The most prominent include:

Tables Accessed

The package reads and writes through APPS synonyms across the HR, Payroll, and FND schemas:

Usage Notes

HR_MX_UTILITY is an internal support package rather than a public API. It is referenced by 32 other packages in the E-Business Suite, and is typically invoked from Mexico-localized forms (such as the People and Assignment forms when the MX legislation is active), from the full-name trigger, and from payroll and tax reporting code that must derive GRE, tax subsidy, or seniority values. The GET_BG_FROM_PERSON function is commonly reached when a form or report has a person identifier and needs to establish business group context — for example, when validating flexfield segments or applying business-group-specific lookups.

Because the package is AUTHID CURRENT_USER and legislation-specific, it should not be called directly in custom code without reviewing the Mexico localization configuration. Oracle does not document these routines as supported public APIs in all releases, so custom extensions should treat them as internal and version-sensitive. Any change to person, assignment, or payroll data that triggers a full-name or legislative derivation will flow through this package, making it a dependency worth tracing during upgrades from 12.1.1 to 12.2.2.