Results for “role_type_cd”

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

Overview

PQH_ROLES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the PQH – Public Sector HR product family. In the 12.1.1 and 12.2.2 releases, this view is a thin, decode-based projection layered over the base table PQH_ROLES. It exists primarily to present role definitions to forms, concurrent programs, and reporting consumers with a human-readable role type label in place of the raw lookup code stored in the underlying table.

The view is exposed with the VALID status in ETRM and is intended for query-only consumption. It retains the native security model of the base table, so multi-tenant filtering by BUSINESS_GROUP_ID is maintained for callers. The view is referenced by Public Sector HR role administration and by any module that needs to resolve a role_id into its descriptive name and type.

Underlying Base Objects

The view text selects from PQH_ROLES, which is exposed in ETRM as a SYNONYM. Every column in the view originates in that table without joins, aggregation, or filtering. The only transformation applied is to the ROLE_TYPE_CD value, which is passed through the HR_GENERAL package function DECODE_LOOKUP against the lookup type 'PQH_ROLE_TYPE'. HR_GENERAL is listed as a referenced PACKAGE base object in the ETRM metadata. Because the composition is a single-table projection with a scalar function call, the view preserves the row cardinality of PQH_ROLES and does not introduce duplicate rows. All audit and concurrency columns, including the OBJECT_VERSION_NUMBER, remain identical to the base table.

Key Columns

• ROLE_ID – Primary key of the underlying PQH_ROLES record; uniquely identifies each role definition.
• BUSINESS_GROUP_ID – Business group owning the role; essential for multi-organization filtering and security.
• ROLE_NAME – User-defined name of the role as entered during setup.
• ROLE_TYPE – Decoded, translated role type produced by DECODE_LOOKUP('PQH_ROLE_TYPE', ROLE_TYPE_CD); this is the principal reason the view exists and the column most often referenced when searching for "role_type".
• ROLE_TYPE_CD – The underlying lookup code stored in PQH_ROLES, retained for exact-match filtering and joins to lookup tables.
• ENABLE_FLAG – Indicates whether the role is currently active and selectable.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE – Standard EBS who-columns used for audit and change tracking.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the framework to detect concurrent updates.

Common Use Cases and Queries

Typical usage resolves role identifiers to descriptive values for reports and interfaces, filters enabled roles within a business group, and joins the decoded ROLE_TYPE to other Public Sector HR data. Because ROLE_TYPE is derived through a package function, filtering on the raw code is preferable for performance.

List all active roles in a business group:

• SELECT role_id, role_name, role_type, role_type_cd FROM apps.pqh_roles_v WHERE business_group_id = :p_bg_id AND enable_flag = 'Y';

Resolve a specific role type, which is the query pattern most commonly associated with the "role_type" search term:

• SELECT role_id, role_name FROM apps.pqh_roles_v WHERE role_type_cd = :p_code ORDER BY role_name;

Audit recently changed role definitions:

• SELECT role_id, role_name, role_type, last_update_date, last_updated_by FROM apps.pqh_roles_v WHERE last_update_date >= :p_from_date;

When ROLE_TYPE is required in a join, expose the view as an inline query and join on role_id to preserve the single-row-per-role guarantee.