WIP_MOVE_TRANSACTIONS
Schema: WIPtransactionPer inventory orgThe 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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_ID | Surrogate key of the move event | NUMBER | Key |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 3 | WIP_ENTITY_ID | The job or schedule moved | NUMBER | |
| 4 | PRIMARY_ITEM_ID | The assembly item | NUMBER | |
| 5 | LINE_ID | The repetitive production line, for repetitive moves — there is no repetitive-schedule column on this ledger | NUMBER | |
| 6 | TRANSACTION_DATE | When the move happened — the primary analysis date | DATE | Filter date |
| 7 | GROUP_ID | Transaction group the move was processed in | NUMBER | |
| 8 | ACCT_PERIOD_ID | Accounting period of the move | NUMBER | |
| 9 | FM_OPERATION_SEQ_NUM | The operation moved FROM | NUMBER | |
| 10 | FM_INTRAOPERATION_STEP_TYPE | The step moved from (queue, run, to-move, reject, scrap) — numeric, undecoded; direction derives from the from/to pair | NUMBER | |
| 11 | TO_OPERATION_SEQ_NUM | The operation moved TO | NUMBER | |
| 12 | TO_INTRAOPERATION_STEP_TYPE | The step moved to | NUMBER | |
| 13 | FM_DEPARTMENT_ID | Department moved from | NUMBER | |
| 14 | TO_DEPARTMENT_ID | Department moved to | NUMBER | |
| 15 | TRANSACTION_QUANTITY | Quantity moved, in the transaction UOM | NUMBER | |
| 16 | TRANSACTION_UOM | UOM of the move | VARCHAR2 | |
| 17 | PRIMARY_QUANTITY | Quantity in the assembly's primary UOM — the column to aggregate | NUMBER | |
| 18 | REASON_ID | Reason code on the move | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WIP_MOVE_TRANSACTIONSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- 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;7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <TRANSACTION_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON WIP_MOVE_TRANSACTIONS.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID AND WIP_MOVE_TRANSACTIONS.ORGANIZATION_ID = WIP_DISCRETE_JOBS.ORGANIZATION_ID