Results for “pei_attribute20”

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

Overview

APPS.PQH_ROLE_PEOPLE_V is a Public Sector HR (PQH) view that exposes the assignment of roles to people. It is a denormalized presentation layer built on top of the generic Oracle HR extra information model, specifically the PER_PEOPLE_EXTRA_INFO table where rows with INFORMATION_TYPE = 'PQH_ROLE_USERS' are stored. Rather than require report authors or integration developers to understand the DFF-style PEI_INFORMATIONn storage convention, the view resolves those values into meaningful, named columns such as PERSON_NAME, ROLE_NAME, ROLE_ID and DEFAULT_ROLE.

The view therefore plays a bridging role between the technical PER_PEOPLE_EXTRA_INFO structure and the functional concepts of role membership used by the Public Sector HR role-based security and approver configuration logic. It is one of the more commonly queried objects when administrators need to audit who holds which PQH role.

Underlying Base Objects

The view text joins three objects:

• PER_PEOPLE_EXTRA_INFO (synonym over PER_PEOPLE_EXTRA_INFO) — aliased PEI, the driving table filtered on INFORMATION_TYPE = 'PQH_ROLE_USERS'. The role identifier is stored as a character value in PEI_INFORMATION3 and cast with TO_NUMBER.
• PER_PEOPLE_X (view) — aliased PPX, used to supply the resolved FULL_NAME as PERSON_NAME.
• PQH_ROLES (synonym) — aliased RLS, joined on RLS.ROLE_ID = TO_NUMBER(PEI.PEI_INFORMATION3), providing ROLE_NAME.

Documented dependencies also include the HR_GENERAL, HR_PERSON_NAME and HR_SECURITY packages, consistent with standard HR secured views used for name formatting and security predicates.

Key Columns

• ROW_ID — ROWID of the underlying PER_PEOPLE_EXTRA_INFO row, available for updatable-view identification.
• ROLE_USER_ID — maps the underlying PERSON_EXTRA_INFO_ID, the unique identifier of the role assignment record.
• PERSON_ID / PERSON_NAME — the person identifier and their resolved full name.
• ROLE_ID / ROLE_NAME — the PQH role, derived via DECODE(PEI.INFORMATION_TYPE,'PQH_ROLE_USERS', TO_NUMBER(PEI_INFORMATION3),0) and the PQH_ROLES join.
• DEFAULT_ROLE — sourced from PEI_INFORMATION4, indicating whether the assignment is the user's default role.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO/audit columns.
• PEI_ATTRIBUTE1 through PEI_ATTRIBUTE20 — the 20 descriptive flexfield attribute columns. PEI_ATTRIBUTE20, referenced in many ad hoc queries, is the last of these and is exposed verbatim from the base table.
• PEI_INFORMATION1 through PEI_INFORMATION30 — the informational DFF segments, also passed through verbatim. PEI_INFORMATION3 carries the functional role ID, and PEI_INFORMATION4 the default-role flag.
• INFORMATION_TYPE / PEI_ATTRIBUTE_CATEGORY — the DFF context values driving the row's meaning.

Common Use Cases and Queries

Typical uses include auditing role membership, reporting default role holders, and joining to role-based approval configuration. A basic query listing assignments is:

SELECT person_name, role_name, default_role
FROM   apps.pqh_role_people_v
ORDER  BY person_name;

To target a descriptive flexfield attribute, for example PEI_ATTRIBUTE20:

SELECT person_id, person_name, role_name, pei_attribute20
FROM   apps.pqh_role_people_v
WHERE  pei_attribute20 IS NOT NULL;

Filtering to default roles for a specific person:

SELECT role_name
FROM   apps.pqh_role_people_v
WHERE  person_id = :p_person_id
AND    default_role = 'Y';

Because the view exposes DFF columns directly, it is convenient for BI Publisher reports and interface extracts, but note that it is not a base-table replacement: writes, if any, should be directed to PER_PEOPLE_EXTRA_INFO using the standard HR extra information APIs, not the view.