Results for “pqh_attributes”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQH_ATTRIBUTES is a table owned by the HR schema in Oracle E-Business Suite, classified under the PQH (Public Sector HR) product family. As documented in ETRM for releases 12.1.1 and 12.2.2, it stores information about attributes that are used within transactions. In practice, the table functions as the attribute registry for the Public Sector HR transactional framework: each row defines a configurable attribute that can be attached to documents, templates, transaction categories, and routing definitions, and that participates in the routing and history mechanics of the product.

From a Data Vault modeling perspective, the mined FK structure classifies PQH_ATTRIBUTES as hub-leaning. It carries its own surrogate identity and is referenced by multiple dependent tables, while also holding a self-referencing relationship and an outbound reference to PQH_TABLE_ROUTE. That combination suggests a durable business entity (hub) that anchors several satellites and links rather than a pure transaction or link record.

Key Information Stored

The documented physical schema in 12.2.2 exposes 21 columns. The columns of greatest functional significance are:

  • ATTRIBUTE_ID — the surrogate primary key, enforced by PQH_ATTRIBUTES_PK (documented as ATTRIBUTE_ID, ZD_EDITION_NAME in the physical schema).
  • ATTRIBUTE_NAME — the descriptive name of the attribute.
  • MASTER_ATTRIBUTE_ID — a self-referencing foreign key back to PQH_ATTRIBUTES, used to relate a derived attribute to its master definition.
  • MASTER_TABLE_ROUTE_ID — a foreign key to PQH_TABLE_ROUTE, binding the attribute to the routing definition of its source table. This is the column referenced by the search term "master_table_route_id".
  • COLUMN_NAME and KEY_COLUMN_NAME — identify the underlying database column (and key column) that the attribute maps to.
  • COLUMN_TYPE and WIDTH — the data type and display width of the attribute value.
  • ENABLE_FLAG — controls whether the attribute is active for use in transactions.
  • REFRESH_COL_NAME — indicates the column used when the attribute value must be refreshed.
  • LEGISLATION_CODE — the legislative context that qualifies the attribute.
  • ATTRIBUTE_ITEMNAME and REGION_ITEMNAME — the item names used to render the attribute in its functional region.
  • DECODE_FUNCTION_NAME — the name of the decode routine applied to translate stored values.

Besides PQH_ATTRIBUTES_PK, a unique index PQH_ATTRIBUTES_UK is documented as covering MASTER_TABLE_ROUTE_ID, COLUMN_NAME, and LEGISLATION_CODE, which constitutes the business-key candidate for this entity. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the ZD_EDITION_NAME editioning column are also present.

Common Use Cases and Queries

Typical usage involves resolving which attributes are enabled for a given table route, and reporting on attribute configuration by legislation. A representative query joins the table to its routing parent:

  • SELECT a.attribute_id, a.attribute_name, a.column_name, a.enable_flag, r.table_route_id FROM hr.pqh_attributes a, hr.pqh_table_route r WHERE a.master_table_route_id = r.table_route_id AND a.legislation_code = :legislation_code AND a.enable_flag = 'Y';
  • Self-referencing lookups to find master/derived attribute pairs: SELECT child.attribute_id, child.attribute_name, parent.attribute_name FROM hr.pqh_attributes child, hr.pqh_attributes parent WHERE child.master_attribute_id = parent.attribute_id;
  • Join to PQH_TXN_CATEGORY_ATTRIBUTES to enumerate which attributes are available to a given transaction category.

Reporting use cases include auditing enabled attribute coverage per legislation, validating that every referenced COLUMN_NAME exists in the routed table, and tracing attribute-to-document usage through PQH_DOCUMENT_ATTRIBUTES_F.

Related Objects

The following objects are the most significant dependencies, based on documented FK relationships:

  • PQH_TABLE_ROUTE — referenced by PQH_ATTRIBUTES.MASTER_TABLE_ROUTE_ID.
  • PQH_ATTRIBUTES (self) — referenced by MASTER_ATTRIBUTE_ID.
  • PQH_ATTRIBUTE_RANGES — references PQH_ATTRIBUTES.ATTRIBUTE_ID.
  • PQH_DOCUMENT_ATTRIBUTES_F — references PQH_ATTRIBUTES.ATTRIBUTE_ID.
  • PQH_ROUTING_HIST_ATTRIBS — references PQH_ATTRIBUTES.ATTRIBUTE_ID for routing history.
  • PQH_TEMPLATE_ATTRIBUTES — references PQH_ATTRIBUTES.ATTRIBUTE_ID for template configuration.
  • PQH_TXN_CATEGORY_ATTRIBUTES — references PQH_ATTRIBUTES.ATTRIBUTE_ID for transaction category setup.