Search Results update_template_attribute

Overview

The APPS.PQH_TEMPLATE_ATTRIBUTES_API package body is a public Oracle E-Business Suite API that manages the association between attributes and templates within the HR/Payroll template framework. Templates in Oracle EBS define reusable layouts and behaviors (for example, for forms, self-service pages, or administrative processes), and each template is composed of one or more template attributes. This package provides the programmatic interface for creating, updating, and deleting those template attribute records, as well as for copying attributes when a template is duplicated. It is classified as an API and belongs to the PQH (Public Sector/HR) product family. The package follows the standard EBS API conventions, including a validation-only mode, an object_version_number for optimistic locking, and user-hook extension points (via the _bk1 before-process hook, as shown in the source excerpt). The header comment (pqtatapi.pkb) indicates this is a long-standing, shipped (noship) component.

Key Procedures and Functions

The documented procedures are:

• CREATE_TEMPLATE_ATTRIBUTE — Inserts a new template attribute record associating an attribute with a template. It accepts the required/optional behavioral flags (required, view, edit), the attribute identifier, the template identifier, and an effective date, and returns the generated template_attribute_id and object_version_number. It supports a validate-only mode using a savepoint, and invokes the before-process user hook prior to performing the insert logic.
• UPDATE_TEMPLATE_ATTRIBUTE — Modifies an existing template attribute record, allowing the behavioral flags (required, view, edit) and related values to be changed. This is the procedure most commonly targeted by searches for update_template_attribute, and is the standard supported mechanism for programmatic updates to the PQH_TEMPLATE_ATTRIBUTES table.
• DELETE_TEMPLATE_ATTRIBUTE — Removes a template attribute association, typically invoked when an attribute is disassociated from a template or when a template is being restructured.
• CREATE_UPDATE_COPIED_ATTRIBUTE — Creates or updates a template attribute as part of a copy operation, used when duplicating an existing template and its attribute set to a new template.

No parameter lists are invented here; parameter signatures and defaults should be confirmed against the package specification in the target release.

Tables Accessed

• PQH_TEMPLATE_ATTRIBUTES — The primary table holding the attribute-to-template association, including the behavioral flags and version/effective-date columns.
• PQH_ATTRIBUTES — Provides the attribute definitions referenced by template attributes.
• PQH_TEMPLATES — Provides the parent template records to which attributes are linked.
• PQH_TXN_CATEGORY_ATTRIBUTES — Referenced for transaction-category-to-attribute relationships tied to the template framework.
• PLITBLM — A standard EBS utility table used by the API infrastructure (commonly for message/lookup or temporary processing).

Usage Notes

This API is typically invoked from Oracle Forms that maintain template and attribute configuration, from concurrent programs that copy or generate templates, or from custom PL/SQL that provisions template attributes during implementation or data migration. Callers should supply an effective_date, honor the p_validate flag for dry-run validation, and always capture and persist the returned object_version_number for subsequent updates to avoid concurrent-modification conflicts. Direct DML against PQH_TEMPLATE_ATTRIBUTES should be avoided in favor of this API, since it enforces validation, optimistic locking, and user-hook extensibility. The API is referenced by no other shipped packages, so it is normally called directly by forms or custom code rather than as an internal dependency.