Search Results find_dt_del_modes




Overview
Explore in AI Chat

Overview

PAY_RTU_SHD is a shadow (suffix "_SHD") PL/SQL package in the APPS schema that supports the Payroll Run Type Usages entity within Oracle EBS Human Resources and Payroll. The "_SHD" naming convention denotes a table-handler shadow package generated to accompany the primary API package PAY_RTU_API; it encapsulates the business logic and row-handling operations that the main API delegates to, particularly around effective-dating and record locking. The package operates over the PAY_RUN_TYPE_USAGES_F date-tracked ("_F" suffix) table, which stores the relationships defining how a run type is used—parent/child run type associations, sequences, legislation, and business group ownership.

The package exposes a global record type, g_rec_type, mirroring the structure of PAY_RUN_TYPE_USAGES_F. It includes fields such as parent_run_type_id, child_run_type_id, effective_start_date, effective_end_date, sequence, object_version_number, run_type_usage_id, business_group_id, and legislation_code, together with a global variable g_old_rec used internally to cache prior row state during processing.

Key Procedures and Functions

  • FIND_DT_UPD_MODES — Determines the valid date-track update modes applicable to a record, driving how the API decides between correction, update, and insert behaviors during effective-dated processing.
  • FIND_DT_DEL_MODES — The user-requested object; this procedure determines the valid date-track delete modes for a record, governing whether a deletion is implemented as an end-date update, a full removal, or a ZAP/date-tracked termination. It is central to proper effective-dating behavior when deleting run type usage rows.
  • CONSTRAINT_ERROR — Accepts a constraint name and raises a standardized error, translating low-level Oracle constraint violations into application-level messages.
  • API_UPDATING — Returns a Boolean indicating whether the API is currently performing an update for a given run type usage and object version, supporting concurrency and locking checks.
  • UPD_EFFECTIVE_END_DATE — Updates the effective end date of a run type usage record to support date-track termination logic.
  • LCK — Performs row-level locking and object version validation to prevent concurrent modification.
  • CONVERT_ARGS — Normalizes incoming arguments for downstream processing within the shadow handler.

Tables Accessed

The package references two documented objects via APPS synonyms:

  • PAY_RUN_TYPE_USAGES_F — The primary date-tracked table holding run type usage definitions; both read and write operations occur here for effective dating, deletion, and end-date updates.
  • ALL_CONSTRAINTS — Used by CONSTRAINT_ERROR to resolve constraint names and produce meaningful error diagnostics.

Usage Notes

PAY_RTU_SHD is not intended to be called directly by end users or custom code. It is invoked indirectly through PAY_RTU_API and Payroll run type setup forms, where effective-dated insert, update, and delete operations on run type usages are required. ETRM records show it is referenced by four other packages, consistent with shared shadow-handler reuse across the Run Type API family. When extending or debugging run type usage behavior, developers should inspect FIND_DT_DEL_MODES and FIND_DT_UPD_MODES to understand how deletion and update date-track modes are resolved. Direct calls should be avoided; the supported entry point remains the public API, ensuring constraint handling, locking, and effective-dating logic execute in the correct sequence.