Results for “so_line_details”

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

Overview

SO_LINE_DETAILS is a transactional table in the Oracle Order Entry (OE) module, owned by the OE schema. It stores order line schedule details — the split-level fulfillment records that decompose a sales order line into individual scheduled quantities, each carrying its own warehouse, demand class, schedule date, revision, lot, and subinventory instructions. Where SO_LINES_ALL holds the commercial intent of a line (item, ordered quantity, price, customer), SO_LINE_DETAILS records how that quantity is to be sourced, reserved, and shipped.

Because each schedule row links a parent order line to inventory components, bills of material, deliveries, and departures, the table functions as a junction between order management and shipping, inventory reservation, and configured-item explosions. The mined Data Vault classification is link, which is consistent with its structure: the surrogate key identifies each schedule occurrence while a dense set of foreign keys connects order lines to fulfillment, BOM, inventory, and departure entities.

Key Information Stored

The surrogate primary key is LINE_DETAIL_ID, enforced by SO_LINE_DETAILS_PK and mirrored in the unique index SO_LINE_DETAILS_U1. The most significant columns include:

• LINE_ID — foreign key to SO_LINES_ALL; identifies the parent order line.
• INVENTORY_ITEM_ID — the item scheduled on this detail row (may differ from the ordered item for configurations).
• COMPONENT_SEQUENCE_ID — links to BOM_INVENTORY_COMPONENTS and BOM_BILL_OF_MATERIALS for configured or included items.
• QUANTITY — the scheduled quantity for this detail row.
• WAREHOUSE_ID and SUBINVENTORY — sourcing location and subinventory instructions.
• DEMAND_CLASS_CODE — demand class driving reservation and sourcing rules.
• SCHEDULE_DATE and LATEST_ACCEPTABLE_DATE — planning dates governing shipment timing.
• SCHEDULE_STATUS_CODE and RECEIPT_STATUS_CODE — workflow state of the schedule and its receipt.
• REVISION, LOT_NUMBER, CUSTOMER_REQUESTED_LOT_FLAG — inventory control attributes.
• DELIVERY_ID and DEPARTURE_ID — foreign keys to WSH_DELIVERIES and WSH_DEPARTURES.
• CUSTOMER_ITEM_ID — FK to MTL_CUSTOMER_ITEMS, supporting customer-specific item numbering.
• SHIPPABLE_FLAG, TRANSACTABLE_FLAG, RESERVABLE_FLAG, RELEASED_FLAG — eligibility flags controlling downstream processing.

Columns such as QUANTITY_SVRID, WAREHOUSE_SVRID, and DATE_SVRID support Oracle's value-set/descriptive flexfield mechanics. The five WHO columns track audit history, and ATTRIBUTE1–15 provide descriptive flexfield capacity.

Common Use Cases and Queries

Typical reporting includes schedule-level shipment detail, reservation and sourcing analysis, and delivery-planning reconciliation. A common pattern joins schedules to their parent lines:

• Retrieve all schedule rows for an order: SELECT d.line_detail_id, d.line_id, d.inventory_item_id, d.quantity, d.schedule_date FROM oe.so_line_details d, oe.so_lines_all l WHERE d.line_id = l.line_id AND l.header_id = :header_id.
• Trace delivery assignments: join DELIVERY_ID to WSH_DELIVERIES to report shipped quantities per delivery.
• Analyze configuration components by joining COMPONENT_SEQUENCE_ID to BOM_INVENTORY_COMPONENTS.
• Reconcile reservations by filtering on RESERVABLE_FLAG and SCHEDULE_STATUS_CODE.

Related Objects

The most significant related objects, per documented foreign keys, are:

• SO_LINES_ALL — parent order line, joined on LINE_ID.
• BOM_INVENTORY_COMPONENTS — component definition, joined on COMPONENT_SEQUENCE_ID.
• BOM_BILL_OF_MOMATERIALS (BOM_BILL_OF_MATERIALS) — bill header, joined on COMPONENT_SEQUENCE_ID.
• WSH_DELIVERIES — delivery header, joined on DELIVERY_ID.
• WSH_DEPARTURES — departure record, joined on DEPARTURE_ID and SO_LINE_DETAILS_DEPARTURE_ID.
• MTL_CUSTOMER_ITEMS — customer item cross-reference, joined on CUSTOMER_ITEM_ID.

These relationships establish SO_LINE_DETAILS as the operational bridge between order capture and fulfillment execution.