Search Results create_attribute_a

Overview

PQH_ATTRIBUTES_BK1 is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under the ETRM documentation standard as an "OTHER" API type. The package is part of the Oracle HRMS (Human Resources Management System) Public Sector/position management framework, and its naming convention (PQH_ prefix) indicates it belongs to the HRMS position and hierarchy module family. The "_BK1" suffix denotes a private, generated "book" package — one of the internal hook layers produced by the Oracle HRMS API Hook Pre-processor. As explicitly recorded in the source header, the code was generated by this tool on 2007/01/03, with an underlying version marker (pqattapi.pkb 115.13). The package's business purpose is to provide the private implementation backbone for creating attribute definitions — configuration metadata that drives dynamic form regions, item names, and column mappings used across HRMS self-service and professional forms.

The package is referenced by one other package, confirming it is not a standalone entry point but a dependency consumed by a higher-level public API wrapper (typically PQH_ATTRIBUTES_API).

Key Procedures and Functions

The ETRM metadata documents two procedures:

• CREATE_ATTRIBUTE_A — The "A" variant of the attribute creation routine. It accepts a full parameter set including an attribute identifier, object version number, and master attribute reference — a signature characteristic of the primary, fully-specified creation path.
• CREATE_ATTRIBUTE_B — The "B" variant, invoked when the attribute identifier is not supplied by the caller, allowing the system to derive or generate it. The parameter list confirms this distinction: CREATE_ATTRIBUTE_B omits the P_ATTRIBUTE_ID and P_OBJECT_VERSION_NUMBER inputs present in the "A" counterpart.

In the documented source, both procedures are stubbed implementations that only bracket execution with hr_utility.set_location calls marking entry and exit. This is consistent with Oracle's hook pre-processor pattern: the generated book package establishes the call contract and instrumentation points, while the substantive business logic is layered in by the API framework or customer extensions during deployment. Neither procedure contains declarative business logic in the shipped excerpt, meaning the packaged behaviour is effectively delegated through the hook mechanism.

Tables Accessed

The ETRM metadata for this package records no direct table references via APPS synonyms. This absence is expected given the stub nature of the generated body: the procedures do not issue DML or queries directly. Where attribute data is ultimately persisted, it occurs in downstream (non-generated) logic or via the base table that the API is designed to manage — conventionally a PQH_ATTRIBUTES-family table holding attribute name, master attribute reference, column name and type, enable flag, display width, effective dates, region and attribute item names, and decode function configuration. The parameters of both procedures map precisely to such columns, indicating the intended insert target. Any table access should therefore be verified against the deployed, non-generated implementation rather than the shipped stub.

Usage Notes

This package should not be called directly from custom code. It is an internal hook layer: the public interface exposed to developers is the corresponding PQH_ATTRIBUTES_API wrapper, which routes calls into these "_BK1" procedures. In Oracle EBS 12.1.1 and 12.2.2, invocation occurs primarily through HRMS attribute configuration forms and through framework-level setup routines that register dynamic region items and column mappings. Because the generated body contains only hr_utility.set_location instrumentation, tracing entries in the HR_UTILITY location stack can be used to confirm whether these hooks fire during a given form or concurrent process. Customizations requiring additional attribute creation behaviour should extend the public API or use its documented extension points rather than modify this generated body, which is subject to regeneration by the API Hook Pre-processor and will be overwritten.