WIP_TRANSACTIONS
Schema: WIPtransactionPer inventory orgThe WIP resource ledger — one row per resource charge (labor, machine, outside processing) with operation, resource, rates, and the purchasing/receiving references that drive outside-processing charges
Resource and overhead charges only — material movements live in the material transaction ledger. Outside-processing rows carry the PO header and the receiving transaction that triggered the charge, tying shop-floor cost back to procurement.
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.
- 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 withORGANIZATION_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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
18 fields · 1 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_ID | Surrogate key of the resource charge | NUMBER | Primary-key field |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 3 | WIP_ENTITY_ID | The job or schedule charged | NUMBER | |
| 4 | LINE_ID | The repetitive production line, for repetitive charges | NUMBER | |
| 5 | ACCT_PERIOD_ID | Accounting period of the charge | NUMBER | |
| 6 | OPERATION_SEQ_NUM | The operation charged | NUMBER | |
| 7 | RESOURCE_SEQ_NUM | The resource sequence within the operation | NUMBER | |
| 8 | RESOURCE_ID | The resource charged | NUMBER | |
| 9 | DEPARTMENT_ID | The department charged | NUMBER | |
| 10 | TRANSACTION_DATE | When the charge happened — the primary analysis date | DATE | The table's primary analysis date — a real DATE column, no conversion needed |
| 11 | TRANSACTION_TYPE | The charge kind — numeric, undecoded; this column exists here, not on the move ledger | NUMBER | |
| 12 | TRANSACTION_QUANTITY | Charged quantity in the transaction UOM | NUMBER | |
| 13 | TRANSACTION_UOM | UOM of the charge | VARCHAR2 | |
| 14 | PRIMARY_QUANTITY | Quantity in the primary UOM | NUMBER | |
| 15 | ACTUAL_RESOURCE_RATE | The actual rate charged | NUMBER | |
| 16 | STANDARD_RESOURCE_RATE | The standard rate — variance analysis pairs it with the actual | NUMBER | |
| 17 | PO_HEADER_ID | The outside-processing PO behind the charge, when OSP-driven | NUMBER | |
| 18 | RCV_TRANSACTION_ID | The receiving transaction that triggered the OSP charge — the cross-ledger link to receiving | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WIP_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.
7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <TRANSACTION_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : WIP_TRANSACTIONS — The WIP resource ledger — one row per resource charge (labor, machine, outside processing) with operation, resource, rates, and the purchasing/receiving references that drive outside-processing charges
-- Purpose: Column-selected read of WIP_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 resource charge",
t.ORGANIZATION_ID AS "Inventory organization",
t.WIP_ENTITY_ID AS "The job or schedule charged",
t.LINE_ID AS "The repetitive production line, for repetitive charges",
t.ACCT_PERIOD_ID AS "Accounting period of the charge",
t.OPERATION_SEQ_NUM AS "The operation charged",
t.RESOURCE_SEQ_NUM AS "The resource sequence within the operation",
t.RESOURCE_ID AS "The resource charged",
t.DEPARTMENT_ID AS "The department charged",
t.TRANSACTION_DATE AS "When the charge happened — the primary analysis date",
t.TRANSACTION_TYPE AS "The charge kind — numeric, undecoded; this column exists here, not on the move ledger",
t.TRANSACTION_QUANTITY AS "Charged quantity in the transaction UOM",
t.TRANSACTION_UOM AS "UOM of the charge",
t.PRIMARY_QUANTITY AS "Quantity in the primary UOM",
t.ACTUAL_RESOURCE_RATE AS "The actual rate charged",
t.STANDARD_RESOURCE_RATE AS "The standard rate — variance analysis pairs it with the actual",
t.PO_HEADER_ID AS "The outside-processing PO behind the charge, when OSP-driven",
t.RCV_TRANSACTION_ID AS "The receiving transaction that triggered the OSP charge — the cross-ledger link to receiving"
FROM <catalog>.<schema>.WIP_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
ON WIP_TRANSACTIONS.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = WIP_DISCRETE_JOBS.ORGANIZATION_IDON WIP_TRANSACTIONS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_IDON WIP_TRANSACTIONS.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_IDON WIP_TRANSACTIONS.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = RCV_TRANSACTIONS.ORGANIZATION_ID
More Work in Process tables
- WIP_ACCOUNTING_CLASSESThe WIP accounting class master per organization — class code, type, and the elemental valuation and variance accounts jobs charge through
- WIP_DISCRETE_JOBSDiscrete job detail — status, start/completed/scrapped quantities, scheduled vs actual dates, accounting class, and the BOM/routing the job was built from; the workhorse of job-level manufacturing analytics
- WIP_ENTITIESThe WIP identity registry — every discrete job, repetitive assembly, and flow schedule claims its id and unique name here before type-specific detail lands in child tables; the anchor outside references point at
- WIP_MOVE_TRANSACTIONSThe 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
- WIP_OPERATIONSOperations on a job or repetitive schedule — the shop-floor step sequence with department, live quantity counters per intraoperation step (queue, run, to-move, reject, scrap), and first/last-unit schedule dates
- WIP_REQUIREMENT_OPERATIONSMaterial requirements per job and operation — the job's exploded BOM with required vs issued quantities, supply type, and the supply subinventory issues pull from