Search Results org_information4

Overview

The view APPS.OE_HR_ORGANIZATION_INFO_V is a denormalized projection defined in the Oracle E-Business Suite Order Management (ONT) product module. It exposes the full set of generic descriptive flexfield segment columns and standard WHO (Who Columns) audit attributes for organization information records. The view is documented in the ETRM repository with the status VALID, and it is registered under the APPS schema in both Oracle EBS 12.1.1 and 12.2.2.

The most significant characteristic of this object is that its documented description is explicitly stated as "No longer used." This indicates that Oracle has de-supported or deprecated the view; it remains in the database for backward compatibility with legacy customizations, concurrent programs, and integrations but is not relied upon by current Oracle-delivered Order Management functionality. The view's definition is a simple pass-through SELECT with no joins, filters, or transformations, listing every column of its source object explicitly rather than using a wildcard.

Underlying Base Objects

The view is defined over a single referenced base object: HR_ORGANIZATION_INFORMATION, which is accessed in the view text through a synonym (the underlying table resides in the HR schema and is exposed in APPS via the standard synonym). Because the definition is a direct column-list SELECT from that source, OE_HR_ORGANIZATION_INFO_V does not add or derive any data—it is purely a column-selective, named wrapper. Every row returned corresponds one-to-one with a row in HR_ORGANIZATION_INFORMATION.

This projection relationship means that the same integrity, key structure, and functional context rules enforced on HR_ORGANIZATION_INFORMATION apply to the view. The ORG_INFORMATION_CONTEXT column in the base table determines which descriptive flexfield context applies to a given row, and consequently determines which of the ORG_INFORMATION1 through ORG_INFORMATION20 segments carry meaningful values.

Key Columns

• ORG_INFORMATION_ID — Primary identifier for the organization information record.
• ORG_INFORMATION_CONTEXT — The descriptive flexfield context governing which ORG_INFORMATIONn segments are populated and what they represent.
• ORGANIZATION_ID — The organization to which the information row belongs; this is the foreign key linking to HR_ALL_ORGANIZATION_UNITS and, in Order Management contexts, to operating unit and inventory organization definitions.
• ORG_INFORMATION1 through ORG_INFORMATION20 — Twenty generic flexfield segment columns. The column ORG_INFORMATION20 is the twentieth such segment and, as with the other segments, its business meaning is entirely determined by the context defined in ORG_INFORMATION_CONTEXT.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns recording the last concurrent process that touched the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — The secondary descriptive flexfield structure associated with the base table.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns.

Common Use Cases and Queries

Because the view is documented as no longer used, it should be treated as a legacy compatibility surface. The following query, filtered on the segment the user searched for, retrieves organization information keyed by context:

SELECT organization_id,
       org_information_context,
       org_information1,
       org_information20
FROM   apps.oe_hr_organization_info_v
WHERE  org_information_context = :context
AND    org_information20 IS NOT NULL;

A typical integration use case joins the view back to the organization master to resolve names:

SELECT o.name,
       v.org_information_context,
       v.org_information20
FROM   apps.oe_hr_organization_info_v v,
       apps.hr_all_organization_units o
WHERE  v.organization_id = o.organization_id
AND    v.org_information_context = 'Accounting Information';

Any new development should query HR_ORGANIZATION_INFORMATION directly or use the supported HR organization information APIs, since reliance on a deprecated view risks breakage in future releases or under patching. Existing dependent code should be reviewed and migrated to the supported base object or an approved public view.