Search Results csp_required_parts_v

Overview

The CSP_REQUIRED_PARTS_V view is an APPS-owned database object within the CSP (Spares Management) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to present the complete status of spare part requirements — consolidating demand, sourcing, reservation, and fulfillment information into a single queryable interface. The view is documented with STATUS = VALID and is registered in the ETRM repository, making it a supported reporting surface for spares-related analysis.

From an architectural standpoint, the view functions as a union-style presentation layer. Certain columns are populated with literal or reserved values (for example, CATEGORY = 'RESERVED', and numerous TO_NUMBER(NULL) and TO_CHAR(NULL) casts) because the underlying SQL assembles a consistent column shape across different requirement sources. This pattern is typical of EBS views that unify reserved, requisition-sourced, and order-sourced spare part demand into one reporting projection. Because the view is owned by APPS and exposed through standard synonyms, it is accessible to custom concurrent programs, BI Publisher data models, and third-party integration tools without requiring grants beyond the standard APPS reporting privileges.

Underlying Base Objects

The ETRM metadata documents a broad set of referenced base objects. The core requirement entities are CSP_REQUIREMENT_HEADERS, CSP_REQUIREMENT_LINES, and CSP_REQ_LINE_DETAILS, which supply requirement identity, line-level demand, need-by dates, order-by dates, and destination organization context. Reservation and inventory context are sourced from MTL_RESERVATIONS, MTL_PARAMETERS, and MTL_SYSTEM_ITEMS_B_KFV, the latter providing concatenated item segments and descriptions for both demanded and supplied items.

Fulfillment-side data flows from procurement and order management objects: PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_HEADERS, and PO_LINE_LOCATIONS_ALL, together with OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. Freight context is available via ORG_FREIGHT. Service-request linkage is derived from JTF_TASKS_VL, JTF_TASK_ASSIGNMENTS, and JTF_OBJECTS_VL. Lookup decoding uses FND_LOOKUPS and PO_LOOKUP_CODES. Supporting programmatic logic (pick lists, priorities, and standards) is drawn from the packages CSP_PICK_UTILS, CSP_PART_PRIORITIES_V, CS_STD, and FND_GLOBAL, with the latter typically supplying the operating unit or user context in the WHERE clause.

Key Columns

• REQUIREMENT_HEADER_ID / REQUIREMENT_LINE_ID / REQ_LINE_DETAIL_ID — Primary requirement identifiers for joining back to CSP base tables.
• SOURCE_TYPE_MEANING — Decoded lookup indicating the origin of the spare part demand.
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, CATEGORY — The demanded item, its flexfield representation, and category classification.
• SUPPLIED_ITEM_NUMBER, DESCRIPTION — The item ultimately reserved or supplied against the requirement.
• REQUIRED_QUANTITY, ORDERED_QUANTITY, SHIPPING_QUANTITY, SHIPPED_QUANTITY, RECEIVED_QUANTITY, FULFILLED_QUANTITY, CANCELLED_QUANTITY — The quantity lifecycle. Note that SHIPPING_QUANTITY is exposed as TO_NUMBER(NULL) in the documented view text, reflecting the 'RESERVED' source branch where shipping is not applicable.
• ORDER_NUMBER, PO_REQUISITION_NUMBER, DELIVERY_NUMBER, WAYBILL_NUM — Fulfillment document references.
• ORGANIZATION_ID, ORGANIZATION_CODE, DESTINATION_ORGANIZATION_ID, SHIP_TO_LOCATION_ID — Sourcing and destination context.
• NEED_BY_DATE, ORDER_BY_DATE, PROMISE_DATE, SCHEDULE_SHIP_DATE, ACTUAL_SHIPMENT_DATE, ACTUAL_ARRIVAL_DATE — Scheduling milestones.
• SERVICE_REQUEST, INCIDENT_ID, TASK_NUMBER, TASK_ASSIGNMENT_ID, RESOURCE_TYPE — Service and task linkage for maintenance-driven demand.

Common Use Cases and Queries

Typical usage includes open spare part demand reporting, reservation-to-fulfillment tracking, and service request material planning. Because SHIPPING_QUANTITY is null in the reserved branch, filtering on it will exclude reserved requirements; analysts seeking shipped quantities should use SHIPPED_QUANTITY instead.

SELECT requirement_header_id,
       requirement_line_id,
       concatenated_segments,
       required_quantity,
       ordered_quantity,
       shipping_quantity,
       shipped_quantity,
       status_meaning,
       need_by_date
FROM   apps.csp_required_parts_v
WHERE  organization_id = :p_org_id
AND    need_by_date BETWEEN :p_from AND :p_to;

A second common pattern joins the view back to CSP_REQUIREMENT_LINES for status enrichment, or filters by SOURCE_TYPE_MEANING to isolate reservation-sourced versus order-sourced demand. Given the volume of underlying joins, queries should always be constrained by organization and date range to avoid full scans across the CSP, MTL, PO, and OE base objects.