Search Results service_request_number




Overview
Explore in AI Chat

Overview

CSP_PICKLIST_LINES_V1 is a supplementary view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CSP (Customer Service/Field Service) module family and exposes picklist line information in a flattened, report-friendly format. The view is classified as a "supplementary view used to simplify forms coding" — Oracle explicitly warns that it should not be queried or altered directly for data maintenance purposes, and that its definition may change dramatically across minor or major releases. It is registered under the FND Design Data path CSP.CSP_PICKLIST_LINES_V1 and is currently VALID. In practice, the view serves reporting, integration, and diagnostic scenarios where picklist lines must be joined with move order, incident/service request, item, and inventory context without navigating the normalized base tables individually.

Underlying Base Objects

The view is constructed over a mix of CSP, MTL, and CS objects. The documented base dependencies are CSP_MOVEORDER_HEADERS, CSP_MOVEORDER_LINES, CSP_PACKLIST_PVT (a package, indicating that some derived columns are computed at runtime), CSP_PICKLIST_HEADERS, CSP_PICKLIST_LINES, CSP_SEC_INVENTORIES, CS_INCIDENTS_ALL, MTL_SYSTEM_ITEMS_VL, MTL_TXN_REQUEST_HEADERS, and MTL_TXN_REQUEST_LINES. The picklist header and line synonyms provide the core record set, while the move order and transaction request objects supply request numbers and line identifiers. MTL_SYSTEM_ITEMS_VL supplies item descriptions and revisions. CS_INCIDENTS_ALL provides the service request linkage exposed through the SERVICE_REQUEST_NUMBER column, and CSP_SEC_INVENTORIES resolves subinventory and organization detail. Because CSP_PACKLIST_PVT is referenced, some columns are populated through packaged logic rather than a simple table join.

Key Columns

The column set reflects a mixed operational and logistics context. Picklist identification is carried by PICKLIST_NUMBER, PICKLIST_HEADER_ID, PICKLIST_LINE_NUMBER, and PICKLIST_LINE_ID. Item context comes from ITEM_NUMBER, INVENTORY_ITEM_ID, ITEM_DESCRIPTION, REVISION, and UOM_CODE. The move order relationship is exposed through REQUEST_NUMBER, HEADER_ID, LINE_NUMBER, and LINE_ID (described as the move order line identifier). Inventory placement is captured by ORGANIZATION_ID, SUBINVENTORY_CODE, and LOCATION_ID, while logistics data appears in CARRIER, SHIPMENT_METHOD, and DATE_REQUIRED. Two columns are especially relevant to service-oriented searches: SERVICE_REQUEST_NUMBER (VARCHAR2(64)), which carries the service request number derived from CS_INCIDENTS_ALL, and PARTY_SITE_ID, which identifies the customer party site associated with the picklist line. QUANTITY_PICKED records the fulfilled quantity.

Common Use Cases and Queries

The most common scenario leading to this view is a search for "service_request_number" — tracing a field service request to the picklist lines and move orders that fulfilled it. The view eliminates the need to manually join picklist lines to incidents and move order tables. Representative queries include:

  • Locating all picklist lines for a given service request: SELECT picklist_number, item_number, quantity_picked, request_number FROM apps.csp_picklist_lines_v1 WHERE service_request_number = :request_num;
  • Reporting picked quantities by organization and subinventory for logistics reconciliation.
  • Extracting carrier and shipment method detail for outbound service parts shipping.

Because the view is documented as unstable and non-updatable, it should be used strictly for read-only reporting and integration extracts. Direct DML is unsupported, and any dependency on specific column behaviour should be revalidated after patching in 12.1.1 or 12.2.2.