Search Results csp_requirement_headers

Overview

The CSP_REQUIREMENT_HEADERS table is a core data object within the Oracle E-Business Suite Spares Management (CSP) module, specifically in versions 12.1.1 and 12.2.2. It functions as the primary transactional table for storing high-level information about parts requirements. A requirement in this context typically represents a formal request for spare parts, often generated from service tasks or field service operations. The table serves as the master header record, establishing the context and key attributes for the detailed line items, which are stored in the related CSP_REQUIREMENT_LINES table. Its existence is central to the spares fulfillment process, linking service activities to inventory and procurement operations.

Key Information Stored

The table's primary identifier is the REQUIREMENT_HEADER_ID, which is enforced by the CSP_REQUIREMENT_HEADERS_PK primary key. This unique key is referenced by all associated requirement lines. Critical foreign key relationships define the table's integration with other EBS modules. The TASK_ID column links the requirement to a specific service task in the JTF_TASKS_B table, while TASK_ASSIGNMENT_ID can provide a more granular link to a task assignment via JTF_TASK_ASSIGNMENTS. The DESTINATION_ORGANIZATION_ID column, linked to MTL_PARAMETERS, specifies the inventory organization to which the requested parts are destined, anchoring the requirement within the enterprise's supply chain structure. While the provided metadata does not list all columns, typical header information would include creation dates, status, priority, and requester details.

Common Use Cases and Queries

This table is pivotal for reporting and process flows related to service parts demand. Common operational scenarios include generating reports on all open parts requirements for a specific service organization, analyzing requirement volume linked to particular task types, and tracing the fulfillment status of parts requested for high-priority tasks. A fundamental query pattern involves joining the header to its lines and related task information:

• Identifying requirements for a specific task: SELECT * FROM csp_requirement_headers WHERE task_id = <task_id>;
• Reporting on requirements by destination organization: SELECT crh.requirement_header_id, crh.creation_date, mtl.organization_code FROM csp_requirement_headers crh, mtl_parameters mtl WHERE crh.destination_organization_id = mtl.organization_id ORDER BY mtl.organization_code, crh.creation_date;
• Tracing the complete requirement record: SELECT crh.*, crl.* FROM csp_requirement_headers crh, csp_requirement_lines crl WHERE crh.requirement_header_id = crl.requirement_header_id;

Related Objects

The CSP_REQUIREMENT_HEADERS table is a central node in a network of related EBS objects. Its most direct relationship is with the CSP_REQUIREMENT_LINES table, which holds the specific part numbers and quantities for each header via the foreign key CSP_REQUIREMENT_LINES.REQUIREMENT_HEADER_ID. For contextual and integration data, it references tables from other modules: JTF_TASKS_B for the source service task, JTF_TASK_ASSIGNMENTS for assignment details, and MTL_PARAMETERS to identify the destination inventory organization. This structure ensures that parts requirements are fully integrated with Oracle Service, Inventory, and Procurement functionalities.