Search Results pay_bth_bus




Overview
Explore in AI Chat

Overview

PAY_BTH_BUS is a PL/SQL business logic package in the APPS schema that encapsulates the core validation and security-context logic for Oracle Payroll batch header processing. In Oracle EBS 12.1.1 and 12.2.2, the PAY_BTH_% family of packages implements a consistent "bus/ins/upd/del/shd" design pattern, where the "_BUS" package holds the business rules and validation routines, the "_INS", "_UPD", and "_DEL" packages handle row-level DML, and the "_SHD" package acts as a shadow or public synonym layer. PAY_BTH_BUS sits at the centre of this pattern for batch headers, centralising the logic that the insert, update, and delete packages all reuse rather than duplicating validation code.

The package is classified as an OTHER API in the ETRM documentation, meaning it is an internal or supporting API rather than a formally published public interface. It is nonetheless a critical dependency: five other packages (PAY_BCT_BUS, PAY_BTL_BUS, PAY_BTH_INS, PAY_BTH_UPD, and PAY_BTH_DEL) reference it, and it in turn references the shadow object PAY_BTH_SHD and the SYS.STANDARD package.

Key Procedures and Functions

  • SET_SECURITY_GROUP_ID — Establishes the security group context for the current session. Oracle HRMS and Payroll objects are partitioned by security group, and this routine ensures that all subsequent operations in the batch header processing flow are scoped to the caller's business group.
  • RETURN_LEGISLATION_CODE — A function that returns the legislation code applicable to the batch being processed. Legislation drives country-specific validation rules in Payroll, so downstream routines rely on this value to select the correct processing logic.
  • INSERT_VALIDATE — Performs the business-rule validation required before a new batch header row is inserted. It is invoked by PAY_BTH_INS so that insert-time checks (mandatory attributes, referential integrity, and batch status rules) are applied consistently.
  • UPDATE_VALIDATE — Validates a batch header before modification. Called by PAY_BTH_UPD, it guards against invalid state transitions and prevents updates that would violate batch control totals.
  • DELETE_VALIDATE — Confirms that a batch header may safely be deleted, typically checking that no dependent batch lines or control totals remain. Invoked by PAY_BTH_DEL.

Tables Accessed

While no explicit DML is documented for this package, its procedures are designed to support the batch header lifecycle, and the associated tables in this family are:

  • PAY_BATCH_HEADERS — The primary entity this package validates. Holds batch-level information such as batch name, status, and action parameters.
  • PAY_BATCH_LINES — Contains the individual element entries or assignments grouped under a batch header; checked during delete and update validation.
  • PAY_BATCH_CONTROL_TOTALS — Stores aggregated control totals used to reconcile and validate batch contents.
  • PAY_MESSAGE_LINES — Used to surface validation errors and warnings to the user through the Payroll messaging framework.

Usage Notes

PAY_BTH_BUS is not intended to be called directly from forms or concurrent programs. It is invoked indirectly through the batch header DML packages (PAY_BTH_INS, PAY_BTH_UPD, PAY_BTH_DEL), which are themselves driven by the Payroll batch entry forms and by concurrent processes that load or maintain batch data. Because it is classified as an OTHER API, Oracle does not guarantee its signature across releases; customisations should avoid calling PAY_BTH_BUS directly and instead call the supported insert/update/delete entry points. Developers extending batch header processing can reference this package as a model for consistent validation, but must re-validate any assumptions against the target patch level, since internal business rules may change without notice.