Search Results pay_balance_classifications_s

Overview

The APPS.PAY_BAL_CLASSIFICATIONS_PKG package body encapsulates the core data-maintenance logic for Oracle Payroll balance classifications in Oracle E-Business Suite 12.1.1 and 12.2.2. Balance classifications define how a payroll balance is categorized for reporting, costing, and statutory purposes; they form the linkage between payroll balances and the classifications applied to them through the PAY_BALANCE_CLASSIFICATIONS entity. The package provides a controlled, API-style interface for creating, modifying, locking, and removing rows in that entity, shielding callers from direct DML against the underlying tables and from the associated validation and derived-column maintenance.

ETRM classifies this package as OTHER rather than a public, documented business API. This is significant: the package is a supporting implementation unit invoked primarily by Oracle Payroll forms and internal processing, not a formally published integration interface. It is not referenced by any other database object according to the dependency metadata, which confirms its role as a leaf-level implementation module rather than a shared library.

Key Procedures and Functions

The package exposes four documented procedures, all following the standard Oracle Forms / Table API naming convention:

• INSERT_ROW — Creates a new balance classification record, populating the target table columns and maintaining any system-derived attributes required for a valid classification row.
• LOCK_ROW — Acquires a row-level lock on an existing classification record, providing the concurrency control contract required by the Oracle Forms block-level locking protocol and by batch callers that must serialize updates.
• UPDATE_ROW — Applies changes to an existing classification record, enforcing the validation rules that govern allowable modifications.
• DELETE_ROW — Removes a balance classification record, subject to the referential and business-rule constraints enforced before deletion.

No parameter lists are documented in the ETRM metadata; callers should inspect the package specification in the target environment before invoking these procedures directly.

Tables Accessed

The package operates against three documented tables, referenced through APPS synonyms:

• PAY_BALANCE_CLASSIFICATIONS — The primary transactional table holding balance classification definitions; the target of all insert, update, lock, and delete activity.
• PAY_BALANCE_CLASSIFICATIONS_S — The translated (TL-style) companion table storing language-specific classification names and descriptions. This is the object users most commonly locate when searching for pay_balance_classifications_s.
• PAY_ELEMENT_CLASSIFICATIONS — Read and validated to ensure a classification is applied only to element classifications that permit it, preserving the element-to-balance relationship model.

Additional dependencies documented in the metadata include the HR_BALANCE_FEEDS and HR_UTILITY packages for balance-related processing logic, and APP_EXCEPTION and FND_MESSAGE for standardized error handling and message token resolution. SYS.DUAL and the STANDARD package supply scalar queries and base PL/SQL functionality.

Usage Notes

Because the DML procedures follow the Forms-oriented Table API pattern, the package is typically invoked from the Balance Classifications maintenance form in the Payroll responsibility, where the form's block triggers call INSERT_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW during standard record navigation and commit processing. In this mode the procedures also maintain the _S translation rows in step with the base table.

Custom code should treat these procedures as internal rather than as a supported public API. Direct insertion into PAY_BALANCE_CLASSIFICATIONS and PAY_BALANCE_CLASSIFICATIONS_S bypasses the validation and translation maintenance performed here and risks creating inconsistent classification data. Where programmatic maintenance of balance classifications is genuinely required, the procedures should be called within a transaction that also supplies valid WHO column values, and the package specification in the target environment should be reviewed first, since the ETRM documentation records only procedure names and dependencies, not signatures. The package operates within the APPS schema and inherits the standard Oracle EBS concurrency and error-propagation conventions from APP_EXCEPTION and FND_MESSAGE.