Search Results pay_set_upd




Overview
Explore in AI Chat

Overview

PAY_SET_UPD is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the Oracle ETRM as an "OTHER" API object. Its name — the abbreviated form of "Payroll Set Update" — indicates that it provides the maintenance logic behind the payroll shadow set construct used by the Oracle Payroll "Shadow" feature set. Shadow sets allow a user to define a logical grouping of payroll elements so that a particular business process, such as a special payroll run or a simulation, can operate against a controlled subset of element types rather than the full element universe. PAY_SET_UPD encapsulates the write-side operations for those definitions, centralising the update logic that would otherwise be scattered across forms, concurrent programs, and dependent APIs.

The package is recorded with a VALID status in the 12.2.2 ETRM repository, confirming that it remains an active, supported component in both the 12.1.1 and 12.2.2 releases. Its dependency list is deliberately narrow, referencing only the standard database package STANDARD, the HR_API security and validation layer, and the shadow table PAY_SET_SHD. This minimalist dependency profile is characteristic of a low-level utility package that performs direct data manipulation while delegating security and validation concerns to HR_API.

Key Procedures and Functions

The ETRM metadata documents a single entry point for this package: the procedure UPD. Consistent with the package's naming and its dependency on PAY_SET_SHD, UPD is the update routine for shadow set records. It accepts the identifying information for an existing set together with the changed attribute values supplied by the caller, validates the caller's access through HR_API, and applies the modification to the underlying shadow set storage. No parameter list is published in the ETRM excerpt, and none should be assumed; integrators should inspect the package specification in the target instance with USER_SOURCE or the Oracle EBS API documentation before calling it directly. The single-procedure footprint suggests that insert, delete, and query operations are handled elsewhere — likely by sibling packages or by the shadowing framework itself — leaving PAY_SET_UPD responsible solely for mutation of one or more attributes of an existing set.

Tables Accessed

PAY_SET_UPD operates against PAY_SHADOW_ELEMENT_TYPES (referenced through an APPS synonym). This table holds the definition of element types that have been flagged for inclusion in shadow sets, and it is the persistence target that the UPD procedure modifies. The package also depends on PAY_SET_SHD, a shadow (history/audit) counterpart that typically receives the pre-update image of a row when it is changed. The presence of PAY_SET_SHD in the dependency list indicates that updates performed through this package are auditable and that the "SHD" table follows the standard Oracle EBS shadow-table convention of preserving prior values for retroactive or date-tracked processing. Because PAY_SET_SHD is referenced with "show dependent code" in the ETRM manifest, some or all of this activity may occur indirectly through a trigger or an internal call path rather than an explicit statement in the package body.

Usage Notes

PAY_SET_UPD is an internal, lower-level package rather than a public integration API. ETRM records it as referenced by exactly one other package, PAY_SHADOW_ELEMENT_API, which is the logical public entry point for shadow element maintenance. The package is therefore normally invoked indirectly: a user action in the Payroll shadow element maintenance form, a concurrent program that refreshes shadow set membership, or a custom extension that calls PAY_SHADOW_ELEMENT_API will ultimately reach PAY_SET_UPD.UPD. Direct invocation from custom code is technically possible but is discouraged in 12.1.1 and 12.2.2 because the parameter signature is not published in the ETRM repository and because bypassing PAY_SHADOW_ELEMENT_API risks skipping validation and audit logic. Customers upgrading from 12.1.1 to 12.2.2 should be aware that the Online Patching (adop) architecture does not alter this package's contract; it remains a valid, non-editioned object in the APPS schema and is unaffected by editioning views on the payroll tables it touches.