Results for “transaction_category_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PQH_ROLE_TEMPLATES is a transaction-table owned by the HR schema and delivered as part of the PQH – Public Sector HR product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define the template for a transaction category attached to a role. In functional terms, the table acts as a mapping or assignment entity: it binds a specific role (from PQH_ROLES) to a specific transaction category (from PQH_TRANSACTION_CATEGORIES) and, in turn, to a specific template (from PQH_TEMPLATES). This allows an administrator to control which template is presented when a given role initiates a transaction belonging to a particular category.

The table is documented as VALID and contains 11 columns in the 12.2.2 physical schema, confirming structural stability across the 12.1.1 to 12.2.2 upgrade path. Under the heuristic Data Vault classification mined from its foreign-key structure, the object is best modeled as a link. This classification is a modeling suggestion rather than a documented Oracle attribute: the table contains no single descriptive attribute hub, but instead resolves a many-to-many relationship between roles, transaction categories, and templates, which is the defining characteristic of a link construct.

Key Information Stored

The primary key is defined by the unique index PQH_ROLE_TEMPLATES_PK, which covers the surrogate key column ROLE_TEMPLATE_ID. A second unique index, PQH_ROLE_TEMPLATES_UK1, establishes the business-key candidate over the column pair (ROLE_ID, TRANSACTION_CATEGORY_ID). The presence of _UK1 in the user's search term indicates familiarity with this constraint: it enforces that any single role may be associated with a given transaction category only once.

  • ROLE_TEMPLATE_ID — surrogate primary key; system-generated identifier for each assignment row.
  • ROLE_ID — foreign key to PQH_ROLES; identifies the role to which the template mapping applies. Part of the UK1 business key.
  • TRANSACTION_CATEGORY_ID — foreign key to PQH_TRANSACTION_CATEGORIES; identifies the transaction category being templated. Part of the UK1 business key.
  • TEMPLATE_ID — foreign key to PQH_TEMPLATES; identifies the template selected for the role/category combination.
  • ENABLE_FLAG — controls whether the role-template association is active and usable by the application.
  • LAST_UPDATE_DATE — audit column recording the most recent modification timestamp.
  • LAST_UPDATED_BY — audit column recording the user who performed the most recent update.
  • LAST_UPDATE_LOGIN — audit column recording the login session of the last update.
  • CREATED_BY — audit column recording the creating user.
  • CREATION_DATE — audit column recording the creation timestamp.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Object Library to detect concurrent modifications.

Common Use Cases and Queries

Typical operational queries resolve the three-way join to produce readable descriptions of each role-template assignment. A representative pattern joins all three foreign-key targets:

  • Reporting which templates are enabled per role: SELECT r.name, tc.name, t.name FROM pqh_role_templates rt JOIN pqh_roles r ON r.role_id = rt.role_id JOIN pqh_transaction_categories tc ON tc.transaction_category_id = rt.transaction_category_id JOIN pqh_templates t ON t.template_id = rt.template_id WHERE rt.enable_flag = 'Y';
  • Validating business-key uniqueness: querying (ROLE_ID, TRANSACTION_CATEGORY_ID) for duplicate combinations before inserting new assignment rows.
  • Audit and troubleshooting: selecting rows by LAST_UPDATE_DATE or LAST_UPDATED_BY to trace recent configuration changes to role-template mappings.
  • Detecting orphaned or disabled mappings by filtering on ENABLE_FLAG to reconcile configuration drift.

Because the table supports optimistic locking through OBJECT_VERSION_NUMBER, any programmatic DML should retrieve and re-supply this column to avoid concurrent-update failures.

Related Objects

The documented foreign keys identify the principal dependencies of this table:

  • PQH_ROLES — joined via PQH_ROLE_TEMPLATES.ROLE_ID = PQH_ROLES.ROLE_ID; the role dimension of the mapping.
  • PQH_TRANSACTION_CATEGORIES — joined via PQH_ROLE_TEMPLATES.TRANSACTION_CATEGORY_ID = PQH_TRANSACTION_CATEGORIES.TRANSACTION_CATEGORY_ID; the category dimension.
  • PQH_TEMPLATES — joined via PQH_ROLE_TEMPLATES.TEMPLATE_ID = PQH_TEMPLATES.TEMPLATE_ID; the template being assigned.

These three master tables, together with PQH_ROLE_TEMPLATES itself, constitute the complete documented relationship set. The unique indexes PQH_ROLE_TEMPLATES_PK and PQH_ROLE_TEMPLATES_UK1 are the principal dependent schema objects and should be referenced when reasoning about constraint behavior or performing bulk data operations. Oracle's proprietary and confidentiality notices apply to all ETRM documentation describing these objects.