Search Results pay_bct_del




Overview
Explore in AI Chat

Overview

PAY_BCT_DEL is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM repository as an "OTHER" API type rather than a public or private API. Its name reflects its functional role within the Oracle Payroll module: the management of Payroll Batch Control Totals (BCT) deletion logic. The package operates as an internal utility that supports the batch element entry and batch control totals infrastructure of Oracle Payroll, a module used to capture, load, and validate large volumes of payroll element entries through batch processes rather than individual online entry. In that context, control totals act as reconciliation checkpoints — they aggregate monetary and unit values across a batch so that payroll administrators can verify that the loaded batch reconciles to an external source such as a time system or third-party payroll feed. PAY_BCT_DEL provides the deletion routine that removes or resets these control total records when a batch is discarded, reloaded, or otherwise invalidated, ensuring that stale totals do not remain in the base tables and corrupt subsequent reconciliation checks. The package is documented as VALID at the database level in release 12.1.1 and 12.2.2 and is fully object-managed within the ETRM metadata repository.

Key Procedures and Functions

ETRM documents a single callable program unit within this package, identified as DEL. No additional parameter list is published in the metadata, and none is inferred here. The procedure's documented purpose is the removal of batch control total data. Conceptually, DEL is invoked when a caller needs to purge the control totals associated with a given batch or batch line before those totals are recalculated or before the batch is removed altogether. Because it is the only documented routine and it holds an "OTHER" API classification, DEL should be treated as an internal, non-public entry point rather than a supported integration surface. Oracle's published ETRM record lists PAY_BCT_DEL itself as one of the objects that references PAY_BCT_DEL, which indicates the package exposes a routine that may be called recursively or through an internal wrapper — a pattern common in utility packages that provide both a public deletion entry point and an internal worker.

Tables Accessed

The ETRM documentation records exactly one base table accessed by this package through APPS synonyms: PAY_BATCH_CONTROL_TOTALS. This is the principal Payroll table that stores aggregated control total amounts and units for batch element entry batches. Deletion activity against this table is the core purpose of DEL. The package also references PAY_BCT_SHD, an archived or shadow copy of the control totals data that is used for migration, purge, and archival operations in Oracle Payroll. Dependencies on SYS.STANDARD indicate that the package body relies on standard PL/SQL language constructs and types. PAY_BATCH_CONTROL_TOTALS is the only documented DML target; any broader table interaction is not supported by the metadata excerpt and should be confirmed directly against the package source before custom code is written against it.

Usage Notes

PAY_BCT_DEL is an internal support object. It is not intended for direct invocation from forms, concurrent programs, or custom interfaces, and neither Oracle Forms nor standard Payroll concurrent programs in the documented metadata list it as a required processing step. Custom code that must clear batch control totals should preferably use the documented public APIs of the Payroll batch element entry layer, particularly PAY_BATCH_ELEMENT_ENTRY_API, which is documented as referencing PAY_BCT_DEL. That API is the supported entry point for batch element entry operations and will invoke the deletion logic internally when a batch is rolled back or invalidated. Direct calls to PAY_BCT_DEL.DEL should be restricted to corrective or data-fix scripts executed under an approved change control process, and only after verifying the object name and signature in the target environment, since the package has no published API specification. Because the routine performs destructive DML on control totals, administrators should retrieve the affected batch identifiers from PAY_BATCH_CONTROL_TOTALS before execution and take a backup of the relevant rows to support rollback.