Search Results pay_evc_rki

Overview

PAY_EVC_RKI is a database package owned by the APPS schema in Oracle E-Business Suite. The suffix "RKI" follows the Oracle EBS naming convention for a row-level trigger handler package that implements the "Row Koordination Insert" (after-insert) processing logic associated with a database trigger. In this role, the package encapsulates the business logic that must execute after a new row is inserted into the underlying payroll table through the corresponding *_INS trigger handler.

At a functional level, PAY_EVC_RKI belongs to the Oracle Payroll module, as indicated by the "PAY_" prefix. Packages of this class act as the procedural back end for the row-level database triggers that Oracle EBS generates to maintain derived columns, populate shadow or mirror columns, apply validation, and ensure consistency of the base payroll data model. ETRM classifies the package under the generic API classification "OTHER," confirming it is an internal, system-managed object rather than a public or customer-facing API. In Oracle EBS 12.1.1 and 12.2.2, the object remains VALID and carries the same structural definition in both releases.

Key Procedures and Functions

The ETRM metadata documents a single procedure within this package:

• AFTER_INSERT — The sole documented procedure, invoked by the associated insert trigger on the base payroll table immediately after a new row is created. Consistent with the RKI naming convention, AFTER_INSERT performs the post-insert processing required to keep dependent data synchronized. Such logic typically includes populating mirrored or denormalized columns, deriving values that depend on the newly generated primary key, and enforcing any referential or business rules that can only be evaluated once the row exists. No parameter list is documented, and the procedure is not intended for direct invocation by external callers.

Tables Accessed

The ETRM excerpt does not enumerate the base tables referenced through APPS synonyms; the dependency listing records only SYS.STANDARD among the referenced schema objects, which is the standard PL/SQL package specification dependency present in virtually every compiled package and reflects no application table access. Consequently, the specific payroll tables read or written by AFTER_INSERT are not disclosed in the documented metadata. By design, a row-level "insert" trigger handler package operates on the triggering table itself — deriving and writing column values on the newly inserted row — and may reference related payroll lookup or control tables. The absence of an explicit table list indicates that the object relies on the APPS synonym layer and that the authoritative table inventory is contained within the package body rather than the specification metadata.

Usage Notes

PAY_EVC_RKI is not a standalone API and is never called directly by forms, concurrent programs, or custom code. It is invoked exclusively through the row-level insert trigger associated with its base payroll table; the ETRM dependency record confirms PAY_EVC_RKI is referenced by PAY_EVC_INS, the companion insert trigger handler package, as well as by itself. This dependency pattern is characteristic of Oracle-generated trigger infrastructure, in which the *_INS package drives the trigger and the *_RKI package supplies the after-insert business logic.

Customers and integrators should treat PAY_EVC_RKI as an internal, unsupported object. Customizations should be implemented through the documented payroll APIs rather than by modifying this package or its trigger, because direct changes can be overwritten during patching or upgrade. The package exists identically in Oracle EBS 12.1.1 and 12.2.2, and its behavior is exercised only as a byproduct of inserting rows into the underlying payroll table.