Search Results per_gen_hier_node_types_v




Overview
Explore in AI Chat

Overview

The APPS.PER_GEN_HIER_NODE_TYPES_V view is a Human Resources (PER) product database object in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the user interface for HRMS Calendar node types only. It presents a denormalized, presentation-ready representation of the generic hierarchy node type definitions stored in the PER_GEN_HIER_NODE_TYPES table, enriched with descriptive lookup meanings so that the UI and reports receive human-readable labels rather than raw lookup codes.

The view is particularly relevant to the search term "hierarchy_type". The HIERARCHY_TYPE column identifies the hierarchy category to which a node type definition belongs, and a defining characteristic of this view is its restriction to a single family of hierarchy types: the WHERE clause applies PGT.HIERARCHY_TYPE LIKE 'PER_CAL%'. Consequently, the view exposes only node types associated with HRMS Calendar hierarchies, filtering out all other hierarchy types defined in the base table. This scoping explains the description "Supports UI for HRMS Calendar node types only."

Underlying Base Objects

ETRM documents the referenced base objects as PER_GEN_HIER_NODE_TYPES (accessed through a synonym), HR_LOOKUPS (VIEW), and HR_API (PACKAGE). The view text joins PER_GEN_HIER_NODE_TYPES (aliased PGT) to HR_LOOKUPS twice:

PER_GEN_HIER_NODE_TYPES stores the structural definition of each node type, including identifiers and value set bindings. HR_LOOKUPS supplies the translatable MEANING and DESCRIPTION attributes for the underlying lookup codes. HR_API is referenced as a supporting package in the object's dependency metadata, though the view text itself does not invoke it directly. The join effectively performs a code-to-meaning translation for both the hierarchy type and the child node type.

Key Columns

Common Use Cases and Queries

Typical consumers include HRMS Calendar configuration screens, personalizations, and custom reports that need to display node type labels instead of coded values. Because the view filters to PER_CAL% hierarchy types, queries against it return only calendar-related definitions.

Retrieve all calendar node types with labels:

SELECT HIER_NODE_TYPE_ID,
       HIERARCHY_TYPE,
       HIERARCHY_TYPE_NAME,
       PARENT_NODE_TYPE,
       CHILD_NODE_TYPE,
       CHILD_NODE_NAME,
       CHILD_VALUE_SET
FROM   APPS.PER_GEN_HIER_NODE_TYPES_V
ORDER  BY HIERARCHY_TYPE, PARENT_NODE_TYPE;

Filter by a specific hierarchy type code:

SELECT HIER_NODE_TYPE_ID, CHILD_NODE_TYPE, CHILD_NODE_NAME
FROM   APPS.PER_GEN_HIER_NODE_TYPES_V
WHERE  HIERARCHY_TYPE = :p_hierarchy_type;

Reporting tools and integrations can use these queries to drive LOVs and validations aligned with the value sets bound in CHILD_VALUE_SET, ensuring consistency with the HRMS Calendar UI.