Search Results check_balance_exists

Overview

APPS.PAY_ADHOC_UTILS_PKG is a utility package body within the Oracle Payroll (PAY) schema of Oracle E-Business Suite. Its documented API classification is "OTHER," meaning it is an internal helper package rather than a formally supported public API. The package consolidates a wide range of ad-hoc lookup, decoding, validation, and salary-comparison routines required by payroll element entry processing, balance definition maintenance, and assignment-level checks. Typical callers are payroll forms, concurrent programs, and other PL/SQL packages that need convenient access to element, balance, and assignment metadata without re-implementing joins against the underlying PAY and HR tables.

The header comment $Header: pyadcutl.pkb 120.3.12000000.1 2007/01/17 15:14:59 appldev noship $ indicates the file was last rebuilt against the 12.0.0 code line, and it remains in the 12.1.1 and 12.2.2 file systems as a NOSHIP-tier object used internally by the product. The user search term "get_balance_date" is not among the sixteen documented program units; the closest documented routine is GET_BAL_VALID_LOAD_DATE, which returns the effective/validation load date associated with a balance definition. Consumers looking for a balance-date lookup should use that function, or query PAY_BALANCE_TYPES directly if they need the balance's start and end dates.

Key Procedures and Functions

The package exposes sixteen documented program units, grouped by function:

• Decoding helpers — DECODE_OPM_TERRITORY, DECODE_CURRENCY_CODE, DECODE_EVENT_GROUP, and DECODE_ELEMENT_TYPE translate stored codes into display values, typically via FND_LOOKUP_VALUES.
• Element metadata — GET_ELEMENT_NAME returns an element type's name; GET_ELEMENT_LINK_STATUS reports whether an element is linked to an assignment; GET_INPUT_NAME returns the input value name for an element entry, mirroring the logic in the POPULATE_INPUT_NAME cursor shown in the source.
• Salary comparison — GET_PREV_SALARY, GET_PREV_SAL_CHANGE_DATE, and GET_MULTIPLE_SAL_CHANGE_FLAG support salary-basis validation by retrieving the prior salary value, its change date, and a flag indicating multiple changes within a period.
• Balance checks — CHECK_BALANCE_EXISTS confirms a balance is defined; GET_BAL_VALID_LOAD_DATE returns the validation/load date for a balance; GET_BANK_DETAILS retrieves bank account information associated with a person or assignment.
• Assignment and context — CHECK_ASSIGNMENT_IN_SET verifies whether an assignment belongs to a given HR assignment set; FLEX_CONCATENATED builds a concatenated key from a key flexfield; CHK_POST_R11I detects whether the instance is post-11i, which is useful for backward-compatible logic.

The package-level constant g_package is used to prefix error messages, consistent with Oracle's standard error-handling convention.

Tables Accessed

The documented table references cluster around balance and element metadata: PAY_BALANCE_TYPES, PAY_BAL_ATTRIBUTE_DEFINITIONS, PAY_BALANCE_ATTRIBUTES, PAY_BALANCE_DIMENSIONS, PAY_BALANCE_VALIDATION, and PAY_DEFINED_BALANCES support CHECK_BALANCE_EXISTS and GET_BAL_VALID_LOAD_DATE. Element-related lookups use PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_TYPES_F, and PAY_INPUT_VALUES_F, plus their _TL translation tables. Assignment-set validation reads HR_ASSIGNMENT_SETS and HR_ASSIGNMENT_SET_AMENDMENTS. Environment detection uses FND_APPLICATION, FND_PRODUCT_INSTALLATIONS, FND_ID_FLEX_SEGMENTS, and FND_LOOKUP_VALUES. All access is via APPS synonyms and respects the language of the session through userenv('LANG'), as demonstrated by the POPULATE_INPUT_NAME cursor joining the _TL views.

Usage Notes

This package is referenced by twelve other packages, confirming its role as a shared internal library. It should not be treated as a formally supported public API; Oracle does not publish a compatibility guarantee for its signatures across releases. Customizations should call it only when the same logic is not available from a supported API such as PAY_ELEMENT_ENTRY_API or HR_ASSIGNMENT_API. Typical invocation points include payroll element entry forms, balance definition setup forms, and concurrent programs validating element links or balance membership. Because the package queries translation and installation tables, callers must ensure that FND_GLOBAL.APPS_INITIALIZE or an equivalent session initialization has run before invocation, otherwise userenv('LANG') and product-installation checks may return unexpected results.