Results for “hr_organization_information”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_ORGANIZATION_INFORMATION is a core table in the Oracle E-Business Suite Human Resources (PER) module, owned by the HR schema. It stores the additional descriptive attributes of an organization that fall outside the base definition held in HR_ALL_ORGANIZATION_UNITS. Because organizations in EBS are modeled generically (a single organization unit can represent a business group, a legal employer, an operating unit, an inventory organization, or an HR organization), the flexible, key-value oriented columns in this table hold the class-specific and information-type-specific detail that gives each organization its particular character. Common examples include employer identification, tax reporting identifiers, location descriptors, and other class-dependent settings.

The table is therefore an extension (or detail) child of the organization header. Each row is governed by an associated information type, referenced through ORG_INFORMATION_CONTEXT, which maps to HR_ORG_INFORMATION_TYPES. The information type defines how the generic ORG_INFORMATION1 through ORG_INFORMATION20 columns should be interpreted for that context.

Based on the foreign key structure documented in the ETRM metadata, the heuristic Data Vault classification for this object is a link — it primarily records relationships between organizations and their information types, with dependent descriptive payload. This is offered as a modeling suggestion rather than a definitive designation.

Key Information Stored

Although the table is documented with 55 columns, the following are the most significant:

  • ORG_INFORMATION_ID — the surrogate primary key, enforced by the unique index HR_ORGANIZATION_INFORMATIO_PK.
  • ORGANIZATION_ID — foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the parent organization to which this row of attributes belongs.
  • ORG_INFORMATION_CONTEXT — foreign key to HR_ORG_INFORMATION_TYPES, defining the information type or classification that determines how the remaining value columns are interpreted.
  • ORG_INFORMATION1 – ORG_INFORMATION20 — the generic value columns holding the class-specific or type-specific attribute data. These are the business payload of the row.
  • PARTY_ID — reference to the associated TCA party, linking the organization to its trading community record where applicable.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 – ATTRIBUTE20 — the standard EBS descriptive flexfield (DFF) columns, allowing installations to capture additional client-specific attributes without schema change.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard concurrent program who-columns identifying the process that created or last touched the row.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Auditing and optimistic-locking columns present on virtually all EBS transactional tables.

The surrogate primary key (ORG_INFORMATION_ID) is distinct from any business-key candidate; the unique index documented is on the surrogate itself, and true uniqueness of a business row is achieved through the combination of ORGANIZATION_ID and ORG_INFORMATION_CONTEXT.

Common Use Cases and Queries

This table is typically queried when a report or interface needs organization attributes that are not held in HR_ALL_ORGANIZATION_UNITS, such as legal employer registration data, financial or tax identifiers, or business-group-specific configuration.

  • Retrieving all information types for a given organization, joined to HR_ORG_INFORMATION_TYPES to decode the context.
  • Reporting organization classification data for setups where specific ORG_INFORMATION[1..20] columns carry meaning for a known context.
  • Populating downstream integrations (for example, HR_H2PI_ORGANIZATION_INFO or HR_H2PI_ORGANIZATION_CLASS) that reference ORG_INFORMATION_ID.
  • Auditing changes to organization configuration using the who-columns and PROGRAM_UPDATE_DATE.

A representative query pattern joins the table to its parent and to the type lookup:

SELECT ooi.organization_id,
       ooi.org_information_context,
       ooi.org_information1,
       ooi.org_information2
FROM   hr.hr_organization_information ooi,
       hr.hr_all_organization_units  oau,
       hr.hr_org_information_types   oit
WHERE  ooi.organization_id        = oau.organization_id
AND    ooi.org_information_context = oit.org_information_context
AND    ooi.organization_id        = :p_organization_id;

Related Objects

The following related objects are the most significant to understand when working with this table:

  • HR_ALL_ORGANIZATION_UNITS — parent table; joined on ORGANIZATION_ID. Holds the primary definition of the organization.
  • HR_ORG_INFORMATION_TYPES — lookup table defining the valid information types; joined on ORG_INFORMATION_CONTEXT.
  • HR_H2PI_ORGANIZATION_INFO — references this table via ORG_INFORMATION_ID.
  • HR_H2PI_ORGANIZATION_CLASS — also references this table via ORG_INFORMATION_ID.
  • HZ_PARTIES — indirectly related through the PARTY_ID column, linking the organization to its trading community party record.
  • PER_ORGANIZATION_INFORMATION_API / PER_ORGANIZATION_API — the public PL/SQL APIs used to maintain organization and information records rather than direct DML.

When building custom reports or integrations, always prefer the supported APIs over direct inserts or updates, and validate ORG_INFORMATION_CONTEXT values against HR_ORG_INFORMATION_TYPES to ensure correct interpretation of the generic value columns.