Search Results per_pem_rki




Overview
Explore in AI Chat

Overview

PER_PEM_RKI is a database trigger implementation package owned by the APPS schema in Oracle E-Business Suite. The suffix "RKI" identifies it as a row-level insert trigger body — a generated package whose single procedure encapsulates the PL/SQL logic fired after insert on a base table. In the Oracle EBS 12.1.1 and 12.2.2 releases, PER_PEM_RKI forms part of the Human Resources (PER) module's generated trigger infrastructure, specifically supporting the PER_PEM entity — the "payroll event messaging" or payroll event management base table that records payroll-related event activities processed by the payroll engine.

The package is not a business API in the conventional sense. It contains no user-callable entry points and is not documented as part of the public PL/SQL API surface. Rather, it is a technical artifact generated by Oracle's Forms/trigger-generation utilities to externalize row-level trigger logic from the base table definition. The ETRM classification as "OTHER" reflects this internal, generated nature. Its validity status (VALID) indicates the compiled package body resides in the database dictionary and is operational.

Key Procedures and Functions

The documented package metadata lists exactly one procedure:

  • AFTER_INSERT — This procedure encapsulates the logic executed following the insertion of a row into the underlying PER_PEM base table. Its role is to enforce referential or business rules that must run post-insert, such as populating derived columns, recording audit information, or cascading updates to dependent tables. Consistent with Oracle's generated RKI pattern, the procedure operates on the row-level trigger context (:NEW/:OLD values), and is invoked automatically by the table's AFTER INSERT trigger rather than by application code.

No parameter lists are exposed or documented for this procedure; invoking it directly from custom code is neither intended nor supported.

Tables Accessed

The ETRM dependency information documents no directly referenced application tables via APPS synonyms for this package. Dependencies are limited to SYS and STANDARD — the PL/SQL standard package providing the DBMS_STANDARD primitives required for trigger execution. This is characteristic of a generated trigger package whose data manipulation is confined to the base table itself and any logic embedded through the :NEW and :OLD row-level bind variables rather than through explicit SELECT/INSERT statements against other application tables. Any table interaction is therefore implicit in the owning table's definition rather than enumerated as a package dependency.

Usage Notes

PER_PEM_RKI is referenced by one other package, PER_PEM_INS, which performs the actual insert operations against the base table and thereby triggers the AFTER_INSERT procedure. The package also appears as a self-reference in the dependency report, reflecting the typical generated header/body pairing.

In practice, this package is never invoked directly. It is activated implicitly whenever a row is inserted into the PER_PEM table — whether through concurrent payroll processes, Oracle Forms-based HR/payroll screens, or supported APIs such as PER_PEM_INS. Customizations should never modify this generated package, as re-generation or patching will overwrite its contents. Developers diagnosing payroll event insert behavior should trace calls through PER_PEM_INS into PER_PEM_RKI.AFTER_INSERT to understand post-insert side effects.