Search Results upd_balance_feed
Overview
The APPS.HR_BALANCES package is a foundational Oracle EBS Human Resources (Payroll) PL/SQL package that manages the configuration metadata underpinning payroll balance processing. It holds procedures and functions related to the definition, feeding, classification, and deletion of balance types and their associated feeds. In the Oracle HRMS/Payroll data model, a balance feed establishes the relationship between an input value of an element and a defined balance, determining how an element contributes to the accumulated balances that payroll reports, costing, and statutory calculations depend upon. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than those of its owner.
The package's original header documents that it operates over the element type, input value, sub-classification rule, balance feed, balance type, balance classification, and defined balance configuration tables. Its stated dependencies are hr_utility, and it is used by hr_input_values and hr_elements, embedding it firmly in the element and balance configuration layer of Payroll setup. The ETRM record for 12.2.2 lists eight documented procedures and functions and identifies 36 other packages that reference it.
Key Procedures and Functions
INS_BALANCE_FEED— Inserts a new balance feed record, creating the association between an element input value and a balance.UPD_BALANCE_FEED— Updates an existing balance feed definition.CHK_DEL_BALANCE_FEED— Validation routine executed prior to deletion, confirming that a balance feed may be safely removed without violating dependent configuration.DEL_BALANCE_FEED— Deletes a balance feed record once validation has succeeded.DEL_BALANCE_TYPE_CASCADE— Removes a balance type together with its dependent records, performing the cascading delete logic required to maintain referential integrity across the balance configuration tables.CHK_INS_SUB_CLASS_RULES— Validation routine invoked before inserting sub-classification rules, which govern how balances are grouped and reported.CHK_INS_BALANCE_FEED— Validation routine invoked before inserting a balance feed, checking the proposed definition for consistency.DECODE_BALANCE— A function introduced in version 115.1 (08-NOV-99) that decodes a balance reference into its meaningful representation. This is the routine most frequently sought by developers searching ondecode_balance, as it is commonly called when balance identifiers require interpretation in custom code or reports.
Tables Accessed
The package reads and writes the core payroll configuration tables accessed through APPS synonyms:
PAY_BALANCE_FEEDS_FandPAY_BALANCE_FEEDS_S— the date-effective and translated balance feed definitions manipulated by the insert, update, check, and delete routines.PAY_BALANCE_TYPES,PAY_BALANCE_TYPES_TL, andPAY_BALANCE_CLASSIFICATIONS— balance type and classification metadata, including the cascade-delete target ofDEL_BALANCE_TYPE_CASCADE.PAY_DEFINED_BALANCES— balances defined at the business-group level which feeds accumulate into.PAY_ELEMENT_TYPES_FandPAY_INPUT_VALUES_F(withPAY_INPUT_VALUES_F_TL) — the element and input value definitions that balance feeds connect to balances.PAY_SUB_CLASSIFICATION_RULES_F— rules used to sub-classify balances, validated byCHK_INS_SUB_CLASS_RULES.HR_APPLICATION_OWNERSHIPS— used to resolve application ownership, consistent with theAUTHID CURRENT_USERdeclaration.
Usage Notes
HR_BALANCES is an internal configuration API, not an end-user interface. It is typically invoked indirectly through the Oracle Forms-based Payroll setup windows — notably the Element, Input Values, and Balance definitions forms — where hr_elements and hr_input_values call into it to create and maintain balance feeds. Because the ETRM record shows 36 referencing packages, it should be treated as a dependency of broader payroll configuration flows rather than a standalone entry point. Custom code should call the validation routines (CHK_INS_BALANCE_FEED, CHK_DEL_BALANCE_FEED, CHK_INS_SUB_CLASS_RULES) before the corresponding DML procedures to preserve data integrity, and should respect the date-effective (F/S) table pattern. Direct DML against the underlying tables is discouraged; the package encapsulates the required validation and cascade logic.