HR_ORGANIZATION_INFORMATION
Schema: HRcontrolPer inventory orgClassification 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
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.
- 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
6 fields · 1 key
6 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | ORG_INFORMATION_ID | Surrogate key of the classification/attribute row | NUMBER | Primary-key field |
| 2 | ORGANIZATION_ID | The organization this row classifies — joins to HR_ALL_ORGANIZATION_UNITS | NUMBER | |
| 3 | ORG_INFORMATION_CONTEXT | The context code that decides what the generic columns mean on this row | VARCHAR2 | |
| 4 | ORG_INFORMATION1 | Generic attribute 1 — meaning depends on the context | VARCHAR2 | |
| 5 | ORG_INFORMATION2 | Generic attribute 2 — meaning depends on the context | VARCHAR2 | |
| 6 | ORG_INFORMATION3 | Generic attribute 3 — meaning depends on the context | VARCHAR2 |
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.
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
ON HR_ORGANIZATION_INFORMATION.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID
More Foundation tables
- 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)
- GL_CODE_COMBINATIONSEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; inventory accounting distributions and every journal line reference accounts through CODE_COMBINATION_ID
- GL_LEDGERSOne row per ledger, tying together the four Cs — currency, calendar, chart of accounts, and accounting convention; the R12 replacement for the 11i sets-of-books table, and the ledger context every operating unit resolves to