Search Results create_input_value
Overview
APPS.PY_FR_ADDITIONAL_ELEMENT_RULES is a PL/SQL package body belonging to the Oracle E-Business Suite Payroll (PY) module, specifically the French localization layer (indicated by the "FR" prefix and the French legislation context). Its principal business responsibility is the automated creation and configuration of additional payroll elements and their associated input values, driven by rules rather than manual setup through the Payroll Element forms. In global payroll implementations, legislation-specific rules frequently require that a set of derived elements and input values be generated consistently across business groups. This package encapsulates that logic so that element structures, input values, and related formula result rules can be provisioned programmatically and in a repeatable manner.
The package operates within the constraints of the Oracle Payroll datetracked model, meaning all element and input value records it creates carry effective start and end dates derived from existing element type definitions. It is classified in ETRM as OTHER, reflecting that it is not a published, supported public API but rather an internal utility used by the localization and by other payroll setup routines.
Key Procedures and Functions
ETRM documents two callable units within this package:
- CREATE_INPUT_VALUE — a function that creates a single input value for a given payroll element. It returns the generated input value identifier. Internally it derives the effective date range from PAY_ELEMENT_TYPES_F, delegates the physical insert to the standard pay_db_pay_setup.create_input_value API, and then calls hr_input_values.chk_input_value to validate the newly created input value against the element type and legislation. The wrapper exists to apply French-localization defaults (for example, units of measure, display sequence, and effective dating) that would otherwise have to be supplied manually at each call site.
- CREATE_EXTRA_ELEMENTS — the controlling routine that orchestrates the creation of the additional elements themselves, invoking CREATE_INPUT_VALUE for each required input value and managing the overall element setup sequence. The package-level global g_package is initialized to reference this routine, which is used in error and logging messages.
Tables Accessed
The package reads and writes the core payroll setup tables through APPS synonyms. Key among them:
- PAY_ELEMENT_TYPES_F — the source of the effective start and end dates used to datetrack each new input value and element definition.
- PAY_INPUT_VALUES_F — the destination for input value records created by CREATE_INPUT_VALUE.
- PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_LINKS_F, and PAY_EVENT_GROUPS — used when establishing element classifications, links, and event associations for the generated elements.
- PAY_FORMULA_RESULT_RULES_F, FF_FORMULAS_F, and FF_FORMULA_TYPES — accessed to attach the appropriate formula result rules and to identify the formulas that drive element behavior.
- PAY_ACCRUAL_PLANS and FND_LOOKUP_VALUES — consulted for accrual configuration and for validating lookup-backed attributes such as units of measure.
Usage Notes
Because PY_FR_ADDITIONAL_ELEMENT_RULES is an internal localization package rather than a public API, it is normally invoked by the French payroll localization setup routines and by other payroll packages (ETRM records two referencing packages) during element provisioning. It is not intended to be called directly from a form or concurrent program in supported customization work; Oracle's guidance is to use the delivered element setup or the supported pay_db_pay_setup and hr_input_values APIs for customer extensions. The "create_input_value" function in particular should be treated as a convenience wrapper whose behavior is tied to French legislation rules and the effective dating of the parent element type. Any custom code calling it must run in the correct business group and legislation context and should expect validation to fail if a duplicate or conflicting input value already exists for the element.
-
PACKAGE BODY: APPS.PY_FR_ADDITIONAL_ELEMENT_RULES
12.2.2
-
PACKAGE BODY: APPS.PY_FR_ADDITIONAL_ELEMENT_RULES
12.1.1
-
PACKAGE BODY: APPS.PAY_INPUT_VALUE_API
12.1.1
-
PACKAGE BODY: APPS.PAY_INPUT_VALUE_API
12.2.2
-
PACKAGE: APPS.PY_FR_ADDITIONAL_ELEMENT_RULES
12.1.1
-
PACKAGE: APPS.PAY_FR_DB_PAY_SETUP
12.2.2
-
PACKAGE: APPS.PY_FR_ADDITIONAL_ELEMENT_RULES
12.2.2
-
PACKAGE: APPS.PAY_DB_PAY_SETUP
12.1.1
-
PACKAGE: APPS.PAY_FR_DB_PAY_SETUP
12.1.1
-
PACKAGE: APPS.PAY_DB_PAY_SETUP
12.2.2
-
PACKAGE: APPS.PAY_ACCRUAL_PLANS_PKG
12.2.2
-
PACKAGE: APPS.PAY_ACCRUAL_PLANS_PKG
12.1.1
-
PACKAGE BODY: APPS.HR_ACCRUAL_PLAN_API
12.2.2
-
PACKAGE BODY: APPS.HR_ACCRUAL_PLAN_API
12.1.1
-
PACKAGE: APPS.PAY_INPUT_VALUE_API
12.1.1
-
PACKAGE BODY: APPS.PAY_ACCRUAL_PLANS_PKG
12.2.2
-
PACKAGE: APPS.PAY_INPUT_VALUE_API
12.2.2
-
PACKAGE BODY: APPS.PAY_ACCRUAL_PLANS_PKG
12.1.1
-
APPS.PAY_ACCRUAL_PLANS_PKG SQL Statements
12.1.1
-
APPS.PAY_ACCRUAL_PLANS_PKG SQL Statements
12.2.2
-
PACKAGE: APPS.HRDYNDBI
12.2.2
-
PACKAGE: APPS.HRDYNDBI
12.1.1
-
PACKAGE: APPS.HR_ACCRUAL_PLAN_API
12.2.2
-
PACKAGE: APPS.HR_ACCRUAL_PLAN_API
12.1.1
-
PACKAGE BODY: APPS.PAY_DB_PAY_SETUP
12.2.2
-
APPS.HRDYNDBI SQL Statements
12.1.1
-
PACKAGE BODY: APPS.PAY_AU_RETRO_UPGRADE
12.1.1
-
PACKAGE BODY: APPS.PAY_FR_DB_PAY_SETUP
12.2.2
-
PACKAGE BODY: APPS.PAY_DB_PAY_SETUP
12.1.1
-
PACKAGE BODY: APPS.PAY_FR_DB_PAY_SETUP
12.1.1
-
APPS.HRDYNDBI SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PAY_AU_RETRO_UPGRADE
12.2.2
-
APPS.PY_FR_ADDITIONAL_ELEMENT_RULES dependencies on PY_FR_ADDITIONAL_ELEMENT_RULES
12.2.2
-
APPS.PY_FR_ADDITIONAL_ELEMENT_RULES dependencies on PY_FR_ADDITIONAL_ELEMENT_RULES
12.1.1
-
APPS.PAY_INPUT_VALUE_API dependencies on HR_UTILITY
12.2.2
-
PACKAGE BODY: APPS.HRDYNDBI
12.1.1
-
PACKAGE BODY: APPS.HRDYNDBI
12.2.2
-
APPS.PAY_INPUT_VALUE_API dependencies on HR_UTILITY
12.1.1
-
APPS.PY_FR_ADDITIONAL_ELEMENT_RULES dependencies on HR_UTILITY
12.1.1
-
APPS.PAY_INPUT_VALUE_API dependencies on PAY_INPUT_VALUES_F
12.2.2
-
APPS.PY_FR_ADDITIONAL_ELEMENT_RULES dependencies on HR_UTILITY
12.2.2
-
APPS.PAY_INPUT_VALUE_API dependencies on PAY_INPUT_VALUES_F
12.1.1
-
APPS.PAY_INPUT_VALUE_API dependencies on PAY_INPUT_VALUE_API
12.1.1
-
APPS.PAY_INPUT_VALUE_API dependencies on HR_API
12.1.1
-
APPS.PAY_INPUT_VALUE_API dependencies on HR_API
12.2.2
-
APPS.HR_USER_INIT_EARN SQL Statements
12.2.2
-
APPS.HR_USER_INIT_EARN SQL Statements
12.1.1
-
APPS.HR_ACCRUAL_PLAN_API dependencies on HR_UTILITY
12.1.1
-
APPS.HR_ACCRUAL_PLAN_API dependencies on HR_UTILITY
12.2.2
-
APPS.HRDYNDBI dependencies on HR_UTILITY
12.2.2