Search Results per_pyp_rki

Overview

APPS.PER_PYP_RKI is a PL/SQL package body residing in the APPS schema within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Object Metadata records its status as VALID and classifies it under the API classification OTHER, indicating that it is a supporting internal object rather than a public, fully documented application programming interface. The suffix "RKI" follows Oracle's established naming convention for row-level trigger kernel packages, which encapsulate the server-side logic fired by row-level triggers on base tables. In this context, PER_PYP_RKI is associated with the Payroll (PER) product family, which owns the core human resources and payroll tables used throughout Oracle Advanced Benefits, Payroll, and related modules. Its business role is to centralize and enforce the row-level validation, defaulting, and derivation logic that must execute whenever a qualifying insert, update, or delete occurs against the underlying payroll table, keeping that logic in a single maintained PL/SQL unit rather than repeating it inline in trigger bodies.

Key Procedures and Functions

ETRM documentation records exactly one procedure within this package body: AFTER_INSERT. As the name implies, this procedure is designed to run after an insert operation has been performed against the associated base table. Its purpose is to apply any post-insert processing required to keep dependent data consistent, propagate derived values, or invoke related business logic that must follow the successful creation of the row. The package's documented dependency list shows it calls into APPS.HR_UTILITY, a common shared utility package used across HR and payroll modules for standard validation, date, and lookup handling, which confirms that AFTER_INSERT participates in standard row-level processing rather than standalone batch calculation. No parameter signatures are published in the available metadata, so parameter lists are not reproduced here. Documentation notes that PER_PYP_RKI is referenced by one other database package, indicating that AFTER_INSERT, or the package as a whole, is also invoked programmatically from within the payroll layer in addition to its trigger-driven role.

Tables Accessed

The available ETRM metadata does not enumerate specific tables accessed by PER_PYP_RKI through APPS synonyms; the documented dependency section instead identifies the PL/SQL dependencies, namely APPS.HR_UTILITY, its own specification PER_PYP_RKI, and the SYS.STANDARD package. The absence of an explicit table list is typical of row-level trigger kernel packages, because they operate on the row currently being processed, supplied through the trigger context rather than a statically named table. Functionally, the package supports DML against the payroll base table whose insert trigger invokes it. Without a published table list, no additional tables should be assumed; implementers should confirm the specific base table by inspecting the trigger definition that references PER_PYP_RKI in their environment.

Usage Notes

PER_PYP_RKI is not intended for direct invocation by end users or custom code. It is normally executed indirectly through the row-level database trigger attached to the payroll base table, and, per the documented dependency data, it is also called by one dependent package within the APPS schema. The AFTER_INSERT entry point fires automatically when a new row is inserted. Because the API classification is OTHER rather than PUBLIC, Oracle does not warrant this package as a stable integration surface, and signatures may change between patch levels or releases. Customizations should therefore avoid calling PER_PYP_RKI directly and should instead rely on supported APIs such as HR_UTILITY or the relevant payroll public interfaces. When troubleshooting insert-related errors on the associated payroll table, DBAs and developers can review this package body and its dependency on HR_UTILITY to trace validation failures, while treating any direct reference as unsupported.