Search Results csp_picklist_lines_v1




Overview

The CSP_PICKLIST_LINES_V1 view is a reporting construct within the Oracle E-Business Suite Spares Management (CSP) module, owned by the APPS schema. It presents consolidated picklist line information by joining picklist header and line data with move order, inventory item, subinventory, and incident (service request) details. The view exposes only rows associated with active picklists — specifically those whose header status is 3 (picked/released) and whose move order lines carry a line status of 3 or 7 — and filters to lines where the outstanding packed quantity is greater than zero. Because it resolves the outstanding quantity dynamically through a call to the CSP_PACKLIST_PVT package, the view reflects current packing state rather than a static snapshot.

In Oracle EBS 12.1.1 and 12.2.2, this view serves as a convenient reporting and integration surface for spare parts fulfillment. It is not a base table; it is a derived, read-only object intended for queries in custom reports, OAF/ADF extensions, and outbound integrations that require a joined view of picklist activity tied to field service incidents.

Underlying Base Objects

The view is defined over ten referenced objects. The core picklist data originates from the CSP_PICKLIST_HEADERS and CSP_PICKLIST_LINES synonyms (base tables in the CSP schema). Item and revision attributes are resolved through MTL_SYSTEM_ITEMS_VL, while move order context is drawn from MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES. Subinventory validation joins CSP_SEC_INVENTORIES. Move order header and line relationships are supplied by CSP_MOVEORDER_HEADERS and CSP_MOVEORDER_LINES, which are matched to the transaction request lines. Service request linkage is provided by CS_INCIDENTS_ALL, joined via an outer join (CIA.INCIDENT_ID(+) = CML.INCIDENT_ID), so picklist lines without an associated incident are retained. The outstanding packed quantity is computed by calling the CSP_PACKLIST_PVT package function PACKED_QUANTITY.

Key Columns

Common Use Cases and Queries

Typical scenarios include open picklist monitoring, shortages-and-shipping reporting, and linking spares activity to service requests. The following query lists outstanding picklist lines for a given request number:

SELECT picklist_number, item_number, revision,
       quantity_picked, uom_code,
       service_request_number, date_required
FROM   apps.csp_picklist_lines_v1
WHERE  request_number = :p_request_number
ORDER  BY picklist_line_number;

To report all service requests with pending picklist activity:

SELECT service_request_number, picklist_number,
       item_number, quantity_picked, subinventory_code
FROM   apps.csp_picklist_lines_v1
WHERE  service_request_number IS NOT NULL;

Filters on PICKLIST_HEADER_ID, ORGANIZATION_ID, or DATE_REQUIRED are also common for operational dashboards and backlog analysis, since the view already restricts results to active, unpacked lines.