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:
- PER_PERSON_TYPES (SYNONYM) – the base definition table holding
PERSON_TYPE_ID,SYSTEM_PERSON_TYPE,DEFAULT_FLAG,ACTIVE_FLAG, andBUSINESS_GROUP_ID. Aliased as PPT in the view text. - PER_PERSON_TYPES_TL (SYNONYM) – the translation table holding language-specific
USER_PERSON_TYPEvalues keyed byPERSON_TYPE_IDandLANGUAGE. Aliased as PPTT. - HR_BIS (PACKAGE) – the HR business intelligence security package. The view calls
HR_BIS.GET_SEC_PROFILE_BG_IDto constrain results to the business group(s) the user is secured to.
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_IDFROM APPS.HRI_CL_PTY_NONPTU_B_VORDER BY USER_PERSON_TYPE;
Identify the default person type per business group:
SELECT BUSINESS_GROUP_ID, USER_PERSON_TYPEFROM APPS.HRI_CL_PTY_NONPTU_B_VWHERE 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.
-
View: HRI_CL_PTY_NONPTU_B_V 12.2.2
APPS.HRI_CL_PTY_NONPTU_B_V·↳ HR_BIS·↳ PER_PERSON_TYPES·↳ PER_PERSON_TYPES_TL·Explore HRI module →
-
View: HRI_CL_PTY_NONPTU_B_V 12.1.1
APPS.HRI_CL_PTY_NONPTU_B_V·↳ HR_BIS·↳ PER_PERSON_TYPES·↳ PER_PERSON_TYPES_TL·Explore HRI module →
-
Specific formats valid for one or more locations.
-
Table: EGO_CAT_GRP_TEMPLATES 12.2.2
Table contains the Catalog Category to template associations
-
This table contains phases and all possible statuses in this phase
-
Definition of a collection of Styles
-
Implementation-defined available distribution rules for each project type
-
This table stores information of User Defined Account Hierarchy
-
Entity to capture the relation between Units and Grading Schemas
-
Stores change category relationships
-
Entity to capture the Grading Schemas related to the Unit Sections.
-
View: HZ_STYLE_FORMATS_VL 12.1.1
Translation view for name and address formatting style formats
APPS.HZ_STYLE_FORMATS_VL·↳ HZ_STYLE_FORMATS_B·↳ HZ_STYLE_FORMATS_TL·Explore AR module →
-
Specific formats valid for one or more locations.
-
View: HRI_CL_ASGSTYP_BX_V 12.1.1
APPS.HRI_CL_ASGSTYP_BX_V·↳ HR_BIS·↳ HR_GENERAL·↳ PER_ASSIGNMENT_STATUS_TYPES·Explore HRI module →
-
View: IGS_FI_HIER_ACCOUNTS_V 12.1.1
information of User Defined Account Hierarchy
APPS.IGS_FI_HIER_ACCOUNTS_V·↳ IGS_FI_HIER_ACCOUNTS·Explore IGS module →
-
Stores change category relationships
-
Stores the sub types associated with a transaction type. This is the base table for the detail block of the Define Budget Transaction Types form.
-
View: IGS_GE_REF_CD_V 12.1.1
-
Definition of a collection of Styles
-
Used to support user-interface.
APPS.PER_STARTUP_PERSON_TYPES·↳ PER_STARTUP_PERSON_TYPES_TL·Explore PER module →
-
Used to support user-interface.
APPS.PER_STARTUP_PERSON_TYPES·↳ PER_STARTUP_PERSON_TYPES_TL·Explore PER module →
-
View: BNE_STYLESHEETS_VL 12.2.2
BNE_STYLESHEETS_VL is a standard translation view over the BNE_STYLESHEETS entity.
APPS.BNE_STYLESHEETS_VL·↳ BNE_STYLESHEETS_B·↳ BNE_STYLESHEETS_TL·Explore BNE module →
-
Predefined list of translated person types.
-
View: AMS_USER_STATUSES_V 12.1.1
This view returns information on User statuses defined for System Statuses for Marketing Objects(Event,Registration,Campaign etc..)
APPS.AMS_USER_STATUSES_V·↳ AMS_LOOKUPS·↳ AMS_USER_STATUSES_VL·↳ FND_LOOKUP_TYPES_VL·Explore AMS module →
-
This Table is used to store Reason Codes
-
Source transaction types - Applicable IB Transaction Types association.
-
User amendments to predefined assignment status types.
-
The XLA_EVT_CLASS_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the event class level.
-
- Retrofitted
-
User amendments to predefined assignment status types.
-
- Retrofitted
-
Source transaction types - Applicable IB Transaction Types association.
-
View: IGS_PS_USEC_GRD_SCHM_V 12.1.1
APPS.IGS_PS_USEC_GRD_SCHM_V·↳ IGS_AS_GRD_SCHEMA·↳ IGS_PS_USEC_GRD_SCHM·Explore IGS module →
-
Contract billing method assignments view
APPS.OKE_K_BILLING_METHODS_V·↳ OKE_BILLING_METHODS_VL·↳ OKE_K_BILLING_METHODS·Explore OKE module →
-
Used to support status types table and translated table
APPS.PER_ASSIGNMENT_STATUS_TYPES_V·↳ PER_ASSIGNMENT_STATUS_TYPES·↳ PER_ASSIGNMENT_STATUS_TYPES_TL·Explore PER module →
-
Predefined and user defined assignment status types.
-
Business view template from which the flexfield view is generated.
APPS.OTFV_ENROLLMENT_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·Explore OTA module →
-
View: JTF_FM_FILE_V 12.2.2
view referring to the JTF_FM_FILE table
-
View: JTF_FM_PRINTER_V 12.2.2
view referring to the JTF_FM_PRINTER table.
-
This table is used to store Report List information
-
This table is used to store Report List information
-
View: JTF_FM_PRINTER_V 12.1.1
view referring to the JTF_FM_PRINTER table.
-
Stores User status information
-
Life Event Plan in Program Enrollment Date Track View
APPS.BEN_LER_CHG_PLIP_ENRT_D·↳ BEN_LER_CHG_PLIP_ENRT_F·↳ BEN_LER_F·↳ BEN_PLIP_F·Explore BEN module →
-
Transaction Routing Information
-
View: EGO_REPORT_LISTS_VL 12.1.1
This view is a multi-lingual view on the Report Lists tables
APPS.EGO_REPORT_LISTS_VL·↳ EGO_REPORT_LISTS_B·↳ EGO_REPORT_LISTS_TL·Explore EGO module →
-
Stores User status information
-
View: CSI_SRC_TXN_SUB_TYPES 12.1.1
Transaction Sources and the applicable Installed Base transactions.
APPS.CSI_SRC_TXN_SUB_TYPES·↳ CSI_SOURCE_IB_TYPES·↳ CSI_TXN_TYPES·Explore CSI module →
-
Stores information about Fulfillment printers