Skip to content
EBS Reference

HR_ORGANIZATION_INFORMATION

Schema: HRcontrolPer inventory org

Classification 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

Identity
Module: FoundationInventory-org partitioned (ORGANIZATION_ID)
Notes

Multi-org structure is encoded here as context-discriminated generic columns — the same physical column changes meaning per context, so read it through the delivered views (HR_OPERATING_UNITS, ORG_ORGANIZATION_DEFINITIONS) unless you know the contexts.

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

6 fields · 1 key

6 fields.

Table fields: position, field name, description, data type, and flags. 6 fields.
#FieldDescriptionTypeFlags
1ORG_INFORMATION_IDSurrogate key of the classification/attribute rowNUMBER
Primary-key field
2ORGANIZATION_IDThe organization this row classifies — joins to HR_ALL_ORGANIZATION_UNITSNUMBER
3ORG_INFORMATION_CONTEXTThe context code that decides what the generic columns mean on this rowVARCHAR2
4ORG_INFORMATION1Generic attribute 1 — meaning depends on the contextVARCHAR2
5ORG_INFORMATION2Generic attribute 2 — meaning depends on the contextVARCHAR2
6ORG_INFORMATION3Generic attribute 3 — meaning depends on the contextVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HR_ORGANIZATION_INFORMATION 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.

Query parameters

4 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <watermark>

-- ============================================================
-- Table  : HR_ORGANIZATION_INFORMATION — Classification 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
-- Purpose: Column-selected read of HR_ORGANIZATION_INFORMATION — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + ORG_INFORMATION_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.ORG_INFORMATION_ID AS "Surrogate key of the classification/attribute row",
  t.ORGANIZATION_ID AS "The organization this row classifies — joins to HR_ALL_ORGANIZATION_UNITS",
  t.ORG_INFORMATION_CONTEXT AS "The context code that decides what the generic columns mean on this row",
  t.ORG_INFORMATION1 AS "Generic attribute 1 — meaning depends on the context",
  t.ORG_INFORMATION2 AS "Generic attribute 2 — meaning depends on the context",
  t.ORG_INFORMATION3 AS "Generic attribute 3 — meaning depends on the context"
FROM <catalog>.<schema>.HR_ORGANIZATION_INFORMATION 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.ORG_INFORMATION_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_ORGANIZATION_INFORMATIONHR_ALL_ORGANIZATION_UNITSforeign key · N:1
    ON HR_ORGANIZATION_INFORMATION.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID

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.