Skip to content
EBS Reference

WIP_MOVE_TRANSACTIONS

Schema: WIPtransactionPer inventory org

The shop-floor move ledger — one row per move event with from/to operation and intraoperation step, quantity, and date; the throughput, cycle-time, and WIP-aging fact behind the operation counters

Notes

There is NO transaction-type column here — a move's direction derives from the from/to step pair, and completions into inventory surface in the material transaction ledger. Repetitive apportionment lives in a separate allocations table; LINE_ID is the repetitive-line pointer on this one.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_IDSurrogate key of the move eventNUMBER
Primary-key field
2ORGANIZATION_IDInventory organizationNUMBER
3WIP_ENTITY_IDThe job or schedule movedNUMBER
4PRIMARY_ITEM_IDThe assembly itemNUMBER
5LINE_IDThe repetitive production line, for repetitive moves — there is no repetitive-schedule column on this ledgerNUMBER
6TRANSACTION_DATEWhen the move happened — the primary analysis dateDATE
The table's primary analysis date — a real DATE column, no conversion needed
7GROUP_IDTransaction group the move was processed inNUMBER
8ACCT_PERIOD_IDAccounting period of the moveNUMBER
9FM_OPERATION_SEQ_NUMThe operation moved FROMNUMBER
10FM_INTRAOPERATION_STEP_TYPEThe step moved from (queue, run, to-move, reject, scrap) — numeric, undecoded; direction derives from the from/to pairNUMBER
11TO_OPERATION_SEQ_NUMThe operation moved TONUMBER
12TO_INTRAOPERATION_STEP_TYPEThe step moved toNUMBER
13FM_DEPARTMENT_IDDepartment moved fromNUMBER
14TO_DEPARTMENT_IDDepartment moved toNUMBER
15TRANSACTION_QUANTITYQuantity moved, in the transaction UOMNUMBER
16TRANSACTION_UOMUOM of the moveVARCHAR2
17PRIMARY_QUANTITYQuantity in the assembly's primary UOM — the column to aggregateNUMBER
18REASON_IDReason code on the moveNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WIP_MOVE_TRANSACTIONS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <TRANSACTION_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : WIP_MOVE_TRANSACTIONS — The shop-floor move ledger — one row per move event with from/to operation and intraoperation step, quantity, and date; the throughput, cycle-time, and WIP-aging fact behind the operation counters
-- Purpose: Column-selected read of WIP_MOVE_TRANSACTIONS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + TRANSACTION_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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.TRANSACTION_ID AS "Surrogate key of the move event",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.WIP_ENTITY_ID AS "The job or schedule moved",
  t.PRIMARY_ITEM_ID AS "The assembly item",
  t.LINE_ID AS "The repetitive production line, for repetitive moves — there is no repetitive-schedule column on this ledger",
  t.TRANSACTION_DATE AS "When the move happened — the primary analysis date",
  t.GROUP_ID AS "Transaction group the move was processed in",
  t.ACCT_PERIOD_ID AS "Accounting period of the move",
  t.FM_OPERATION_SEQ_NUM AS "The operation moved FROM",
  t.FM_INTRAOPERATION_STEP_TYPE AS "The step moved from (queue, run, to-move, reject, scrap) — numeric, undecoded; direction derives from the from/to pair",
  t.TO_OPERATION_SEQ_NUM AS "The operation moved TO",
  t.TO_INTRAOPERATION_STEP_TYPE AS "The step moved to",
  t.FM_DEPARTMENT_ID AS "Department moved from",
  t.TO_DEPARTMENT_ID AS "Department moved to",
  t.TRANSACTION_QUANTITY AS "Quantity moved, in the transaction UOM",
  t.TRANSACTION_UOM AS "UOM of the move",
  t.PRIMARY_QUANTITY AS "Quantity in the assembly's primary UOM — the column to aggregate",
  t.REASON_ID AS "Reason code on the move"
FROM <catalog>.<schema>.WIP_MOVE_TRANSACTIONS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.TRANSACTION_ID = <TRANSACTION_ID>
  -- AND t.TRANSACTION_DATE >= DATE '<DATE_FROM>'
  -- AND t.TRANSACTION_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.TRANSACTION_ID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • WIP_MOVE_TRANSACTIONSWIP_DISCRETE_JOBSforeign key · N:1
    ON WIP_MOVE_TRANSACTIONS.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID AND WIP_MOVE_TRANSACTIONS.ORGANIZATION_ID = WIP_DISCRETE_JOBS.ORGANIZATION_ID

Browse more Work in Process tables

More Work in Process tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.