Search Results pqp_ert_rkd

Overview

PQP_ERT_RKD is an Oracle Application Object Library (APPS) PL/SQL package that forms part of the Enterprise Resource Knowledge (ERKD) framework within the E-Business Suite Enterprise Transaction Resource Manager (ETRM) subsystem. Its name follows the ETRM convention in which the _RKD suffix designates a knowledg(e)-base or rule-definition handler that is associated with a specific ERTM entity, in this instance the ERT object family. The package is a private utility package: it is not exposed as a public application programming interface and is invoked exclusively by other objects in the same family.

The business purpose of PQP_ERT_RKD is to manage the lifecycle of ERT-related rule or knowledge records, particularly at the point where such records are removed. It provides the deletion-time logic required to keep dependent data consistent when an ERT definition or its associated knowledge record is purged from the system. In Oracle EBS 12.1.1 and 12.2.2 the object is registered in the APPS schema with a VALID status, confirming it is a supported, compiled component of the standard product code.

Key Procedures and Functions

ETRM documentation for release 12.2.2 records a single callable procedure in the package specification:

• AFTER_DELETE — A post-deletion handler. Its purpose is to execute the follow-up processing that must occur once an ERT knowledge record has been physically deleted. This includes any cascading maintenance of dependent ERT data and invalidation or cleanup of related cached or staging records. As an AFTER DELETE style hook, it is intended to be called by the parent transaction after the primary delete has been committed within the same logical unit of work.

The package also exposes a package body containing additional private logic. No parameter signatures are published in the ETRM record; the documented metadata identifies the procedure by name and role only. The procedure is classified as OTHER in the API classification, indicating it is an internal handler rather than a business-facing API.

Tables Accessed

The documented metadata for PQP_ERT_RKD does not enumerate referenced tables through APPS synonyms; no table-level dependencies are listed in the ETRM registry entry. This is consistent with the object's role as a thin event handler whose data manipulation is performed either through unqualified references resolved at runtime or through invocations of sibling ERT packages. Where the package does touch data, it operates on the ERT entity tables owned by the PQP schema and exposed as APPS synonyms, performing the delete-time maintenance associated with the ERT knowledge base. Implementers should verify actual table usage by inspecting the package body in the target instance before extending it.

Usage Notes

PQP_ERT_RKD is referenced by one other documented package, PQP_ERT_DEL, which is the ERT deletion driver. The typical invocation pattern is therefore indirect: when the deletion process in PQP_ERT_DEL removes an ERT record, it calls PQP_ERT_RKD.AFTER_DELETE to perform post-delete work. The recursive self-reference also recorded in the dependency list reflects internal calls within the package body.

Because the package is an internal ETRM component, it should not be called directly from custom forms, concurrent programs, or integration code. Customizations that need to participate in ERT deletion should hook into the supported ERT interfaces rather than calling AFTER_DELETE directly, since the procedure assumes it is running inside the parent deletion transaction and relies on that transaction's context. During upgrades from 12.1.1 to 12.2.2 the package is recompiled as part of the ETRM patch set; any invalid status after patching should be resolved by recompiling the APPS.PQP_ERT_RKD package specification and body.