Search Results org_information6_meaning

Overview

APPS.HR_ORGANIZATION_INFORMATION_V1 is a supplementary database view registered under the PER product design data (FND Design Data: PER.HR_ORGANIZATION_INFORMATION_V1) within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Its stated purpose is to simplify forms coding for the Oracle HRMS organization information inquiry and maintenance screens. Oracle explicitly cautions that this view is not intended as a general-purpose query or DML target: the documentation warns that querying or altering data through this view is not recommended, because its definition may change dramatically in subsequent minor or major releases. Consequently, the view should be treated as a presentation-layer artifact rather than a stable integration interface.

The view is most commonly encountered by developers and report authors searching for the derived column ORG_INFORMATION6_MEANING. That column, unlike the base ORG_INFORMATION6 attribute, is a display-oriented value; the view resolves the stored code or lookup value in ORG_INFORMATION6 into a human-readable meaning, typically by joining against HR_LOOKUPS for the relevant organization information context.

Underlying Base Objects

According to the documented metadata, the view is defined over the following referenced base objects: the base table accessed through the HR_ORGANIZATION_INFORMATION synonym, the HR_LOOKUPS view, the HR_API package, the HR_DE_GENERAL package, and the FND_SESSIONS synonym. HR_ORGANIZATION_INFORMATION holds the raw attribute rows, keyed by ORGANIZATION_ID, ORG_INFORMATION_CONTEXT, and ORG_INFORMATION_ID, while HR_LOOKUPS supplies the display values that populate the derived columns such as ORG_INFORMATION6_MEANING. FND_SESSIONS and HR_DE_GENERAL support session context and date/effective-date handling, and HR_API provides the business logic and validation routines that govern the underlying records. The view therefore does not introduce independent persistence; it projects and decorates the base organization information rows for forms consumption.

Key Columns

• ORGANIZATION_ID — Identifier of the organization whose information record is being displayed.
• ORG_INFORMATION_ID — Primary key of the underlying row in the base table.
• ORG_INFORMATION_CONTEXT — Classifies the record (for example, organization type or a specific information category) and determines the meaning of the numbered attributes.
• ORG_INFORMATION1 through ORG_INFORMATION20 — The generic attribute slots carrying organization data; ORG_INFORMATION6 is VARCHAR2(150) and ORG_INFORMATION7 is NUMBER.
• ORG_INFORMATION6_MEANING — The derived VARCHAR2(80) column that resolves ORG_INFORMATION6 into its display meaning for the corresponding context.
• TAX_OFFICE_NAME and TAX_OFFICE_NUMBER — Derived display columns for tax office identification.
• ROW_ID — ROWID of the underlying base row.
• REQUEST_ID, PROGRAM_APPLICATION_ID — Standard concurrent request auditing columns inherited from the base record.

Common Use Cases and Queries

The primary scenario associated with this view is retrieving the meaning of ORG_INFORMATION6 for a given organization and context without writing the lookup join manually. A representative query is:

SELECT organization_id, org_information_context, org_information6, org_information6_meaning FROM apps.hr_organization_information_v1 WHERE organization_id = :p_org_id;

Additional practical uses include building HRMS extraction routines that must reproduce exactly what the organization information form displays, and troubleshooting discrepancies between stored codes and their visible meanings. Because Oracle documents the view as forms-support only, integration code should generally join HR_ORGANIZATION_INFORMATION to HR_LOOKUPS directly instead, and any reliance on the derived columns should be validated against the specific patch level in use.