Results for “csp_plist_itmslno_nav”

20 results




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

Overview

The CSP_PLIST_ITMSLNO_NAV view is an APPS-owned, VALID database object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the CSP product family, Spares Management, and is documented in the ETRM as a "View for packlist items to Serial/Lot flow." Functionally, the view exists to supply the navigational data that drives the serial and lot drill-down within the Spares Management packlist hierarchy. Each row represents a single serial-numbered or lot-controlled item contained on a packlist line, formatted so that it can be consumed directly by a tree or hierarchical navigation region.

The view does not store data. It is a read-only projection assembled from packlist serial/lot records and the CSP navigation node type definitions. Because it is a view and not a table, it carries no segments, indexes, or storage, and it cannot be updated through DML. Its principal role is in reporting and integration: presenting a flattened, label-ready representation of serial/lot packlist contents for inquiry screens, concurrent reports, and any interface that walks the CSP packlist navigation tree.

Underlying Base Objects

The documented metadata identifies three referenced base objects:

The joins are constrained by organization and packlist line: PSL.ORGANIZATION_ID = PLL.ORGANIZATION_ID and PSL.PACKLIST_LINE_ID = PLL.PACKLIST_LINE_ID. A cross-reference to CSP_NAV_NODE_TYPES is required for NT.ROOT_KEY = 'CSP_PACKLIST' and NT.NODE_TYPE = 'PLIST_SERIAL_LOT', ensuring the view returns only node types valid for packlist serial/lot navigation. Results are ordered by the first column (the concatenated label).

Key Columns

  • LABEL — A concatenated display value built as PSL.SERIAL_NUMBER || DECODE(LOT_NUMBER, NULL, ' ', '/' || LOT_NUMBER). For serial-only items the label is the serial number followed by a space; for serial/lot combinations the serial is joined to the lot with a forward slash.
  • NODE_TYPE — Derived from NT.NODE_TYPE, denoting the navigation type, resolved to PLIST_SERIAL_LOT.
  • NODE_KEY — The unique row identifier from PSL.PACKLIST_SERIAL_LOT_ID.
  • ICON_NAME — The icon associated with the node type, taken from NT.ICON_NAME.
  • LEAF_FLAG — Hard-coded as 'Y', marking every row as a terminal (leaf) node in the navigation tree. This is the attribute most directly associated with the user search term "leaf_flag."
  • PARENT_NODE_TYPE — Hard-coded as 'PLIST_ITEMS', identifying the parent level in the packlist hierarchy.
  • PACKLIST_LINE_ID — The packlist line identifier from PLL.PACKLIST_LINE_ID, linking the leaf back to its packlist line and, transitively, to the packlist header.
  • PARENT_NODE_KEY — Listed among the view columns; in the documented view text the parent key is not explicitly projected, so consumers should reference PACKLIST_LINE_ID when they require a parent linkage.

Common Use Cases and Queries

Typical uses include auditing which serial/lot items belong to a given packlist, validating that every packlist line has resolvable serial/lot leaf nodes, and powering tree navigation in Spares Management inquiry or returns processing. A representative query retrieving the nodes belonging to a specific packlist is:

SELECT label, node_type, node_key, icon_name, leaf_flag, parent_node_type, packlist_line_id
FROM csp_plist_itmslno_nav
WHERE packlist_line_id = :packlist_line_id;

To isolate leaf nodes and confirm the traversal depth of the serial/lot level:

SELECT node_key, label
FROM csp_plist_itmslno_nav
WHERE leaf_flag = 'Y'
AND node_type = 'PLIST_SERIAL_LOT';

To count serial/lot items per packlist line:

SELECT packlist_line_id, COUNT(*) serial_lot_count
FROM csp_plist_itmslno_nav
GROUP BY packlist_line_id;

Because the view is read-only and joined across organization and line, queries should always filter on PACKLIST_LINE_ID or an organization-scoped identifier to avoid scanning the full packlist population.