Search Results pay_bct_upd




Overview
Explore in AI Chat

Overview

APPS.PAY_BCT_UPD is a PL/SQL package body within the Oracle E-Business Suite Payroll (PAY) module. Its name follows the EBS entity-handler naming convention for batch control totals: the PAY_BCT_ prefix identifies the Pay Batch Control Totals entity, and the _UPD suffix identifies this package as the update (and row-level handling) component of that entity's handler set. Batch control totals represent aggregated monetary and count values derived across payroll action batches, and the integrity of those totals is essential for balancing and reconciling payroll runs before they are transferred to costing and accounting.

The package body is registered in the APPS schema with a status of VALID in both 12.1.1 and 12.2.2, and it is classified in the ETRM repository under the API classification OTHER, indicating it is an internal, entity-maintenance API rather than a public, documented business interface. It operates as part of a generated-style handler group that separates insert (PAY_BCT_INS), update, delete, row-level locking (PAY_BCT_RKU), and shadow/audit (PAY_BCT_SHD) responsibilities.

Key Procedures and Functions

The documented package metadata lists a single public program unit, UPD, within the package body. Consistent with the EBS entity-handler pattern, UPD is the update routine responsible for modifying existing rows in the batch control totals entity. It encapsulates the mandatory column validation, WHO-column auditing, and row-processing logic that Oracle Forms and other callers rely upon when a batch control total record is changed. The metadata does not expose a parameter list for UPD, and none is asserted here.

Additional internal program units are implied by the dependency list. The body depends on PAY_BCT_BUS (business rules), PAY_BCT_RKU (row-level locking and "row known unique" handling), and PAY_BCT_SHD (shadow column maintenance), and it references itself recursively, which is typical when handler bodies delegate shared logic. It also references HR_API, HR_CHKFMT, and HR_UTILITY, indicating that update processing enforces HR-consistent formatting and business-rule validation before committing changes.

Tables Accessed

The only documented table referenced via APPS synonyms is PAY_BATCH_CONTROL_TOTALS. This is the base table storing batch control total records. The UPD routine reads and writes rows in this table: reads are used to identify the target record by primary key, validate current values, and enforce concurrency; writes apply the modified total and count attributes together with WHO audit columns. Because the entity package set also includes PAY_BCT_SHD, update operations may propagate values to shadow columns maintained on the same table for audit or cross-business-group visibility.

Usage Notes

PAY_BCT_UPD is not a standalone entry point and is not referenced by any other database object, confirming its role as a called-in handler rather than a caller. It is typically invoked indirectly through the batch control totals entity handler stack, most commonly when a user edits control total information through a Payroll forms-based maintenance window, or when a payroll batch-processing or reconciliation concurrent program recalculates and persists control totals after a payroll action. Custom code should not call UPD directly without first invoking the corresponding business-rules and locking routines, because the update path assumes prior validation and row locking have been performed by PAY_BCT_BUS and PAY_BCT_RKU. Direct DML against PAY_BATCH_CONTROL_TOTALS is strongly discouraged, as it bypasses the audit and validation logic encapsulated in this package body.