Results for “default_flag”

50+ results




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

Overview

HRI_CL_PTY_NONPTU_B_V is an APPS-owned read-only view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 database tier. It belongs to the HRI – Human Resources Intelligence product, a legacy analytics module that is marked Obsolete in the ETRM repository. The view exposes a filtered, security-aware list of person types defined in Oracle Human Resources (PER). Its name follows the HRI convention of a "CL_PTY_NONPTU_B" construct, indicating a party (person type) listing restricted to business group scope and excluding personalization user types.

The view is built to bridge Oracle HR person-type definitions with the multi-language translation layer, so that downstream HRI reports, Discoverer workbooks, and integration extracts can present person-type descriptions in the session language while honouring the security profile of the executing user. Because it is a read-only view (the text terminates with WITH READ ONLY), it is intended strictly for querying; no DML is permitted through it.

Underlying Base Objects

The view is defined over two synonyms that resolve to the PER base tables, plus one HR security package. The documented referenced base objects are:

The join is an equi-join on PPT.PERSON_TYPE_ID = PPTT.PERSON_TYPE_ID, filtered to the session language via USERENV('LANG') and to active person types via ACTIVE_FLAG = 'Y'. The business group predicate uses NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, PPT.BUSINESS_GROUP_ID), meaning that when no security profile business group is resolved, all business groups are returned.

Key Columns

  • USER_PERSON_TYPE – the translated, user-facing name of the person type, sourced from PER_PERSON_TYPES_TL in the session language.
  • DEFAULT_FLAG – indicates whether the person type is the default for its business group ('Y'/'N').
  • SYSTEM_PERSON_TYPE – the seeded system-level identifier for the person type, identifying standard Oracle-delivered classifications versus user-defined ones.
  • PERSON_TYPE_ID – the unique primary key linking to PER_PERSON_TYPES and to related HR tables.
  • BUSINESS_GROUP_ID – the business group that owns the person type, used for multi-org and security filtering.

Common Use Cases and Queries

Typical uses include populating LOVs on HRI report parameters, validating person-type values in extracts, and reconciling translated person-type names across languages. Because the view already applies security and active-flag filters, it is convenient for self-service and analytics queries.

List all available person types for the current user:

  • SELECT USER_PERSON_TYPE, SYSTEM_PERSON_TYPE, PERSON_TYPE_ID
  • FROM APPS.HRI_CL_PTY_NONPTU_B_V
  • ORDER BY USER_PERSON_TYPE;

Identify the default person type per business group:

  • SELECT BUSINESS_GROUP_ID, USER_PERSON_TYPE
  • FROM APPS.HRI_CL_PTY_NONPTU_B_V
  • WHERE DEFAULT_FLAG = 'Y';

Join to other HR objects (for example, PER_ALL_PEOPLE_F) using PERSON_TYPE_ID to attribute employees to their person-type classification. As HRI is obsolete, new development should target the underlying PER_PERSON_TYPES and PER_PERSON_TYPES_TL tables directly, but the view remains valid for existing HRI artifacts in both 12.1.1 and 12.2.2.