Skip to content
EBS Reference

HR_OPERATING_UNITS

Schema: HRviewOperating-unit key (ORGANIZATION_ID)View

The delivered view that enumerates operating units — the ORG_ID domain — with their business group, ledger, and legal context; the standard way to turn the ORG_ID on an _ALL table into a name

Identity
Module: FoundationOperating-unit view key (ORGANIZATION_ID)
Notes

APPS-schema view over the HR org tables (product: Human Resources). ORGANIZATION_ID is the operating-unit identifier joined from subledger ORG_ID; it is not an inventory-organization anchor. The view does not project LAST_UPDATE_DATE, so use a full refresh or a verified base-table strategy instead of the generated WHO watermark. Its ledger and legal-context columns are read out of generic attribute columns and come back as VARCHAR2 — cast with TO_NUMBER before joining GL_LEDGERS.LEDGER_ID.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

Fields

9 fields · 1 key

9 fields.

Table fields: position, field name, description, data type, and flags. 9 fields.
#FieldDescriptionTypeFlags
1ORGANIZATION_IDThe operating unit's org id — the value ORG_ID columns on _ALL tables carryNUMBER
Primary-key field
2NAMEOperating unit nameVARCHAR2
3SHORT_CODEOperating unit short codeVARCHAR2
4BUSINESS_GROUP_IDThe business group the operating unit belongs toNUMBER
5DATE_FROMEffectivity start dateDATE
6DATE_TOEffectivity end date — NULL while activeDATE
7SET_OF_BOOKS_IDThe ledger id — comes back as text (read from a generic attribute column), so cast with TO_NUMBER before joining GL_LEDGERSVARCHAR2
8DEFAULT_LEGAL_CONTEXT_IDThe default legal entity context — text for the same reason; cast before joiningVARCHAR2
9USABLE_FLAGWhether the operating unit is usableVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HR_OPERATING_UNITS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. This view does not project LAST_UPDATE_DATE, so the snippet omits that watermark. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

3 parameters not filled: <catalog>, <schema>, <operating_unit_id>

-- ============================================================
-- Table  : HR_OPERATING_UNITS — The delivered view that enumerates operating units — the ORG_ID domain — with their business group, ledger, and legal context; the standard way to turn the ORG_ID on an _ALL table into a name
-- Purpose: Column-selected read of HR_OPERATING_UNITS — auto-generated from field metadata
-- Grain  : One row per operating unit (ORGANIZATION_ID) — see the Fields section for the full key
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. This object does not project LAST_UPDATE_DATE; use a full refresh or a verified base-table watermark strategy. APPS-schema view — land its base tables for extraction; see the table notes.
-- ============================================================
SELECT
  t.ORGANIZATION_ID AS "The operating unit's org id — the value ORG_ID columns on _ALL tables carry",
  t.NAME AS "Operating unit name",
  t.SHORT_CODE AS "Operating unit short code",
  t.BUSINESS_GROUP_ID AS "The business group the operating unit belongs to",
  t.DATE_FROM AS "Effectivity start date",
  t.DATE_TO AS "Effectivity end date — NULL while active",
  t.SET_OF_BOOKS_ID AS "The ledger id — comes back as text (read from a generic attribute column), so cast with TO_NUMBER before joining GL_LEDGERS",
  t.DEFAULT_LEGAL_CONTEXT_ID AS "The default legal entity context — text for the same reason; cast before joining",
  t.USABLE_FLAG AS "Whether the operating unit is usable"
FROM <catalog>.<schema>.HR_OPERATING_UNITS t
WHERE
  t.ORGANIZATION_ID = <operating_unit_id>  -- operating unit id exposed under ORGANIZATION_ID by this view
ORDER BY t.ORGANIZATION_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

  • HR_OPERATING_UNITSHR_ALL_ORGANIZATION_UNITSforeign key · 1:1
    ON HR_OPERATING_UNITS.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID
  • OE_ORDER_HEADERS_ALLHR_OPERATING_UNITSforeign key · N:1
    ON OE_ORDER_HEADERS_ALL.ORG_ID = HR_OPERATING_UNITS.ORGANIZATION_ID
  • PO_HEADERS_ALLHR_OPERATING_UNITSforeign key · N:1
    ON PO_HEADERS_ALL.ORG_ID = HR_OPERATING_UNITS.ORGANIZATION_ID
Extraction note

HR_OPERATING_UNITS is an APPS-schema convenience view. Land the base tables it joins instead of extracting from the view directly — views can be slow at scale and aren’t guaranteed stable across patches.

Browse more Foundation tables

More Foundation tables

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.