Search Results get_result_value_date




Overview

APPS.PAY_JP_BALANCE_PKG is a Japan-localized payroll utility package within the Oracle E-Business Suite Oracle Payroll module. Its principal business function is to provide fast, programmatic access to payroll balance values, run result values, and element entry values for a given assignment, assignment action, or effective date. The package abstracts the often complex join paths across balance types, balance dimensions, run results, element entries, and input values, so that Japanese payroll processes, statutory reports, and custom fast formulas can retrieve validated numeric, character, or date values without embedding low-level SQL in each calling object.

The package header carries the RCS identifier pyjpblnc.pkh 120.0.12000000.1, dated 2007, and is owned by APPS. ETRM classifies the package as API classification OTHER, meaning it is not a public, supported business API in the same sense as a datetracked entity API, but rather an internal utility surface that is nonetheless widely reused across the product.

Key Procedures and Functions

The package exposes 27 documented functions, broadly grouped into four families:

Tables Accessed

The package reaches fourteen documented tables through APPS synonyms. Assignment and payroll context comes from PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, and PER_ALL_ASSIGNMENTS_F. Balance metadata and values are drawn from PAY_BALANCE_TYPES, PAY_BALANCE_DIMENSIONS, PAY_DEFINED_BALANCES, and PAY_BALANCE_FEEDS_F. Run result data is read from PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES. Element entry and input value data come from PAY_ELEMENT_TYPES_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_INPUT_VALUES_F, and PAY_LINK_INPUT_VALUES_F. The functions are read-only with respect to payroll data.

Usage Notes

PAY_JP_BALANCE_PKG is most commonly invoked from Oracle Forms, from PL/SQL fast formulas, and from custom concurrent programs that need balance or entry values for Japanese payroll calculations. It is also referenced by 26 other packages in the APPS schema, making it a shared supporting utility. Because it is classified OTHER rather than a supported public API, customizations should treat the signatures as stable for the release but validate behavior after patches. Callers must supply the correct business group, assignment action, or effective date context; passing an assignment action that does not belong to the intended payroll run will return values from the wrong processing context.