Search Results after_delete




Overview
Explore in AI Chat

Overview

APPS.HR_QSN_RKD is a generated PL/SQL package body belonging to the Oracle E-Business Suite Human Resources (HR) module, specifically the Oracle Questionnaires (QSN) schema family. The "RKD" suffix identifies it as a row-level knowledge/documentation stub that mirrors the database trigger and table handling conventions used throughout the HR product line. Its documented role is to expose the post-delete processing hook for the questionnaire template entity, allowing the application to perform any housekeeping required after a questionnaire template row has been removed from the underlying table. In the Oracle EBS 12.1.1 and 12.2.2 codebases, this package is delivered as part of the standard HR Questionnaires installation and is not intended for direct customer modification. The header comment ($Header: hrqsnrhi.pkb 120.6.12020000.2) confirms it was last rebuilt during the 12.2.2 release cycle.

Key Procedures and Functions

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

  • AFTER_DELETE — the row-level post-delete handler. It is invoked after a questionnaire template record has been deleted from the controlling table. Consistent with the Oracle Forms / Table API pattern, it receives the old (pre-delete) column values as input parameters, including the questionnaire template identifier, the template name, the availability flag, the business group identifier, and the object version number. In the delivered 12.2.2 source, the body is intentionally empty apart from hr_utility.set_location tracing calls at entry and exit, meaning no additional business logic is executed by default. Customers extending questionnaire template deletion behaviour would add their custom logic inside this procedure, but such changes are unsupported and would be overwritten by patching.

Tables Accessed

The ETRM metadata does not list any base tables or APPS synonyms referenced by HR_QSN_RKD. This is consistent with the delivered implementation: the AFTER_DELETE body contains no DML, no SELECT, and no calls to other business packages, performing only diagnostic tracing via HR_UTILITY. The procedure is therefore best understood as a structural placeholder rather than an active data-access routine. Its parameters correspond to columns of the questionnaire template table (HR_QUESTIONNAIRE_TEMPLATES and related questionnaire entities), but the package itself neither reads nor writes those tables.

Usage Notes

HR_QSN_RKD is not invoked directly by end users. It is called by the generated Table API / trigger framework associated with the questionnaire template entity — typically from a BEFORE/AFTER DELETE trigger or from the corresponding HR_QSN_API delete routine — during standard Oracle Forms-based questionnaire maintenance. The metadata records zero referencing packages, indicating that no other delivered PL/SQL unit depends on it, so it is effectively a leaf node in the HR Questionnaires call graph. Because the procedure is a no-op in the shipped code, DBAs and developers investigating the "after_delete" search term should treat it as the documented extension point for questionnaire template deletion rather than as a source of functional behaviour. Any customisation should be applied through supported personalisation or a wrapper package, not by editing the delivered body, since hr_qsn_rkd.pkb is a versioned, proprietary Oracle file subject to replacement during patching to 12.2.2 and beyond.