Skip to content
EBS Reference

WIP_TRANSACTIONS

Schema: WIPtransactionPer inventory org

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

Module: Work in ProcessInventory-org partitioned (ORGANIZATION_ID)
Notes

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

18 fields · 1 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_IDSurrogate key of the resource chargeNUMBER
Key
2ORGANIZATION_IDInventory organizationNUMBER
3WIP_ENTITY_IDThe job or schedule chargedNUMBER
4LINE_IDThe repetitive production line, for repetitive chargesNUMBER
5ACCT_PERIOD_IDAccounting period of the chargeNUMBER
6OPERATION_SEQ_NUMThe operation chargedNUMBER
7RESOURCE_SEQ_NUMThe resource sequence within the operationNUMBER
8RESOURCE_IDThe resource chargedNUMBER
9DEPARTMENT_IDThe department chargedNUMBER
10TRANSACTION_DATEWhen the charge happened — the primary analysis dateDATE
Filter date
11TRANSACTION_TYPEThe charge kind — numeric, undecoded; this column exists here, not on the move ledgerNUMBER
12TRANSACTION_QUANTITYCharged quantity in the transaction UOMNUMBER
13TRANSACTION_UOMUOM of the chargeVARCHAR2
14PRIMARY_QUANTITYQuantity in the primary UOMNUMBER
15ACTUAL_RESOURCE_RATEThe actual rate chargedNUMBER
16STANDARD_RESOURCE_RATEThe standard rate — variance analysis pairs it with the actualNUMBER
17PO_HEADER_IDThe outside-processing PO behind the charge, when OSP-drivenNUMBER
18RCV_TRANSACTION_IDThe receiving transaction that triggered the OSP charge — the cross-ledger link to receivingNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WIP_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.

Query parameters
-- ============================================================
-- 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;

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

  • WIP_TRANSACTIONSWIP_DISCRETE_JOBSforeign key · N:1
    ON WIP_TRANSACTIONS.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = WIP_DISCRETE_JOBS.ORGANIZATION_ID
  • WIP_TRANSACTIONSBOM_RESOURCESforeign key · N:1
    ON WIP_TRANSACTIONS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_ID
  • WIP_TRANSACTIONSPO_HEADERS_ALLforeign key · N:1
    ON WIP_TRANSACTIONS.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID
  • WIP_TRANSACTIONSRCV_TRANSACTIONSforeign key · N:1
    ON WIP_TRANSACTIONS.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = RCV_TRANSACTIONS.ORGANIZATION_ID

Browse more Work in Processtables →

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.