Results for “csp_plist_boxitems_nav”

22 results




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

Overview

The CSP_PLIST_BOXITEMS_NAV view is a navigation and reporting object within the Oracle E-Business Suite (EBS) Spares Management (CSP) module. It is owned by the APPS schema and is documented as a VALID view in both ETRM 12.1.1 and ETRM 12.2.2. Its purpose, as stated in the metadata, is to support the "Box to Items flow" — the navigational hierarchy used when drilling from a packing box (box) into the individual packlist items contained within it. This is typically surfaced through the HTML-based user interface of the Field Service / Spares Management application, where a hierarchical tree of nodes is rendered for packlist processing.

Rather than storing data, the view presents a denormalized, navigation-ready projection that combines the description of each packed item (quantity and item concatenated segments) with node-type metadata used to drive tree rendering. Its role is therefore twofold: it participates in the runtime navigation model (via NODE_TYPE, ICON_NAME, LEAF_FLAG, and parent keys) and it can be queried directly for reporting and integration purposes when a flattened list of box-to-item relationships is required.

Underlying Base Objects

Per the documented view text, CSP_PLIST_BOXITEMS_NAV is defined over three referenced base objects:

  • CSP_NAV_NODE_TYPES (VIEW) — supplies node-type metadata and drives the navigation tree structure. The join restricts the query to ROOT_KEY = 'CSP_PACKLIST' and NODE_TYPE = 'PLIST_ITEMS'.
  • CSP_PACKLIST_LINES (SYNONYM) — the transactional source of packlist line data, including quantity packed, item identity, organization, box assignment, and the packlist line identifier.
  • MTL_SYSTEM_ITEMS_VL (VIEW) — the item master view providing the concatenated item segments (CONCATENATED_SEGMENTS) and the inventory item / organization keys used to join to the packlist lines.

The join is established on PLL.INVENTORY_ITEM_ID = MSIV.INVENTORY_ITEM_ID and PLL.ORGANIZATION_ID = MSIV.ORGANIZATION_ID, ensuring items are resolved within the correct inventory organization context.

Key Columns

  • LABEL — a display string formed as QUANTITY_PACKED || ' ' || CONCATENATED_SEGMENTS, giving the packed quantity followed by the item's concatenated segments.
  • NODE_TYPE — the navigation node classification (NT.NODE_TYPE), used to determine how the node is rendered.
  • NODE_KEY — the unique node identifier, populated from PLL.PACKLIST_LINE_ID.
  • ICON_NAME — the icon associated with the node (NT.ICON_NAME).
  • LEAF_FLAG — hard-coded to 'N', indicating these nodes are treated as non-leaf entries in the flow.
  • PARENT_NODE_TYPE — hard-coded to 'PLIST_BOX', identifying the parent box node type.
  • PARENT_NODE_KEY — populated from PLL.BOX_ID, linking each item to its parent box.

Common Use Cases and Queries

Typical uses include verifying which items belong to a given packlist box, auditing packed quantities, and building picklist or box-label reports. Because parent linkage is exposed through PARENT_NODE_KEY, a common query filters by a specific box:

SELECT LABEL, NODE_KEY, ICON_NAME
FROM   APPS.CSP_PLIST_BOXITEMS_NAV
WHERE  PARENT_NODE_KEY = :box_id
ORDER  BY 1;

A broader listing of all box-to-item navigations can be produced simply by selecting LABEL, NODE_KEY, and PARENT_NODE_KEY without a filter. Integration routines that reconstruct the packlist tree can join on NODE_KEY to the corresponding CSP_PACKLIST_LINES record for additional detail such as dates or status. The view is read-only and, being a navigation aid, should be treated as a reporting convenience rather than a transactional source.