Results for “csp_req_line_details_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CSP_REQ_LINE_DETAILS_V view is a reporting and integration object within the Oracle E-Business Suite CSP – Spares Management module. It consolidates information about requirement details, giving application developers, report writers, and integration specialists a denormalized, read-only window into the requirements captured by the Spares Management (field service / depot repair) functionality. The view resides in the APPS schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. Its principal purpose is to expose the linkage between a requirement line and the source that will satisfy it — an inventory reservation (RES), an internal order (IO), or a purchase requisition (POREQ) — while simultaneously presenting item, quantity, source, and status attributes in a single flattened result set.

Underlying Base Objects

The view is defined over the requirement tables — CSP_REQUIREMENT_HEADERS, CSP_REQUIREMENT_LINES, and CSP_REQ_LINE_DETAILS — joined to source-satisfaction objects. Depending on the SOURCE_TYPE of each requirement detail row, the view outer-joins to MTL_RESERVATIONS (for RES), to OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL (for IO), or to PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL (for POREQ). Item information is supplied through MTL_SYSTEM_ITEMS_B_KFV, with multiple aliases supporting the source item columns. Supporting lookups draw from FND_LOOKUPS, PO_LOOKUP_CODES, and WSH_CARRIER_SHIP_METHODS_V, while MTL_PARAMETERS supplies organization context. Several columns are derived at runtime through the CSP_PICK_UTILS and CS_STD packages as well as FND_GLOBAL.

Key Columns

• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION — identify the required item and its flexfield concatenation.
• REQUIRED_QUANTITY, UOM_CODE, REVISION — the demanded quantity, unit of measure, and revision.
• SOURCE_TYPE — the satisfying source: RES, IO, or POREQ; MEANING and SOURCE_ID accompany it.
• Source item/quantity columns — resolved via DECODE to the reservation item, internal-order item, or requisition item, with matching quantity and organization.
• Source reference columns — reservation ID, order number, or requisition number depending on type.
• ORGANIZATION_CODE, SUBINVENTORY_CODE — sourcing organization and subinventory.
• Status columns — hardcoded RESERVED for reservations, CSP_PICK_UTILS.GET_ORDER_STATUS for internal orders, and PRHA.AUTHORIZATION_STATUS for requisitions.
• LIKELIHOOD, SHIP_COMPLETE_FLAG — planning and fulfillment indicators on the requirement line.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes shortage and availability analysis, demand-versus-sourcing reports, and integration feeds that push requirement detail to external planning or warehouse systems. A common query filters by requirement line and organizes output by source type:

• SELECT requirement_line_id, inventory_item_id, concatenated_segments, required_quantity, source_type, meaning FROM csp_req_line_details_v WHERE requirement_line_id = :line_id;
• SELECT source_type, COUNT(*), SUM(required_quantity) FROM csp_req_line_details_v GROUP BY source_type;

Because the view already resolves source items, quantities, and statuses through inline DECODE logic, report writers avoid writing multiple outer joins themselves. Querying it directly against header/line IDs is the recommended pattern for drill-down reports.