Skip to content
Fusion Reference

HR_ALL_ORGANIZATION_UNITS_F

Product: PERmasterDate-effective

The date-effective master list of every organization unit — business units, inventory orgs, departments, and legal-entity org rows all resolve their ids here, one row per org per effectivity window

Grain note

Date-effective: one row per org per EFFECTIVE_START_DATE/EFFECTIVE_END_DATE window — filter to the current row or every join multiplies

Notes

The organization NAME is not on this table — it lives in the translation companion (HR_ORGANIZATION_UNITS_F_TL, note the missing ALL — not yet cataloged), so name lookups are language-filtered. No enabled flag either: active status comes from the org classification rows. The ORGANIZATION_ID here is what INV_ORG_PARAMETERS and FUN_ALL_BUSINESS_UNITS_V ids resolve to.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

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

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
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.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Fields

10 fields · 3 key

10 fields.

Table fields: position, field name, description, data type, and flags. 10 fields.
#FieldDescriptionTypeFlags
1ORGANIZATION_IDThe organization unit's key — the id every org-shaped reference in Fusion ultimately resolves toNUMBER
Key
2EFFECTIVE_START_DATEStart of this date-effective slice — part of the primary keyDATE
Key
3EFFECTIVE_END_DATEEnd of this date-effective slice — part of the primary keyDATE
Key
4BUSINESS_GROUP_IDEnterprise partition the org belongs toNUMBER
5LEGAL_ENTITY_IDLegal entity the org represents or belongs toNUMBER
6ORGANIZATION_CODEOrganization codeVARCHAR2
7TYPEUser-defined organization type codeVARCHAR2
8INTERNAL_EXTERNAL_FLAGInternal vs external organizationVARCHAR2
9LOCATION_IDThe org's physical location recordNUMBER
10ESTABLISHMENT_IDEstablishment reference for statutory reportingNUMBER

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of HR_ALL_ORGANIZATION_UNITS_F on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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

5 parameters not filled: <catalog>, <schema>, <EFFECTIVE_START_DATE>, <EFFECTIVE_END_DATE>, <watermark>

-- ============================================================
-- Table  : HR_ALL_ORGANIZATION_UNITS_F — The date-effective master list of every organization unit — business units, inventory orgs, departments, and legal-entity org rows all resolve their ids here, one row per org per effectivity window
-- Purpose: Column-selected read of HR_ALL_ORGANIZATION_UNITS_F — auto-generated from field metadata
-- Grain  : One row per ORGANIZATION_ID + EFFECTIVE_START_DATE + EFFECTIVE_END_DATE
-- Caution: Date-effective: one row per org per EFFECTIVE_START_DATE/EFFECTIVE_END_DATE window — filter to the current row or every join multiplies
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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 Fusion ultimately resolves to",
  t.EFFECTIVE_START_DATE AS "Start of this date-effective slice — part of the primary key",
  t.EFFECTIVE_END_DATE AS "End of this date-effective slice — part of the primary key",
  t.BUSINESS_GROUP_ID AS "Enterprise partition the org belongs to",
  t.LEGAL_ENTITY_ID AS "Legal entity the org represents or belongs to",
  t.ORGANIZATION_CODE AS "Organization code",
  t.TYPE AS "User-defined organization type code",
  t.INTERNAL_EXTERNAL_FLAG AS "Internal vs external organization",
  t.LOCATION_ID AS "The org's physical location record",
  t.ESTABLISHMENT_ID AS "Establishment reference for statutory reporting"
FROM <catalog>.<schema>.HR_ALL_ORGANIZATION_UNITS_F t
WHERE
  CURRENT_DATE BETWEEN t.EFFECTIVE_START_DATE AND t.EFFECTIVE_END_DATE  -- current row of a date-effective table — see quirks guide #date-effective
  -- AND t.EFFECTIVE_START_DATE = '<EFFECTIVE_START_DATE>'
  -- AND t.EFFECTIVE_END_DATE = '<EFFECTIVE_END_DATE>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.EFFECTIVE_START_DATE;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

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

  • FUN_ALL_BUSINESS_UNITS_VHR_ALL_ORGANIZATION_UNITS_Fforeign key · 1:N
    ON FUN_ALL_BUSINESS_UNITS_V.BU_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_ID AND CURRENT_DATE BETWEEN HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_START_DATE AND HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (HR_ALL_ORGANIZATION_UNITS_F) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.
  • INV_ORG_PARAMETERSHR_ALL_ORGANIZATION_UNITS_Fforeign key · 1:N
    ON INV_ORG_PARAMETERS.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_ID AND CURRENT_DATE BETWEEN HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_START_DATE AND HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (HR_ALL_ORGANIZATION_UNITS_F) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.
  • PO_DISTRIBUTIONS_ALLHR_ALL_ORGANIZATION_UNITS_Fforeign key · N:1
    ON PO_DISTRIBUTIONS_ALL.DESTINATION_ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_ID AND CURRENT_DATE BETWEEN HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_START_DATE AND HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (HR_ALL_ORGANIZATION_UNITS_F) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.
  • CST_COST_ORGS_VHR_ALL_ORGANIZATION_UNITS_Fforeign key · 1:N
    ON CST_COST_ORGS_V.COST_ORG_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_ID AND CURRENT_DATE BETWEEN CST_COST_ORGS_V.EFFECTIVE_START_DATE AND CST_COST_ORGS_V.EFFECTIVE_END_DATE AND CURRENT_DATE BETWEEN HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_START_DATE AND HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (CST_COST_ORGS_V, HR_ALL_ORGANIZATION_UNITS_F) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.