WIP_ACCOUNTING_CLASSES
Schema: WIPcontrolPer inventory orgThe WIP accounting class master per organization — class code, type, and the elemental valuation and variance accounts jobs charge through
Class codes repeat across organizations — the key is code + org.
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
10 fields · 2 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CLASS_CODE | The accounting class code — key together with the organization | VARCHAR2 | Primary-key field |
| 2 | ORGANIZATION_ID | Inventory organization — part of the key; class codes repeat across orgs | NUMBER | Primary-key field |
| 3 | CLASS_TYPE | Class type — standard vs non-standard, asset vs expense; numeric, undecoded | NUMBER | |
| 4 | DESCRIPTION | Class description | VARCHAR2 | |
| 5 | DISABLE_DATE | When the class was disabled — NULL while active | DATE | |
| 6 | MATERIAL_ACCOUNT | GL valuation account (CCID) for material | NUMBER | |
| 7 | RESOURCE_ACCOUNT | GL valuation account for resource charges | NUMBER | |
| 8 | OVERHEAD_ACCOUNT | GL valuation account for overhead | NUMBER | |
| 9 | MATERIAL_VARIANCE_ACCOUNT | Material variance account | NUMBER | |
| 10 | RESOURCE_VARIANCE_ACCOUNT | Resource variance account | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading WIP_ACCOUNTING_CLASSES 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.
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <CLASS_CODE>, <watermark>
-- ============================================================
-- Table : WIP_ACCOUNTING_CLASSES — The WIP accounting class master per organization — class code, type, and the elemental valuation and variance accounts jobs charge through
-- Purpose: Column-selected read of WIP_ACCOUNTING_CLASSES — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + CLASS_CODE
-- 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.CLASS_CODE AS "The accounting class code — key together with the organization",
t.ORGANIZATION_ID AS "Inventory organization — part of the key; class codes repeat across orgs",
t.CLASS_TYPE AS "Class type — standard vs non-standard, asset vs expense; numeric, undecoded",
t.DESCRIPTION AS "Class description",
t.DISABLE_DATE AS "When the class was disabled — NULL while active",
t.MATERIAL_ACCOUNT AS "GL valuation account (CCID) for material",
t.RESOURCE_ACCOUNT AS "GL valuation account for resource charges",
t.OVERHEAD_ACCOUNT AS "GL valuation account for overhead",
t.MATERIAL_VARIANCE_ACCOUNT AS "Material variance account",
t.RESOURCE_VARIANCE_ACCOUNT AS "Resource variance account"
FROM <catalog>.<schema>.WIP_ACCOUNTING_CLASSES t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.CLASS_CODE = '<CLASS_CODE>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CLASS_CODE;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_DISCRETE_JOBS.CLASS_CODE = WIP_ACCOUNTING_CLASSES.CLASS_CODE AND WIP_DISCRETE_JOBS.ORGANIZATION_ID = WIP_ACCOUNTING_CLASSES.ORGANIZATION_ID
More Work in Process tables
- 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
- WIP_TRANSACTIONSThe 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