Search Results input_value_proc

Overview

PQP_PRORATION_WRAPPER is an Oracle EBS PL/SQL package owned by the APPS schema that supports proration processing within the Oracle Payroll and Advanced Benefits (OLTP) legislative and payroll engine. Proration in Oracle EBS refers to the proportional allocation of an element entry's value, eligibility, or cost across a partial pay period — for example, when an employee is hired, terminated, transfers, or changes assignment partway through a payroll period. The package acts as a wrapper layer that validates and applies proration rules by inspecting configuration data such as formula definitions, element classifications, input values, trigger events, and assignment attributes.

In the EBS 12.1.1 and 12.2.2 release streams, this object is catalogued with an API classification of OTHER, meaning it is not exposed as an end-user-facing public API but rather serves as internal infrastructure invoked by the payroll processing engine, proration routines, and related payroll batch processes. Its status is VALID in the ETRM metadata, confirming the package compiles cleanly against the documented schema. Its structure reflects a metadata-driven design: rather than hard-coding proration logic, it reads the configured formulas, element definitions, and event tracking setup to determine how proration should be applied for a given assignment.

Key Procedures and Functions

The package exposes six documented program units:

• STANDARD_PROC — The standard entry point and orchestrating procedure, typically responsible for initializing context, sequencing the proration workflow, and invoking the more granular handlers.
• PRORATION_GROUP_PROC — Processes proration at the group level, resolving groups of related elements, event groups, or trigger components that must be prorated together.
• ELEMENT_PROC — Handles proration logic for a specific payroll element, drawing on element type definitions, classifications, and extra information.
• INPUT_VALUE_PROC — Applies proration to element input values, ensuring the numeric inputs attached to an element entry are scaled consistently with the proration factor.
• FORMULA_PROC — Evaluates or invokes the formula (and its formula type) associated with the element to drive prorated calculations.
• GET_CONTRACT_TYPE — A retrieval function that returns the applicable contract type, which influences how proration is calculated for the assignment.

Tables Accessed

The package reads configuration and transactional metadata through APPS synonyms. Formula-related tables — FF_FORMULAS_F, FF_FORMULAS_S, and FF_FORMULA_TYPES — supply the formula definitions and classifications used in proration calculations. Element configuration is retrieved from PAY_ELEMENT_TYPES_F, PAY_ELEMENT_CLASSIFICATIONS, and PAY_ELEMENT_TYPE_EXTRA_INFO. Input value definitions come from PAY_INPUT_VALUES_F, while PAY_FUNCTIONAL_AREAS and PAY_FUNCTIONAL_USAGES establish the functional context in which the element operates. Event and trigger configuration is read from PAY_EVENT_GROUPS, PAY_TRIGGER_EVENTS, and PAY_TRIGGER_COMPONENTS, which determine when proration reacts to dated changes. PAY_DATED_TABLES and PAY_DATETRACKED_EVENTS support date-effective and date-tracked evaluation, and PQP_ASSIGNMENT_ATTRIBUTES_F provides assignment-level attributes that drive proration outcomes. Because this is a wrapper, most access is read-only metadata interrogation rather than direct transactional writes.

Usage Notes

PQP_PRORATION_WRAPPER is not intended to be called directly from forms or custom code. It is invoked internally by the payroll proration engine and related batch processing, typically during payroll runs, QuickPay processing, and proration recalculation when dated events such as hires, terminations, or assignment changes are detected. The package is not referenced by any other APPS packages per the ETRM metadata, which is consistent with its role as a leaf-level internal utility. Administrators and developers encountering this object in a dependency trace should treat it as configuration-driven infrastructure: correctness depends on properly defined formulas, element classifications, input values, and date-tracked events. Debugging proration issues therefore usually means validating this configuration rather than modifying the package itself.