Search Results initialize_balances

Overview

PQP_VEHICLE_MILEAGE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the "OTHER" API category. Despite its name, which suggests vehicle mileage tracking, the package's documented source header (pqbladwr.pkh) and the procedure it exposes indicate that it operates within the Oracle Payroll and Oracle Human Resources legislative/balance initialization domain. The package is defined with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, a common pattern in EBS packages that must respect row-level security and business group partitioning on HRMS tables.

The business function of PQP_VEHICLE_MILEAGE centers on initializing balances for a given business group. Balance initialization is a prerequisite activity in payroll implementations, particularly when migrating from a legacy payroll system, when introducing a new element or balance definition, or when correcting opening balances for a payroll period. The package header dates to 2003 and the source identifier pqbladwr.pkh suggests an association with balance writer routines in the Oracle Payroll (PQP) product family.

Key Procedures and Functions

The package exposes a single documented procedure:

• INITIALIZE_BALANCES — The only procedure in the package specification. It carries the standard concurrent program interface signature comprising errbuf OUT NOCOPY VARCHAR2 and retcode OUT NOCOPY NUMBER, plus an p_business_group_id IN NUMBER parameter. The presence of errbuf/retcode confirms that INITIALIZE_BALANCES is designed to be called directly as a concurrent program or from a host PL/SQL wrapper, reporting success or failure through the standard EBS concurrent manager conventions. Its purpose is to seed or reset payroll balance records scoped to the identified business group.

Tables Accessed

The package reads and writes a set of core Oracle Payroll and HRMS tables through APPS synonyms:

• PAY_RUN_RESULTS — stores the individual payroll run results from which balance values are derived or against which they are validated.
• PAY_PAYROLL_ACTIONS — identifies the payroll action context under which balances are initialized.
• PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPE_EXTRA_INFO — define the elements and their balance feeds, determining which balances are eligible for initialization.
• PAY_ASSIGNMENT_ACTIONS — provides assignment-level action context for the employees being processed.
• PAY_US_RPT_TOTALS — a US legislative reporting totals table, suggesting that balance initialization may interact with statutory reporting aggregates.
• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — supply the assignment and person records scoped to the business group passed into the procedure.

The combination indicates that INITIALIZE_BALANCES traverses the population of assignments for a business group, evaluates the element and balance definitions that apply, and writes or resets balance values based on existing payroll run results.

Usage Notes

PQP_VEHICLE_MILEAGE.INITIALIZE_BALANCES follows the classic concurrent program entry point pattern. Because the documented signature includes errbuf and retcode as OUT NOCOPY parameters, the procedure is most commonly registered as a concurrent program and invoked from the Submit Requests form or scheduled through the concurrent manager. It may also be called from a custom PL/SQL wrapper, a host script using FND_REQUEST.SUBMIT_REQUEST, or from another payroll package where balance initialization is a prerequisite step.

No other packages are documented as referencing PQP_VEHICLE_MILEAGE, so it is best regarded as a standalone utility rather than a dependency in a larger API chain. When invoking it, the caller must supply a valid business group identifier; the AUTHID CURRENT_USER declaration means the caller's security profile governs visibility of the PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F rows processed. Because balance initialization is a data-altering operation, it should be run with the same controls applied to any payroll data update — in a controlled environment, with a validated business group, and preferably after a backup of the affected balance and run result tables.