Search Results parent_node_key




Overview
Explore in AI Chat

Overview

CSP_PLN_ORG_NAV is a foundational navigation view in the Oracle E-Business Suite Spares Management (CSP) module, owned by the APPS schema and documented as VALID in ETRM for releases 12.1.1 and 12.2.2. It supplies the organization-level nodes displayed within the CSP Planning navigation hierarchy, exposing each inventory organization as a selectable node beneath the CSP_PLANNING root. The view answers the tree-building question of which organizations are available and how they should be labeled, ordered, and parented for the planning user interface and for integration consumers that traverse the same hierarchy.

Because it emits a uniform set of tree attributes — LABEL, NODE_KEY, PARENT_NODE_KEY, NODE_TYPE, LEAF_FLAG — the view can be consumed directly by generic tree-rendering code, by descriptive flexfield or folder-style personalizations, and by custom concurrent programs that must reproduce the standard navigation. The presence of NODE_KEY ($NODE_KEY) in the column list makes it the primary correlation column for joining a navigation node back to the underlying organization record.

Underlying Base Objects

The documented view text joins four sources. CSP_NAV_NODE_TYPES supplies the static node metadata (NODE_TYPE, ICON_NAME, ROOT_KEY) and is itself a view. MTL_PARAMETERS provides the organization identifier, which is projected as NODE_KEY. ORG_ORGANIZATION_DEFINITIONS supplies the display name used as LABEL. CSP_PLANNING_PARAMETERS is outer-joined (CPP.ORGANIZATION_ID(+) with CPP.SECONDARY_INVENTORY IS NULL) so that organizations lacking a planning parameter row are still returned, and its ORGANIZATION_TYPE drives the ORDER BY. ETRM additionally lists HR_GENERAL and HR_SECURITY as referenced base objects, indicating that the security model for the underlying organization definitions is applied through those packages; users therefore see only organizations their responsibility and HR security profile permit.

Key Columns

  • LABEL — the organization name from ORG_ORGANIZATION_DEFINITIONS, used as the visible tree text.
  • NODE_TYPE — literal 'ORGANIZATION' from CSP_NAV_NODE_TYPES; distinguishes this node class from other CSP navigation entries.
  • NODE_KEY — the organization ID from MTL_PARAMETERS; the unique identifier for the node and the join key to inventory and planning data.
  • ICON_NAME — the icon assigned to the node type for UI rendering.
  • LEAF_FLAG — hard-coded 'N', indicating organization nodes may expand further.
  • PARENT_NODE_TYPE — hard-coded 'ROOT'; PARENT_NODE_KEY — the ROOT_KEY value 'CSP_PLANNING', anchoring every row to the planning root.

Common Use Cases and Queries

Typical uses include validating which organizations appear in the planning navigator, driving custom tree regions, and resolving a NODE_KEY back to an organization for downstream spares queries.

  • List all planning organizations with their keys: SELECT label, node_key, node_type FROM csp_pln_org_nav ORDER BY 1;
  • Resolve a node key to inventory context: SELECT n.label, mp.organization_code FROM csp_pln_org_nav n, mtl_parameters mp WHERE n.node_key = mp.organization_id;
  • Filter planning-enabled organizations: SELECT n.node_key, n.label FROM csp_pln_org_nav n, csp_planning_parameters cpp WHERE n.node_key = cpp.organization_id;
  • Confirm the root binding for integration: SELECT DISTINCT parent_node_key, parent_node_type FROM csp_pln_org_nav;

Because security is enforced through HR_GENERAL and HR_SECURITY, results vary by responsibility; queries used in concurrent programs should therefore be executed under the intended operating unit and security profile.