HR_ALL_ORGANIZATION_UNITS
Schema: HRmasterPer inventory orgThe master list of every organization unit of every classification — business groups, legal entities, operating units, inventory organizations, HR organizations — across all business groups; classification detail lives in HR_ORGANIZATION_INFORMATION
Naming trap: the "_ALL" suffix here means all BUSINESS GROUPS, not operating-unit striping — there is no ORG_ID column on this table. The ORGANIZATION_ID it carries is the primary key every org-shaped id in EBS (including operating-unit ORG_ID values) resolves to.
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
8 fields · 1 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | ORGANIZATION_ID | The organization unit's key — the id every org-shaped reference in EBS ultimately resolves to | NUMBER | Primary-key field |
| 2 | BUSINESS_GROUP_ID | The business group the org belongs to | NUMBER | |
| 3 | NAME | Organization name | VARCHAR2 | |
| 4 | DATE_FROM | Effectivity start date | DATE | |
| 5 | DATE_TO | Effectivity end date — NULL while active | DATE | |
| 6 | LOCATION_ID | The org's physical location record | NUMBER | |
| 7 | TYPE | User-defined organization type code | VARCHAR2 | |
| 8 | INTERNAL_EXTERNAL_FLAG | Internal vs external organization | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading HR_ALL_ORGANIZATION_UNITS 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.
4 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <watermark>
-- ============================================================
-- Table : HR_ALL_ORGANIZATION_UNITS — The master list of every organization unit of every classification — business groups, legal entities, operating units, inventory organizations, HR organizations — across all business groups; classification detail lives in HR_ORGANIZATION_INFORMATION
-- Purpose: Column-selected read of HR_ALL_ORGANIZATION_UNITS — auto-generated from field metadata
-- Grain : One row per inventory org (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. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.ORGANIZATION_ID AS "The organization unit's key — the id every org-shaped reference in EBS ultimately resolves to",
t.BUSINESS_GROUP_ID AS "The business group the org belongs to",
t.NAME AS "Organization name",
t.DATE_FROM AS "Effectivity start date",
t.DATE_TO AS "Effectivity end date — NULL while active",
t.LOCATION_ID AS "The org's physical location record",
t.TYPE AS "User-defined organization type code",
t.INTERNAL_EXTERNAL_FLAG AS "Internal vs external organization"
FROM <catalog>.<schema>.HR_ALL_ORGANIZATION_UNITS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
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
ON HR_ORGANIZATION_INFORMATION.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_IDON HR_OPERATING_UNITS.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_IDON ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_IDON MTL_PARAMETERS.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID
More Foundation tables
- HR_OPERATING_UNITSThe 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
- HR_ORGANIZATION_INFORMATIONClassification rows for each organization unit — which orgs are operating units, inventory orgs, or legal entities, and the per-classification attributes, keyed by a context code with generic attribute columns
- ORG_ORGANIZATION_DEFINITIONSThe delivered view that presents inventory organizations with their operating unit, legal entity, ledger, and chart of accounts in one row — the org-mapping backbone of most inventory reporting
- FND_FLEX_VALUE_SETSValue set definitions for key and descriptive flexfields — one row per value set with its validation type, format rules, and size limits; the configuration that gives SEGMENTn columns their meaning
- FND_FLEX_VALUESThe valid values belonging to each flexfield value set — one row per segment value, with enabled/date-effectivity flags and the parent-value linkage dependent and rollup hierarchies use
- FND_LOOKUP_VALUESThe generic lookup table — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per language; the decode target for coded columns across every module (EBS's analog of JDE's UDC table)