Search Results csp_planning




Overview
Explore in AI Chat

Overview

APPS.CSP_PLN_ORG_NAV is a navigational view in Oracle E-Business Suite that supplies the organization-level nodes displayed in the organization navigator for the CSP (Collaborative Supply Planning / Advanced Planning) planning application. Rather than storing data, the view assembles a lightweight, hierarchical result set that a navigator UI control consumes to render the top level of the planning navigator, where each row represents an inventory organization eligible for planning and is labeled with its organization name.

Its role is essentially presentation and integration oriented. The view yields a fixed set of navigator attributes (LABEL, NODE_TYPE, NODE_KEY, ICON_NAME, LEAF_FLAG, PARENT_NODE_TYPE, PARENT_NODE_KEY) that a tree or navigator component in the Oracle EBS forms/HTML framework can interpret directly. Because the driving filter is constrained by the node-type definition, the view is scoped strictly to the CSP_PLANNING root, exposing only organization-type nodes and excluding secondary inventory rows.

Underlying Base Objects

The view is defined over four documented base objects, combined with an outer join and standard organization master joins:

  • CSP_NAV_NODE_TYPES (VIEW) — provides the navigator metadata for the node being rendered, notably NODE_TYPE, ICON_NAME, and ROOT_KEY. The view is filtered so that ROOT_KEY = 'CSP_PLANNING' and NODE_TYPE = 'ORGANIZATION'.
  • CSP_PLANNING_PARAMETERS (SYNONYM) — supplies planning-relevant organization attributes; it is outer-joined (cpp.organization_id(+)) so that organizations lacking a planning-parameter row are still returned, and it filters out secondary inventory organizations via CPP.SECONDARY_INVENTORY IS NULL. It also provides the ORDER BY driver CPP.ORGANIZATION_TYPE.
  • MTL_PARAMETERS (SYNONYM) — the organization parameters table that anchors the inventory organization and supplies the numeric ORGANIZATION_ID used as NODE_KEY.
  • ORG_ORGANIZATION_DEFINITIONS (VIEW) — supplies the ORGANIZATION_NAME, aliased to LABEL.

The documented referent list also cites HR_GENERAL and HR_SECURITY packages, which are the standard Multi-Org / security constructs underlying the organization definition view and ensure that only organizations visible to the current responsibility and operating unit are exposed. Organizations are correlated through ORGANIZATION_ID, and results are ordered by planning organization type and then by the label.

Key Columns

  • LABEL — the display name of the organization (from ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_NAME); this is the text shown on the navigator node.
  • NODE_KEY — the numeric MTL_PARAMETERS.ORGANIZATION_ID that uniquely identifies the node and is used by the UI to resolve the selected organization.
  • NODE_TYPE — set to 'ORGANIZATION', identifying the semantic type of the node.
  • ICON_NAME — the icon the navigator associates with the node, sourced from CSP_NAV_NODE_TYPES.
  • LEAF_FLAG — hard-coded to 'N', indicating that organization nodes are not treated as terminal leaves in the root-level rendering.
  • PARENT_NODE_TYPE — hard-coded to 'ROOT', denoting the parent context.
  • PARENT_NODE_KEY — the NT.ROOT_KEY value ('CSP_PLANNING'), indicating the root node under which each organization is nested.

Common Use Cases and Queries

The primary use is populating the organization selector in the CSP planning navigator. It is also used in diagnostics to verify which organizations are exposed to planning and in integration code that needs to mimic navigator behavior. A basic listing of exposed organizations:

  • SELECT node_key, label FROM apps.csp_pln_org_nav ORDER BY label; — enumerates the planning-visible organizations.
  • SELECT * FROM apps.csp_pln_org_nav WHERE label LIKE :name; — searches for a specific organization displayed in the navigator.
  • Joining NODE_KEY back to other planning tables — for example, comparing the navigator's organization set to CSP_PLANNING_PARAMETERS to detect organizations missing planning parameters, since the outer join intentionally retains them.

Because the view applies outer-join and security semantics, it is a convenient, pre-filtered source that reflects exactly what the planning navigator will render rather than the raw inventory organization master.