Results for “purchase”

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

Overview

SO_DROP_SHIP_SOURCES is an Order Entry (OE) cross-reference table that maintains the operational linkage between sales order lines and the procurement documents raised to fulfil them through a drop-shipment flow. In a drop-ship model, the selling organization never physically receives inventory: the supplier ships directly to the end customer. SO_DROP_SHIP_SOURCES persists the relationship created when Order Management generates requisitions and purchase orders for a drop-shipped sales order line, storing the identifiers of both the originating demand (the sales order line) and the resulting supply (requisition, purchase order, and receipt destination).

The table resides in the OE schema and is classified as VALID in the documented ETRM 12.1.1 / 12.2.2 metadata. With a fully foreign-key-driven structure and no descriptive business attributes beyond control columns, its heuristic Data Vault classification is a link table. It should be modelled as a many-to-many association between the sales order hub (via SO_LINES_ALL) and the purchasing hubs (via PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, and the requisition tables).

Key Information Stored

The table contains 16 documented columns. The surrogate primary key is DROP_SHIP_SOURCE_ID, which uniquely identifies each cross-reference row. The principal business-key and relationship columns are:

• LINE_ID – Foreign key to SO_LINES_ALL; identifies the drop-shipped sales order line that created the demand.
• HEADER_ID – Sales order header identifier for the owning order.
• REQUISITION_HEADER_ID and REQUISITION_LINE_ID – Foreign keys to PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL; the internal requisition raised for the drop-ship line.
• PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID – Foreign keys to PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL; the purchase order, its line, and the shipment line location.
• PO_RELEASE_ID – Foreign key to PO_RELEASES_ALL; populated when the supply is issued as a blanket agreement release.
• ORG_ID – Operating unit (multi-org) identifier controlling the record.
• DESTINATION_ORGANIZATION_ID – The organization designated to receive the drop-shipped shipment.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

Typical applications include tracing a sales order line to its generated PO, reconciling drop-ship supply and demand, and reporting on unfulfilled drop-ship demand. A representative query joins the sales order line to its purchasing documents:

• For each drop-shipped line, retrieve the PO number and supplier by joining SO_DROP_SHIP_SOURCES.PO_HEADER_ID to PO_HEADERS_ALL.
• To confirm whether a requisition or PO already exists for a sales line, query by LINE_ID.
• To trace the full chain, join SO_LINES_ALL → SO_DROP_SHIP_SOURCES → PO_HEADERS_ALL → PO_LINES_ALL → PO_LINE_LOCATIONS_ALL.
• For multi-org reporting, filter by ORG_ID and group by DESTINATION_ORGANIZATION_ID.

Related Objects

• SO_LINES_ALL (via LINE_ID) – The sales order line driving the drop-ship demand.
• PO_REQUISITION_HEADERS_ALL (via REQUISITION_HEADER_ID).
• PO_REQUISITION_LINES_ALL (via REQUISITION_LINE_ID).
• PO_HEADERS_ALL (via PO_HEADER_ID).
• PO_LINES_ALL (via PO_LINE_ID).
• PO_LINE_LOCATIONS_ALL (via LINE_LOCATION_ID).
• PO_RELEASES_ALL (via PO_RELEASE_ID).