Search Results csp_picklist_headers




Overview
Explore in AI Chat

Overview

The CSP_PICKLIST_HEADERS table is a core data object within the Oracle E-Business Suite Spares Management (CSP) module. It functions as the master or header record for a picklist, which is a fundamental document used to manage the picking and issuing of spare parts from inventory. Each record in this table represents a single, unique picklist transaction, providing the overarching control information for the subsequent line-level detail. Its primary role is to establish the identity and key attributes of a picklist, serving as the parent entity in a one-to-many relationship with the CSP_PICKLIST_LINES table. This structure is critical for maintaining data integrity and supporting operational workflows related to spare parts fulfillment.

Key Information Stored

While the provided metadata does not list specific columns, the structure and naming conventions of Oracle EBS tables allow for informed inference of critical data points. The primary key, PICKLIST_HEADER_ID, is a unique system-generated identifier for the picklist. Other essential columns typically found in such header tables include status fields (e.g., STATUS_CODE), which track the picklist's lifecycle from creation through completion or cancellation. The table likely stores reference information such as the creation date (CREATION_DATE), the identifier of the requesting document or order (e.g., REQUISITION_HEADER_ID), the warehouse or subinventory from which parts are to be picked (ORGANIZATION_ID, SUBINVENTORY_CODE), and the person or process responsible for its generation (CREATED_BY). This header-level data provides the necessary context for all associated line items.

Common Use Cases and Queries

This table is central to reporting and process management within Spares Management. Common operational queries involve retrieving all active picklists for a specific warehouse to prioritize picking tasks, or analyzing picklist completion rates over time. A typical reporting query might join the header to its lines and part master data to generate a comprehensive pick slip. For troubleshooting, one might query headers based on status to identify stalled transactions. A fundamental SQL pattern is joining CSP_PICKLIST_HEADERS to CSP_PICKLIST_LINES to get a complete view of a picklist:

  • SELECT h.PICKLIST_HEADER_ID, h.STATUS_CODE, l.LINE_NUM, l.INVENTORY_ITEM_ID, l.QUANTITY FROM CSP_PICKLIST_HEADERS h, CSP_PICKLIST_LINES l WHERE h.PICKLIST_HEADER_ID = l.PICKLIST_HEADER_ID AND h.STATUS_CODE = 'OPEN';

Related Objects

The CSP_PICKLIST_HEADERS table has a direct and documented relationship with one key child table, as per the provided foreign key metadata. The primary key column PICKLIST_HEADER_ID is referenced by the CSP_PICKLIST_LINES table via its foreign key column of the same name (CSP_PICKLIST_LINES.PICKLIST_HEADER_ID). This establishes that every picklist line must be associated with a valid header record. While not listed in the excerpt, it is architecturally common for this header table to also have foreign key relationships to foundational EBS tables such as HR_ORGANIZATION_UNITS (for the warehouse), MTL_SYSTEM_ITEMS_B (for spare parts, typically via the lines table), and FND_USER (for the creator).