Results for “pqh_template_attributes_v”

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

Overview

APPS.PQH_TEMPLATE_ATTRIBUTES_V is a reporting and integration view in the Oracle E-Business Suite Public Sector HR (PQH) product. It exposes the configuration of attributes assigned to HR templates, joining template definitions, attribute definitions, and transaction-category attribute selections into a single denormalized row set. The view carries a status of VALID in both the 12.1.1 and 12.2.2 releases and is owned by the APPS schema.

Functionally, the view answers the question: "For a given HR template, which attributes are visible, editable, and required, and under which transaction category does that template operate?" This makes it a natural access point for reporting, extensions, and inbound/outbound integration logic that must honor template-driven attribute behavior rather than reading the base configuration tables directly.

Underlying Base Objects

The view is defined over four documented base objects:

• PQH_TEMPLATE_ATTRIBUTES (SYNONYM) — the driving transaction table (alias TAT) holding per-template attribute assignments and the view/edit/required flags.
• PQH_ATTRIBUTES_VL (VIEW) — the attribute value-list view (alias ATT) supplying attribute names, column types, and legislation codes.
• PQH_TXN_CATEGORY_ATTRIBUTES (SYNONYM) — the transaction-category attribute table (alias TCT) providing the SELECT_FLAG.
• PQH_TEMPLATES (SYNONYM) — the template master (alias TTT) linking each template to its transaction category.

The join path is: TAT.ATTRIBUTE_ID = ATT.ATTRIBUTE_ID, TCT.ATTRIBUTE_ID = ATT.ATTRIBUTE_ID, TTT.TEMPLATE_ID = TAT.TEMPLATE_ID, and TCT.TRANSACTION_CATEGORY_ID = TTT.TRANSACTION_CATEGORY_ID. The final join ties the attribute selection to the template's own transaction category, ensuring only attributes valid for that category are returned.

Key Columns

• TEMPLATE_ATTRIBUTE_ID — primary key of the template-attribute assignment row.
• TEMPLATE_ID — foreign key to the parent HR template.
• ATTRIBUTE_ID / ATTRIBUTE_NAME — the attribute identity and its display name.
• VIEW_FLAG — indicates whether the attribute is displayed on the template.
• EDIT_FLAG — indicates whether the attribute is editable; the column most frequently searched for when diagnosing template behavior.
• REQUIRED_FLAG — indicates whether a value must be supplied.
• COLUMN_TYPE — the datatype/column characteristic of the attribute.
• SELECT_FLAG — sourced from PQH_TXN_CATEGORY_ATTRIBUTES, indicating selection eligibility for the category.
• ATTRIBUTE_LEGISLATION_CODE — legislation context for the attribute.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard WHO columns and optimistic locking version.

Common Use Cases and Queries

Typical uses include auditing which fields are editable per template, validating configuration before enabling a transaction category, and feeding external forms that must mirror EBS template rules.

• List all editable attributes for a template:

  SELECT ATTRIBUTE_NAME, VIEW_FLAG, EDIT_FLAG, REQUIRED_FLAG
  FROM   APPS.PQH_TEMPLATE_ATTRIBUTES_V
  WHERE  TEMPLATE_ID = :p_template_id
  AND    EDIT_FLAG = 'Y';

• Identify attributes flagged editable but not required:

  SELECT TEMPLATE_ID, ATTRIBUTE_NAME
  FROM   APPS.PQH_TEMPLATE_ATTRIBUTES_V
  WHERE  EDIT_FLAG = 'Y' AND REQUIRED_FLAG = 'N';

• Cross-reference category selection against template editability:

  SELECT ATTRIBUTE_NAME, SELECT_FLAG, EDIT_FLAG, COLUMN_TYPE
  FROM   APPS.PQH_TEMPLATE_ATTRIBUTES_V
  WHERE  TEMPLATE_ID = :p_template_id
  ORDER  BY ATTRIBUTE_NAME;

• Filter by legislation for regional reporting:

  SELECT ATTRIBUTE_NAME, ATTRIBUTE_LEGISLATION_CODE
  FROM   APPS.PQH_TEMPLATE_ATTRIBUTES_V
  WHERE  ATTRIBUTE_LEGISLATION_CODE = :p_leg_code;

Because the view joins four objects, queries should always be constrained by at least TEMPLATE_ID or ATTRIBUTE_ID to avoid full scans. The view is read-only in practice; DML should target the underlying PQH_TEMPLATE_ATTRIBUTES table instead.