Search Results pay_sdb_bus




Overview
Explore in AI Chat

Overview

PAY_SDB_BUS is an Oracle EBS PL/SQL package owned by the APPS schema that supports the Payroll "Shadow Balance" (SDB) subsystem. Its role is to enforce business-rule validation logic for the shadow balance definition entities — the configurable objects that let a payroll implementation describe which balances, attributes, and derived (defined) balances are captured in the shadow balance tables used by downstream payroll processing and reporting.

Functionally, PAY_SDB_BUS acts as the validation layer of the SDB definition stack. It does not itself perform the physical insert, update, or delete of shadow balance definition rows; rather, it exposes validation entry points that the corresponding DML packages invoke before committing changes. The ETRM metadata classifies the package under API classification "OTHER" and records a dependency on APPS.PAY_SDB_SHD, indicating that shadow-balance shared logic or data access is delegated to a companion package. The package is retained at status VALID, confirming it is an active, compiled component of the 12.1.1 and 12.2.2 application editions.

The ETRM metadata for this object is intentionally minimal — the document lists the package, its package body, SQL statements, and dependency blocks but provides no parameter signatures. The descriptions below therefore rely strictly on the documented procedure names and referenced tables rather than reconstructed argument lists.

Key Procedures and Functions

Three documented procedures are exposed by PAY_SDB_BUS, each aligned to a specific DML operation performed by its sibling packages:

  • INSERT_VALIDATE — Validates the data supplied for a new shadow balance definition record before it is created. It is the entry point invoked by the insert-side DML package (PAY_SDB_INS) to confirm that the proposed definition satisfies the business rules governing shadow balance types, attributes, and defined balances.
  • UPDATE_VALIDATE — Validates the modified values of an existing shadow balance definition prior to update. It is invoked by the update-side DML package (PAY_SDB_UPD) to ensure that changes preserve referential and business-rule integrity of the definition.
  • DELETE_VALIDATE — Validates that an existing shadow balance definition may be removed. It is invoked by the delete-side DML package (PAY_SDB_DEL) to prevent deletion of a definition that is still referenced or otherwise prohibited from removal.

All three procedures share the same purpose pattern — pre-DML rule checking — and are called exclusively from the SDB CRUD packages rather than directly by end users. The metadata records three documented procedures and does not document parameters; parameter lists must be read from the package specification in the database. No functions are documented for this package.

Tables Accessed

The ETRM metadata documents five tables referenced through APPS synonyms, each corresponding to a definitional layer of the shadow balance model:

  • PAY_SHADOW_BALANCE_TYPES — the catalog of shadow balance types; validation confirms that a proposed or modified definition uses a valid balance type.
  • PAY_SHADOW_BAL_ATTRIBUTES — the attributes associated with shadow balances; validation confirms attribute assignments are consistent.
  • PAY_SHADOW_DEFINED_BALANCES — the derived/defined balance definitions that roll up or derive from base balances; validation checks the definition's composition rules.
  • PAY_TEMPLATE_CORE_OBJECTS — core objects of the payroll template model; validation checks that a shadow balance definition does not conflict with template core object configuration.
  • PAY_TEMPLATE_EXCLUSION_RULES — exclusion rules governing template objects; validation ensures a proposed definition does not violate an exclusion rule.

The package therefore reads these tables to evaluate candidate rows and to detect existing usage before permitting insert, update, or delete actions. Write access is primarily the responsibility of the DML packages, not the validation package.

Usage Notes

PAY_SDB_BUS is an internal component rather than a public user-facing API. It is invoked indirectly during the maintenance of shadow balance definitions, typically through the Payroll setup forms that manage shadow balance and template configuration, and through any concurrent or custom program that manipulates the same entities. The documented dependency chain confirms this: PAY_SDB_BUS is referenced by PAY_SDB_BUS (its own body), PAY_SDB_DEL, PAY_SDB_INS, and PAY_SDB_UPD, and it in turn references PAY_SDB_SHD. In practice the CRUD packages call the matching validate procedure before executing their DML, so validation is automatic when standard maintenance paths are used.

Custom code should not call PAY_SDB_BUS directly unless it is bypassing the standard DML packages. The recommended pattern for custom maintenance of shadow balance definitions is to use the standard insert, update, and delete APIs, which will route through PAY_SDB_BUS validation. Direct invocation risks inconsistency with the SDB_SHD shared logic and the associated template rules. Because the metadata documents no parameters, developers who must call the procedures should inspect the package specification in the target EBS instance to obtain the exact signatures; signatures may differ across 12.1.1 and 12.2.2 patch levels. The package's compiled status should be monitored using standard EBS validity checks after any payroll patch application, since validation logic in this component is tightly coupled to the payroll balance and template data model.