Search Results input_values_f

Overview

The APPS.HR_LEGISLATION_ELEMENTS package body is an Oracle EBS seed-data installation utility that belongs to the Oracle HRMS / Payroll (Payroll Engine, "pe" prefix) product family. Its principal business function is to transfer startup (seed) configuration rows — element classifications, element types, balance types, balance classifications, element sets, formula definitions, and benefit classifications — from the HR_S_ seed tables into the corresponding live application tables during product installation, upgrade, or a fresh Business Group setup. The package name reflects its role: it delivers the legislation-specific payroll element definitions that Oracle ships for each country (legislation) into a live environment.

The pelegele.pkb header and version string (120.8) confirm it is a shipped, Oracle-maintained artifact. The terminology used in the source excerpts — "INSTALLATION PROCEDURE", "delivery of startup data", savepoints, surrogate keys, and the exception helper crt_exc — indicates a classic EBS installation pattern: iterate over seed rows in dependency order, assign new surrogate primary keys, and roll back to the last savepoint on any unhandled error so that the installation can continue with the next primary key.

Key Procedures and Functions

The documented package exposes a single procedure, INSTALL. Its purpose is to drive the phased seed-data installation process. Internally, the source shows one concrete installation routine, install_ele_class(p_phase IN number), which copies rows from HR_S_ELEMENT_CLASSIFICATIONS into the live PAY_ELEMENT_CLASSIFICATIONS entity. That routine declares a cursor (stu) that projects the startup columns — including classification_id, legislation_code, legislation_subgroup, priority and costing flags, and FREQ_RULE_ENABLED — ordered by parent_classification_id descending so that child classifications are not installed before their parents. A local exception helper, crt_exc, reports any exceptions raised during delivery (the comment references FF_CONTEXTS_F and confirms rollback-to-savepoint semantics). The p_phase parameter allows the caller to control which installation phase executes.

Tables Accessed

The package reads from the HR_S_ seed tables and writes into their live counterparts, all referenced through APPS synonyms. The documented set includes: HR_S_ELEMENT_CLASSIFICATIONS, HR_S_ELEMENT_TYPES_F, HR_S_ELEMENT_TYPE_RULES, HR_S_ELEMENT_SETS, HR_S_BALANCE_TYPES, HR_S_BALANCE_CLASSIFICATIONS, HR_S_BALANCE_FEEDS_F, HR_S_BENEFIT_CLASSIFICATIONS, and HR_S_APPLICATION_OWNERSHIPS. Target and reference tables include BEN_BENEFIT_CLASSIFICATIONS, FF_FORMULAS_F, FND_APPLICATION, FND_FLEX_VALUE_SETS, FND_PRODUCT_INSTALLATIONS, HR_LEGISLATION_SUBGROUPS, and the live element classification table. FND_PRODUCT_INSTALLATIONS and HR_S_APPLICATION_OWNERSHIPS are used to determine installation and ownership state; FF_FORMULAS_F and FND_FLEX_VALUE_SETS are consulted because element types reference formula and value-set definitions. The input_values_f term that led a user here typically describes the design-time input-value metadata associated with those element types, which this package installs alongside the element definitions.

Usage Notes

HR_LEGISLATION_ELEMENTS is an internal installation package and is not intended for direct invocation from forms or concurrent programs in normal runtime operation. It is normally called by the Oracle Applications installation, upgrade, or Business Group setup drivers — for example, during the loading of legislation seed data — and is referenced by one other package, which orchestrates the sequence. Because it manipulates surrogate keys and relies on savepoint-based rollback, direct custom invocation is strongly discouraged. Custom code requiring element setups should use supported APIs such as PAY_ELEMENT_CLASSIFICATION_API or the HRMS element-type APIs rather than calling this package directly. Note that the documented metadata and source excerpt are limited and reflect version 12.1.1 / 12.2.2 behavior; the object's effective logic should always be confirmed against the delivered source in the deployed patch level.