HR_ALL_ORGANIZATION_UNITS_F
Product: PERmasterDate-effectiveThe 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
Date-effective: one row per org per EFFECTIVE_START_DATE/EFFECTIVE_END_DATE window — filter to the current row or every join multiplies
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.
- 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 withINVENTORY_ITEM_IDon 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_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin 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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
10 fields · 3 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | ORGANIZATION_ID | The organization unit's key — the id every org-shaped reference in Fusion ultimately resolves to | NUMBER | Key |
| 2 | EFFECTIVE_START_DATE | Start of this date-effective slice — part of the primary key | DATE | Key |
| 3 | EFFECTIVE_END_DATE | End of this date-effective slice — part of the primary key | DATE | Key |
| 4 | BUSINESS_GROUP_ID | Enterprise partition the org belongs to | NUMBER | |
| 5 | LEGAL_ENTITY_ID | Legal entity the org represents or belongs to | NUMBER | |
| 6 | ORGANIZATION_CODE | Organization code | VARCHAR2 | |
| 7 | TYPE | User-defined organization type code | VARCHAR2 | |
| 8 | INTERNAL_EXTERNAL_FLAG | Internal vs external organization | VARCHAR2 | |
| 9 | LOCATION_ID | The org's physical location record | NUMBER | |
| 10 | ESTABLISHMENT_ID | Establishment reference for statutory reporting | NUMBER |
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.
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
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.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.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.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.
More Foundation tables
- INV_ORG_PARAMETERSInventory organization parameters — one row per inventory org, holding the short org code, the item-master org it points to, its business unit and legal entity, and the org's locator/lot/serial control defaults; the org list every ORGANIZATION_ID resolves against
- FND_LOOKUP_VALUESThe generic lookup view — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per installed language; the decode target for coded columns across every module
- FUN_ALL_BUSINESS_UNITS_VThe delivered view that enumerates business units — the BU domain later waves' documents stripe on — with the legal entity, primary ledger, and default set each BU resolves to
- GL_CODE_COMBINATIONSEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; accounting distributions and journal lines reference accounts through CODE_COMBINATION_ID
- GL_LEDGERSOne row per ledger — currency, calendar, chart of accounts, and accounting convention; the ledger context business units and subledgers resolve to