Search Results per_pem_rku




Overview
Explore in AI Chat

Overview

PER_PEM_RKU is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. In the EBS 12.1.1 and 12.2.2 architectures it forms part of the Oracle Human Resources (PER) product family and specifically belongs to the Payroll/Employee Management "rule" processing infrastructure, where the PEM component prefix denotes Payroll Employee Management rule utilities. The "RKU" suffix (Rule Key Update) identifies the package as a rule-driven key/maintenance handler rather than a user-facing API.

The package is documented as VALID and is classified as OTHER in the ETRM metadata, meaning it is not published as a public, supported API surface. Its functional role is to supply helper logic consumed by rule processing engines and by the PER_PEM_RKU package specification, which is listed as a dependency. In practice the body encapsulates the internal implementation for recalculating or re-keying PEM rule data when an underlying record is modified, a pattern consistent with the AFTER_UPDATE procedure documented in the metadata.

Key Procedures and Functions

The ETRM metadata documents a single procedure in this package body:

  • AFTER_UPDATE — The only documented program unit. Its name and placement indicate that it is a database trigger-style handler executed after an update DML operation against a PEM rule-related table. Its purpose is to propagate post-update processing logic, such as re-evaluating or re-keying dependent rule records, so that the rule definitions remain internally consistent following a change. Because the package is classified as OTHER and no parameter list is published, no public signature is guaranteed for external callers.

The package specification PER_PEM_RKU is referenced as a dependency, confirming that the body implements the contract declared in the specification. No other procedures or functions are enumerated in the documented metadata.

Tables Accessed

The ETRM metadata for PER_PEM_RKU does not enumerate base tables accessed via APPS synonyms; the dependencies section lists only package-level references. The documented dependencies are:

  • HR_API — the Oracle HRMS public API layer, used for standard, validated HR operations.
  • HR_UTILITY — shared HRMS utility routines, typically for date, lookup, and business-group handling.
  • PER_JP_PEM_RULES — Japanese localization rule definitions, indicating that PER_PEM_RKU interfaces with the PEM rules repository used by the localizations.
  • PER_PEM_RKU (the specification) and SYS.STANDARD — the package contract and the PL/SQL built-in package.

Consequently, the tables touched are inferred to be the PEM rules tables underlying PER_JP_PEM_RULES rather than any directly named ETRM table. Readers should not assume a fixed table list; the actual DML is reached indirectly through these dependencies.

Usage Notes

The metadata states that PER_PEM_RKU is not referenced by any database object, while the package body itself is referenced by one other package. This asymmetry is characteristic of rule-engine helper code: the body is called from another PL/SQL package (most plausibly the PER_JP_PEM_RULES or a related PEM rule driver) rather than being wired directly into Oracle Forms or concurrent programs.

Typical invocation therefore occurs indirectly, when an update to PEM rule data is processed and the calling package invokes the AFTER_UPDATE handler to complete post-update maintenance. Because the package is owned by APPS and carries no documented public parameters, it should be treated as an internal implementation object: custom code should not call it directly, and any extension should be performed through the documented HR_API and HR_UTILITY interfaces. Its inclusion in ETRM exists primarily for dependency analysis and impact assessment during patching and upgrade, particularly for the Japanese localization rules that depend on it.