Search Results decode_elmnt_bal_information

Overview

APPS.HR_LEGISLATION_LOCAL is a delivered PL/SQL package body in the Oracle E-Business Suite HRMS (Human Resources) schema. Its documented purpose is to load legislative startup data and to support subsequent legislative refreshes. The package does not itself contain country-specific business logic; instead it exposes a standard entry point that localization teams extend so that jurisdiction-specific routines can be invoked in a consistent manner during installation and upgrade of statutory data. The header comment records that it was created in 1993 and has been maintained continuously through releases 7.0, 8.0, and the 11i/12.x code line (header revision pelegloc.pkb 120.1.12000000.1, dated 2007), which confirms its role as a long-lived infrastructure package rather than a version-specific artifact. In Oracle EBS 12.1.1 and 12.2.2 it remains an APPS-owned object classified as OTHER, meaning it is not a public API in the formal sense and is intended primarily for internal delivery and localization use.

Key Procedures and Functions

ETRM documents five callable units in the package body:

• INSTALL — The generic entry point used to drive legislative data installation. Localization teams place their specific table-loading calls behind this procedure so that the delivery mechanism can invoke the correct jurisdiction logic without knowing its contents.
• INSTALL_US_NEW — The United States-specific installer. It is responsible for loading US legislative reference data such as balance types, element types, taxability rules, and state or federal tax information.
• DECODE_ELMNT_BAL_INFORMATION — A decoding routine associated with the element/balance relationship. Its role is to translate stored element-versus-balance configuration into the values required by downstream legislative processing.
• TRANSLATE_US_ELE_DEV_DF — Converts US element definitions into the developer/definition format required for startup or refresh delivery.
• TRANSLATE_CA_ELE_DEV_DF — The Canadian counterpart, performing the same element definition translation for Canadian legislative data.

The documented history of the package corroborates these functions: successive revisions added columns such as FS_LOOKUP_TYPE to PAY_STATE_RULES handling and CLASSIFICATION_ID to taxability rule handling, and introduced update-if-exists behaviour for state rule delivery.

Tables Accessed

The package reads and writes both HR and FND foundation tables through APPS synonyms. Legislative reference tables include HR_S_BALANCE_TYPES, HR_S_ELEMENT_TYPES_F, HR_S_LEGISLATION_RULES, HR_S_REPORT_LOOKUPS, HR_S_STATE_RULES, HR_S_TAXABILITY_RULES, and the US-specific tax tables HR_S_US_CITY_TAX_INFO_F, HR_S_US_COUNTY_TAX_INFO_F, and HR_S_US_FEDERAL_TAX_INFO_F. Supporting and status tables include HR_S_HISTORY, HR_STU_EXCEPTIONS, HR_REPORT_LOOKUPS, and HR_ORG_INFO_TYPES_BY_CLASS. Foundation tables used to determine context are FND_ID_FLEX_STRUCTURES and FND_PRODUCT_INSTALLATIONS, the latter used historically to detect whether Payroll is installed before deleting from certain control tables. These accesses align with the package's purpose: writing delivered legislative rows, versioning them in history, and gating behaviour on product installation state.

Usage Notes

HR_LEGISLATION_LOCAL is normally invoked during legislative startup data delivery and during legislative refresh, not from end-user forms. It is referenced by one other package, consistent with its role as a shared utility rather than a top-level driver. In the 12.1.1 and 12.2.2 file systems the body resides as pelegloc.pkb under the HR legislative delivery directory and is compiled into the APPS schema with the standard invoker-rights conventions. The search term "element_information10" relates to the element information structures this package installs and translates, including element-versus-balance information decoded by DECODE_ELMNT_BAL_INFORMATION and the element definitions translated by TRANSLATE_US_ELE_DEV_DF and TRANSLATE_CA_ELE_DEV_DF. Custom code should treat the package as internal and avoid direct calls, since localization teams may replace behaviour in later legislative patches.