DOO_FULFILL_LINES_ALL

-- ============================================================
-- Table  : DOO_FULFILL_LINES_ALL — Fulfillment lines — the executable, shippable unit of an order line and the correct analytics grain for order-to-ship reporting, with the quantity lifecycle, schedule/actual dates, fulfillment org, and amounts
-- Purpose: Column-selected read of DOO_FULFILL_LINES_ALL — auto-generated from field metadata
-- Grain  : One row per business unit (ORG_ID) + FULFILL_LINE_ID
-- Caution: Fulfillment lines SPLIT during processing (SPLIT_FROM_FLINE_ID points at the original) — sum quantities knowing splits and cancels add rows
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.FULFILL_LINE_ID AS "Surrogate key of the fulfillment line — the analytics grain",
  t.LINE_ID AS "Parent order line",
  t.HEADER_ID AS "Order header — carried directly, so no two-hop join needed",
  t.ORG_ID AS "The business unit owning the row",
  t.INVENTORY_ITEM_ID AS "Item being fulfilled",
  t.INVENTORY_ORGANIZATION_ID AS "The item-master inventory organization",
  t.FULFILL_ORG_ID AS "The fulfilling (ship-from) organization — a third org concept, distinct from both ORG_ID and the item-master org",
  t.ORDERED_QTY AS "Quantity ordered on this fulfillment line",
  t.ORDERED_UOM AS "UOM of the ordered quantity",
  t.SHIPPED_QTY AS "Quantity shipped",
  t.FULFILLED_QTY AS "Quantity fulfilled",
  t.STATUS_CODE AS "Current fulfillment status",
  t.ON_HOLD AS "Fulfillment line blocked from further processing",
  t.REQUEST_SHIP_DATE AS "The customer's originally requested ship date",
  t.SCHEDULE_SHIP_DATE AS "Currently planned ship date",
  t.ACTUAL_SHIP_DATE AS "Date actually shipped",
  t.EXTENDED_AMOUNT AS "Monetary amount for the fulfillment-line quantity",
  t.SPLIT_FROM_FLINE_ID AS "The original fulfillment line this row split from — splits add rows",
  t.FULFILLMENT_MODE AS "Regular, drop-ship, or back-to-back fulfillment flow"
FROM <catalog>.<schema>.DOO_FULFILL_LINES_ALL t
WHERE
  t.ORG_ID = <business_unit_id>  -- business unit — Fusion _ALL means BU, not the EBS operating unit; see quirks guide #all-means-bu
  -- AND t.FULFILL_LINE_ID = <FULFILL_LINE_ID>
  -- AND t.SCHEDULE_SHIP_DATE >= DATE '<DATE_FROM>'
  -- AND t.SCHEDULE_SHIP_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.FULFILL_LINE_ID;