Search Results after_update




Overview
Explore in AI Chat

Overview

HXC_TKS_RKU is a PL/SQL package in the APPS schema that forms part of the Oracle Time and Labor (HXC) timecard and timekeeper processing infrastructure. The "RKU" suffix follows the Oracle E-Business Suite naming convention for row-level "Row Knowledge Update" style handler packages that are generated to support the shadow/table-handler pattern used throughout the HXC schema. These packages encapsulate the procedural logic that fires after a row-level operation (insert, update, or delete) occurs against a corresponding base table. In practice, HXC_TKS_RKU provides the after-update logic for the timekeeper submission data structure. It belongs to the family of auto-generated handler packages that Oracle produces from its table definitions and business-event triggers. Its primary business purpose is to allow extensions, validations, or downstream propagation to run after a time-related submission record changes, without forcing application code to embed that logic directly in the base table or form.

Key Procedures and Functions

The ETRM metadata documents a single procedure: AFTER_UPDATE.

  • AFTER_UPDATE — The post-update handler for the parent entity this package shadows. Its role is to execute whatever processing must occur once an update has been committed to the underlying record. Because the package is a generated row-knowledge update handler, the procedure is intended to be invoked by the framework rather than called directly by application code. It carries the identifying context for the specific record that changed so that the handler can act on, validate, or synchronize dependent data. The documented signature references a submission identifier and a resource identifier (with an "old" variant of the resource), indicating the handler tracks the previous and current values of the resource attribute so that changes can be detected and reacted to. As with all these handlers, the AFTER_UPDATE body is auto-generated and should be treated as Oracle-owned.

Tables Accessed

The ETRM metadata records no tables referenced through APPS synonyms for this package, which is consistent with its nature as a thin, generated handler. The underlying data it operates against is the Time and Labor submission/timekeeping record set, referenced by the submission and resource keys passed into AFTER_UPDATE. The procedure does not perform broad queries or cross-module reads; any data manipulation it carries out is confined to the parent record context, updating derived or shadow values as needed. Because the referenced-tables list is empty in the documented metadata, integrators should assume that the transaction context is provided by the calling table handler rather than by direct table access within this package.

Usage Notes

HXC_TKS_RKU is an internal, Oracle-owned package. It is generated automatically and is not intended to be called from custom forms, concurrent programs, or user-written PL/SQL. Oracle's documented position is that the bodies of these handler packages may be regenerated when patches or upgrades are applied, so any customer modification would be overwritten and is unsupported.

  • Invoked indirectly by the HXC table-handler framework when an update occurs to the associated timekeeping submission record.
  • Executed within the same transaction as the triggering update, so errors raised here roll back the originating change.
  • Referenced by zero other packages per the ETRM metadata, confirming it is a leaf dependency rather than a shared utility.
  • Not exposed to end users; there is no form, menu, or concurrent program that calls it directly.
  • Customizers needing to extend post-update behavior should use supported APIs or personalization, not edits to HXC_TKS_RKU.

For diagnostics, DBAs may trace execution of this package when investigating timecard update timing or validation failures, but changes should be pursued through Oracle Support and supported extension points only.