Results for “csp_requirement_lines”

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

Overview

CSP_REQUIREMENT_LINES is a transactional table in the CSP (Spares Management) product schema within Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The table stores parts requirement detail records — the individual line-level demands that make up a spares requirement. Where CSP_REQUIREMENT_HEADERS captures the requirement document itself, CSP_REQUIREMENT_LINES records each item, quantity, source, and reservation associated with that requirement, making it the operational core of spares planning and fulfillment activity.

The object carries 41 documented columns and is defined as VALID in the ETRM repository. Based on the foreign key structure extracted from the metadata, the table functions primarily as a link (junction) entity: it connects requirement headers to inventory items, reservations, order lines, and source organizations. A Data Vault modeling suggestion would therefore classify CSP_REQUIREMENT_LINES as a link table, bridging the requirement hub (CSP_REQUIREMENT_HEADERS) to multiple reference hubs such as inventory items, order lines, and reservation records.

Key Information Stored

The surrogate primary key is REQUIREMENT_LINE_ID, enforced by the CSP_REQUIREMENT_LINES_PK constraint and also backed by the unique index CSP_REQUIREMENT_LINES_U1. This column is the value users search for when tracing an individual requirement line; it is the sole documented business-key candidate and is referenced by dependent detail tables. No natural composite unique key is documented for this table, so REQUIREMENT_LINE_ID is the reliable identifier.

• REQUIREMENT_HEADER_ID — foreign key to CSP_REQUIREMENT_HEADERS; groups the line under its parent requirement.
• INVENTORY_ITEM_ID — the spare part being required.
• REQUIRED_QUANTITY and ORDERED_QUANTITY — demanded versus already-ordered amounts, used for shortage analysis.
• UOM_CODE and REVISION — unit of measure and item revision context.
• SOURCE_ORGANIZATION_ID and SOURCE_SUBINVENTORY — the supplying organization and subinventory, joined to MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES respectively.
• ORDER_LINE_ID — links the requirement to a sales order line in OE_ORDER_LINES_ALL.
• RESERVATION_ID and LOCAL_RESERVATION_ID — both reference MTL_RESERVATIONS, capturing material reservations (global and local).
• ORDER_BY_DATE and ARRIVAL_DATE — planning dates driving procurement and shipping decisions.
• SHIP_COMPLETE_FLAG, LIKELIHOOD, and SHIPPING_METHOD_CODE — fulfillment attributes guiding shipment behavior.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS and supports multi-org / security partitioning.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield columns.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — audit tracking.

Common Use Cases and Queries

Typical reporting scenarios include open spares demand by item, reservation reconciliation, and shortage detection. A common query joins lines to headers and items to summarize outstanding requirements:

• Retrieve a single line by primary key: SELECT * FROM csp.csp_requirement_lines WHERE requirement_line_id = :line_id;
• List all lines for a requirement: SELECT * FROM csp.csp_requirement_lines WHERE requirement_header_id = :header_id;
• Shortage analysis comparing required versus ordered: SELECT inventory_item_id, SUM(required_quantity - NVL(ordered_quantity,0)) FROM csp.csp_requirement_lines GROUP BY inventory_item_id;
• Reservation tracing: join RESERVATION_ID and LOCAL_RESERVATION_ID to MTL_RESERVATIONS to reconcile reserved stock against demand.
• Source allocation reporting: join SOURCE_ORGANIZATION_ID to MTL_PARAMETERS and SOURCE_SUBINVENTORY to MTL_SECONDARY_INVENTORIES to identify where each requirement will be sourced.

These patterns support spares planners, order management analysts, and supply chain reporting in identifying fulfillment gaps and reservation accuracy.

Related Objects

The most significant related objects, based on documented foreign keys, are:

• CSP_REQUIREMENT_HEADERS — joined via REQUIREMENT_HEADER_ID; provides the parent requirement context.
• CSP_REQ_LINE_DETAILS — the main child table referencing this table via REQUIREMENT_LINE_ID; stores further line detail.
• MTL_RESERVATIONS — joined via RESERVATION_ID and LOCAL_RESERVATION_ID.
• OE_ORDER_LINES_ALL — joined via ORDER_LINE_ID.
• MTL_PARAMETERS — joined via SOURCE_ORGANIZATION_ID.
• MTL_SECONDARY_INVENTORIES — joined via SOURCE_SUBINVENTORY and SOURCE_ORGANIZATION_ID.
• MTL_SYSTEM_ITEMS_B — implicit reference for INVENTORY_ITEM_ID item validation.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for security partitioning.