Search Results inv_organization_info_v




Overview
Explore in AI Chat

Overview

INV_ORGANIZATION_INFO_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the Inventory (INV) product. It is defined as a VALID database object and presents a consolidated, query-friendly projection of inventory organization configuration data that is otherwise distributed across multiple HR and inventory tables. Its principal role is to expose, for each inventory organization, the organization identifier, the organization code, and the associated accounting context — namely the operating unit, the legal entity, and the set of books (ledger). Because the underlying accounting-context attributes are stored in a generic key-flexfield structure within HR_ORGANIZATION_INFORMATION, retrieving them directly requires knowledge of the flexfield segment mapping. The view encapsulates that mapping, allowing reporting tools, integrations, and custom concurrent programs to obtain organization-to-accounting relationships without reconstructing the joins and DECODE logic themselves. It is typically consumed in multi-org reporting, subledger integration, and data-conversion scripts that must resolve which operating unit, legal entity, and ledger an inventory organization belongs to.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through synonyms in the APPS schema: FND_PRODUCT_GROUPS, HR_ORGANIZATION_INFORMATION, and MTL_PARAMETERS. HR_ORGANIZATION_INFORMATION is joined twice — aliased HOI1 and HOI2 — on ORGANIZATION_ID. HOI1 supplies the organization classification row, restricted by ORG_INFORMATION1 = 'INV', ORG_INFORMATION2 = 'Y', and ORG_INFORMATION_CONTEXT = 'CLASS', which ensures only organizations classified as inventory organizations are returned. HOI2 supplies the accounting information row, filtered by ORG_INFORMATION_CONTEXT = 'ACCOUNTING INFORMATION', from which the operating unit (ORG_INFORMATION3), legal entity (ORG_INFORMATION2), and set of books (ORG_INFORMATION1) are derived. MTL_PARAMETERS provides the ORGANIZATION_ID and the human-readable ORGANIZATION_CODE and is joined on the same ORGANIZATION_ID. FND_PRODUCT_GROUPS is referenced in a scalar subquery to retrieve MULTI_ORG_FLAG; this flag determines whether the operating unit is populated at all, since the operating unit value is returned as a number only when multi-org is enabled, and as NULL otherwise.

Key Columns

  • ORGANIZATION_ID — The unique identifier of the inventory organization, sourced from MTL_PARAMETERS and HR_ORGANIZATION_INFORMATION.
  • ORGANIZATION_CODE — The short alphanumeric code assigned to the inventory organization, sourced from MTL_PARAMETERS.ORGANIZATION_CODE.
  • OPERATING_UNIT — The operating unit identifier derived from ORG_INFORMATION3, populated only when the FND_PRODUCT_GROUPS multi-org flag is 'Y'; otherwise NULL.
  • LEGAL_ENTITY — The legal entity identifier derived from ORG_INFORMATION2 of the accounting information row, cast to a number.
  • SET_OF_BOOKS_ID — The set of books (ledger) identifier derived from ORG_INFORMATION1 of the accounting information row, cast to a number.

Common Use Cases and Queries

The view is commonly used to resolve the accounting context of an inventory organization for reporting and integration, to validate organization setup during implementations, and to drive multi-org-aware queries that must filter by operating unit or ledger. A typical retrieval of all inventory organizations with their accounting attributes is:

  • SELECT organization_id, organization_code, operating_unit, legal_entity, set_of_books_id FROM apps.inv_organization_info_v;
  • Filtering by operating unit: SELECT organization_id, organization_code FROM apps.inv_organization_info_v WHERE operating_unit = :p_operating_unit;
  • Resolving the ledger for a given organization: SELECT organization_code, set_of_books_id FROM apps.inv_organization_info_v WHERE organization_id = :p_org_id;

Because OPERATING_UNIT may be NULL when multi-org is not enabled, consumers should account for that condition when joining to operating unit or ledger tables. The view is read-only in nature and is intended for query access rather than DML.