Search Results pay_rtu_shd




Overview
Explore in AI Chat

Overview

PAY_RTU_SHD is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the Payroll (PAY) module as an "OTHER" API type. The name derives from "Run Type Usage" (RTU) combined with the "SHD" suffix convention Oracle applies to shadow or shadow-synchronized database objects. In Oracle EBS, the _SHD suffix typically designates the runtime shadow copy of a table or package created to support the Online Patching (adop) infrastructure introduced for 12.2 and carried forward in later releases including 12.1.1 and 12.2.2 configurations. The package provides the procedural logic that reconciles and maintains the effective-dating behavior of the PAY_RUN_TYPE_USAGES entity — the intersection table that governs which payroll run types are permitted against which payroll definitions and legislative contexts.

Its documented status is VALID, and it is referenced by four other database packages, indicating it occupies a shared utility role rather than standing as a top-level public API. The package is not itself referenced by any object in the ETRM dependency map beyond its consumers, confirming it is an internal implementation layer.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within PAY_RTU_SHD:

  • CONSTRAINT_ERROR — Standard Oracle forms/DBMS-style constraint violation handler, used to surface integrity exceptions raised during run type usage maintenance.
  • API_UPDATING — Guards or flags the active API update context, ensuring that overlapping or nested update operations on run type usages are detected and prevented.
  • FIND_DT_UPD_MODES — Determines the valid date-tracked update modes applicable to a run type usage record, supporting effective-date logic.
  • FIND_DT_DEL_MODES — Determines the valid date-tracked delete modes, governing how a usage row is end-dated or removed.
  • UPD_EFFECTIVE_END_DATE — Applies or corrects the EFFECTIVE_END_DATE on a run type usage record, the core operation for maintaining date-tracked validity.
  • LCK — Acquires the row-level lock required before mutation, preventing concurrent modification of the same usage entry.
  • CONVERT_ARGS — Normalizes or translates incoming argument values into the canonical form expected by the underlying DataTracked (DT_API) routines.

Tables Accessed

The package references two tables through APPS synonyms. PAY_RUN_TYPE_USAGES_F is the primary subject table — the "_F" suffix denotes the DataTracked flexfield-style effective-dated base table holding run type usage rows. ALL_CONSTRAINTS is consulted to introspect constraint definitions, supporting the CONSTRAINT_ERROR handling path and the date-mode resolution logic. Additional indirect dependencies include DT_API, HR_API, HR_UTILITY, and FND_MESSAGE, which supply the DataTracked framework, HR validation, general utilities, and message lookup respectively.

Usage Notes

PAY_RTU_SHD is not intended for direct invocation by end users or custom code. It is invoked indirectly by the four dependent packages and by the standard payroll setup forms and concurrent programs that maintain run type usages — typically the Payroll Run Type definition and legislative data group setup flows. Because it manipulates effective-dated rows via DT_API, any custom code that must alter run type usage records should call the supported public API (PAY_RUN_TYPE_USAGES_API) rather than PAY_RTU_SHD, allowing the shadow synchronization machinery of Online Patching to remain consistent across the editions-based file system used in 12.2.2.