Results for “csp_not_pltypes_nav”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, CSP_NOT_PLTYPES_NAV is a documented APPS-owned view registered under the CSP (Spares Management) product family. Its stated purpose is to drive the Parts Loop to Notification Types navigational flow — the mechanism that presents a technician with the list of notification types applicable to a given parts loop when building or processing a field service notification. The view carries a VALID status in the ETRM object registry, confirming it is a supported dictionary object rather than a transient or obsolete artifact.

The name is frequently encountered by implementers searching for the business term csp_notification_types, because the view's driving lookup type is literally CSP_NOTIFICATION_TYPES in FND_LOOKUPS. The view therefore sits at the intersection of three concerns: the seeded lookup vocabulary, the CSP navigation node registry, and the parts-loop entity. It is a presentation-layer construct — it holds no data of its own and exists solely to join these three sources into a navigation-ready result set. Because it is read-only and inexpensive, it is safe to query directly from reports, concurrent programs, or integration extracts without write-lock considerations.

Underlying Base Objects

The ETRM metadata documents four referenced objects, all resolved in the APPS schema:

• CSP_NAV_NODE_TYPES (VIEW) — supplies the navigation node typing, filtering on ROOT_KEY = 'CSP_NOTIF' and NODE_TYPE = 'NOTIF_TYPES'.
• CSP_PARTS_LOOPS_B (SYNONYM) — the base parts-loop entity, contributing PARTS_LOOP_ID and the join predicate.
• FND_LOOKUPS (VIEW) — the standard lookup view, restricted here to LOOKUP_TYPE = 'CSP_NOTIFICATION_TYPES'.
• FND_GLOBAL (PACKAGE) — referenced for session context such as responsibility, user, and application identifiers used during node evaluation.

The result set is ordered by the first column (the lookup MEANING), giving alphabetic presentation of notification types without further application-side sorting.

Key Columns

The view exposes eight columns, several of which are literal or concatenated constructions rather than physical columns:

• LABEL — derived from FL.MEANING; the user-visible name of the notification type.
• NODE_TYPE — from NT.NODE_TYPE; identifies the node classification, fixed to NOTIF_TYPES by the filter.
• NODE_KEY — a quoted, comma-separated concatenation of LOOKUP_CODE and PARTS_LOOP_ID; this composite key uniquely identifies the navigation target.
• ICON_NAME — from NT.ICON_NAME; the icon the UI renders beside the node.
• LEAF_FLAG — hard-coded 'N', indicating these nodes are not terminal.
• PARENT_NODE_TYPE — literal 'NOTIF_PARTS_LOOP', the parent context in the tree.
• PARENT_NODE_KEY — the PARTS_LOOP_ID, linking the node to its owning parts loop.

Common Use Cases and Queries

Typical scenarios include validating that seeded CSP_NOTIFICATION_TYPES lookup codes are reachable for each parts loop, troubleshooting missing or mislabelled notification types in the CSP UI, and extracting the node hierarchy for migration or audit. A representative query lists notification types per loop:

SELECT label, node_key, icon_name, parent_node_key
FROM apps.csp_not_pltypes_nav
WHERE parent_node_key = :parts_loop_id
ORDER BY label;

To reconcile the navigation list against the lookup repository, join back to FND_LOOKUPS on LOOKUP_CODE where LOOKUP_TYPE = 'CSP_NOTIFICATION_TYPES' and compare enabled flags. Because the view already joins all three sources, no additional business logic is required in the consuming query.