Search Results pqh_attributes_api




Overview
Explore in AI Chat

Overview

PQH_ATTRIBUTES_API is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a public API within the Oracle Public Sector/HRMS family of modules associated with the PQH (Public Sector HR) product line. The package provides the programmatic interface for managing records in the attributes repository that underpins the configurable, extensible data model used by Oracle's public sector human resources and position management functionality. Attributes in this context represent user-defined or system-defined data elements that are attached to business entities, allowing implementers to extend the base data model without modifying delivered schema objects.

The package encapsulates the standard insert, update, and delete operations against the underlying attribute storage, applying the validation, security, and date-tracking logic required by the EBS business rules layer. Because it is registered as an API, it is the supported entry point for third-party and customer extensions that need to create or maintain attribute definitions and values, insulating callers from direct table-level manipulation and from changes in the physical data model across releases.

Key Procedures and Functions

ETRM documents three procedures on this package:

  • CREATE_ATTRIBUTE — Inserts a new attribute record. This is the entry point for defining a new attribute, including its identifying information and associated metadata, into the attributes repository.
  • UPDATE_ATTRIBUTE — Modifies an existing attribute record. It is used when attribute definitions or their associated descriptive or control information must be changed after initial creation.
  • DELETE_ATTRIBUTE — Removes an attribute record. As with most EBS APIs, deletion is expected to be subject to referential and business validation before the physical or logical removal is performed.

These three procedures constitute the complete documented API surface of the package. Each follows the standard EBS API convention of validating input, performing the DML, and returning status through the customary API error-handling mechanism rather than raising unhandled exceptions to the caller. Parameter lists are not reproduced here; callers should obtain the exact signatures from the package specification in the target environment.

Tables Accessed

Per the ETRM dependency data, PQH_ATTRIBUTES_API references the table PQH_ATTRIBUTES through an APPS synonym. This table is the persistent store for attribute definitions managed by the package. All three procedures operate against this single table: CREATE_ATTRIBUTE inserts rows, UPDATE_ATTRIBUTE modifies existing rows, and DELETE_ATTRIBUTE removes them. No additional documented table dependencies are recorded, which indicates a focused, single-table API with validation logic driven primarily by the HR_API utility layer.

Usage Notes

The package depends on HR_API, the shared Oracle HRMS API utility library that provides common validation, date-effectivity handling, and error-stack management. This dependency confirms that PQH_ATTRIBUTES_API follows standard HRMS API conventions and should be invoked using the same patterns as other HR APIs, including the expectation that callers check the returned status before committing.

Typical invocation points include Oracle Forms-based setup screens, concurrent programs that load or migrate attribute definitions, and custom PL/SQL extensions that need to register attributes as part of a broader integration or configuration routine. Because the package is not referenced by any other delivered package according to the ETRM data, it functions as a leaf-level API rather than a shared internal utility. Custom code should therefore call it directly and treat it as the stable interface, avoiding direct DML against PQH_ATTRIBUTES, which could bypass validation and produce data inconsistent with the delivered application logic.