BOM_DEPARTMENTS
Schema: BOMmasterPer inventory orgThe department (work center) master per inventory organization — the places operations happen, with class, location, and the scrap account
DEPARTMENT_ID is globally unique; the department CODE is unique only per organization.
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
8 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DEPARTMENT_ID | Surrogate key of the department — globally unique | NUMBER | Key |
| 2 | DEPARTMENT_CODE | The department code users see — unique only per organization | VARCHAR2 | |
| 3 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 4 | DESCRIPTION | Department description | VARCHAR2 | |
| 5 | DEPARTMENT_CLASS_CODE | Department class grouping | VARCHAR2 | |
| 6 | LOCATION_ID | Physical location record | NUMBER | |
| 7 | DISABLE_DATE | When the department was disabled — NULL while active | DATE | |
| 8 | SCRAP_ACCOUNT | The GL account (CCID) scrap at this department charges to | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading BOM_DEPARTMENTSon 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 : BOM_DEPARTMENTS — The department (work center) master per inventory organization — the places operations happen, with class, location, and the scrap account
-- Purpose: Column-selected read of BOM_DEPARTMENTS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + DEPARTMENT_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.DEPARTMENT_ID AS "Surrogate key of the department — globally unique",
t.DEPARTMENT_CODE AS "The department code users see — unique only per organization",
t.ORGANIZATION_ID AS "Inventory organization",
t.DESCRIPTION AS "Department description",
t.DEPARTMENT_CLASS_CODE AS "Department class grouping",
t.LOCATION_ID AS "Physical location record",
t.DISABLE_DATE AS "When the department was disabled — NULL while active",
t.SCRAP_ACCOUNT AS "The GL account (CCID) scrap at this department charges to"
FROM <catalog>.<schema>.BOM_DEPARTMENTS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.DEPARTMENT_ID = <DEPARTMENT_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DEPARTMENT_ID;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DEPARTMENT_ID>, <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 BOM_OPERATION_SEQUENCES.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_IDON BOM_DEPARTMENTS.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_IDON CST_ITEM_COST_DETAILS.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID AND CST_ITEM_COST_DETAILS.ORGANIZATION_ID = BOM_DEPARTMENTS.ORGANIZATION_IDON WIP_OPERATIONS.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID AND WIP_OPERATIONS.ORGANIZATION_ID = BOM_DEPARTMENTS.ORGANIZATION_ID