Search Results create_update_copied_attribute




Overview
Explore in AI Chat

Overview

APPS.PQH_RFT_SHD is a shared package body in the Oracle E-Business Suite HRMS/Enterprise Performance Management schema. Within the PQH (Public Sector/Position and Grade) module family, the "RFT" component addresses Reference Templates, and PQH_RFT_SHD provides the shared, low-level utility code used by the reference template API layer. The package operates against the reference template tables — PQH_REF_TEMPLATES, PQH_REF_TEMPLATES_S, and their related attribute, template, and attribute translation tables — which define the reusable templates that drive spreadsheets, requisition formats, and position or performance document generation.

The package is classified as ETRM API type "OTHER," meaning it is an internal service component rather than a public business API. It supplies the plumbing — error handling, locking, row conversion, and seed data loading — on which the public reference template APIs depend. Five other packages reference it, confirming its role as a foundational shared library rather than an entry point invoked directly by end users.

Key Procedures and Functions

  • CONSTRAINT_ERROR — Centralizes exception translation for constraint violations raised against the reference template tables. It maps Oracle constraint names (for example PQH_REF_TEMPLATES_PK, PQH_REF_TEMPLATES_UK, and the foreign keys PQH_REF_TEMPLATES_FK1 and FK2) to user-facing Oracle HRMS error messages via HR_UTILITY.SET_MESSAGE and RAISE_ERROR, so that callers receive meaningful diagnostics instead of raw ORA- error codes.
  • LCK — The locking routine used to serialize concurrent modifications to reference template rows. It corresponds to the standard TCA/HRMS row-locking pattern that prevents lost updates when multiple sessions edit the same template definition.
  • API_UPDATING — Determine whether a template record is currently being processed by an API, allowing callers to enforce update consistency and audit tracking across related child rows.
  • CONVERT_ARGS — Performs argument translation and normalization between the calling interface and the underlying table structures, a common helper in PQH packages that convert internal identifiers into the parameter forms expected by the reference template APIs.
  • LOAD_ROW — Loads a single reference template row and its dependent attribute records, providing the fetch/create primitive used during template replication and seeding.

The procedure list reflects the documented signature set; parameter lists are intentionally omitted here.

Tables Accessed

The package reads and writes PQH_REF_TEMPLATES and its translated counterpart PQH_REF_TEMPLATES_S, the core template definition and its language rows. PQH_ATTRIBUTES and PQH_TEMPLATE_ATTRIBUTES (with PQH_TEMPLATE_ATTRIBUTES_S for translations) hold metadata describing which attributes a template exposes and at what level. PQH_TEMPLATES supplies the parent template records, and PQH_TXN_CATEGORY_ATTRIBUTES ties template attributes to transaction categories. ALL_CONSTRAINTS is queried indirectly through the constraint-error handler's use of constraint name constants. PLITBLM is the PL/SQL index-by table helper package used for array conversion inside CONVERT_ARGS and LOAD_ROW.

Usage Notes

PQH_RFT_SHD is not intended to be called directly from forms or concurrent programs. It is invoked internally by the higher-level reference template APIs and by the five dependent packages during template creation, update, copy, and delete operations. The user search term "create_update_copied_attribute" reflects the attribute-copying logic that depends on this package's row-loading and locking primitives: when a template is copied, LOAD_ROW and CONVERT_ARGS reconstruct the attribute set, LCK protects concurrent edits, and CONSTRAINT_ERROR normalizes any resulting integrity failures. Customizations that must manipulate reference templates should use the supported public APIs, which in turn rely on PQH_RFT_SHD. Because the package is shipped with an OBFUSCATED-wrapped body in 12.2.2, direct modifications are unsupported; developers should inspect it only for debugging and trace purposes.