Search Results edwbv_orga_oper_unit_lcv




Overview
Explore in AI Chat

Overview

EDWBV_ORGA_OPER_UNIT_LCV is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HRI (Human Resources Intelligence) product module. It serves as the base view for the Operating Units level of the Organization dimension within the Oracle HR Intelligence/Enterprise Data Warehouse reporting model. The "LCV" suffix denotes a "localized condensed view," which is a standard ETRM convention indicating a flattened, denormalized projection designed for dimensional loading and BI consumption. In Oracle EBS 12.1.1 and 12.2.2, this view presents operating units as a distinct level within the Organization hierarchy, joining human resources organization structures with inventory organization parameters and the local instance context. It is a read-only reporting construct and is not exposed for transactional DML.

Underlying Base Objects

Although the ETRM metadata documents no base objects, the view definition indicates that it is built over the following APPS tables: HR_ALL_ORGANIZATION_UNITS (aliased OU for the operating unit, OUBG for its business group, and LE for the associated legal entity), HR_ORGANIZATION_INFORMATION (aliased OI1 for the CLASS context and OI2 for the OPERATING UNIT INFORMATION context), MTL_PARAMETERS (MP, providing inventory organization attributes), and EDW_LOCAL_INSTANCE (I, supplying the instance code). The joins establish that OUBG is the business group of the operating unit (OU.BUSINESS_GROUP_ID = OUBG.ORGANIZATION_ID), OI1 identifies the organization as an operating unit when ORG_INFORMATION1 = 'OPERATING_UNIT' and ORG_INFORMATION2 = 'Y', and OI2 links the operating unit to its legal entity identifier. MTL_PARAMETERS contributes the inventory organization code and cost method.

Key Columns

  • OPERATING_UNIT_PK — Surrogate primary key formed as ORGANIZATION_ID concatenated with the instance code.
  • LEGAL_ENTITY_FK — Foreign key to the legal entity, built from the legal entity organization ID and instance code.
  • NAME / OPERATING_UNIT_DP — Combined operating unit and business group name used as the display value.
  • BUSINESS_GROUP — The business group name.
  • DATE_FROM / DATE_TO — Effective date bounds for the operating unit.
  • INT_EXT_FLAG / ORG_TYPE — Decoded lookup values for internal/external flag and organization type.
  • ORG_CODE / PRIMARY_CST_MTHD — Inventory organization code and primary cost method from MTL_PARAMETERS.
  • INSTANCE — Instance code identifying the source EBS environment.
  • OPERATING_UNIT_ID — Native ORGANIZATION_ID of the operating unit.
  • LEVEL_NAME — Constant value 'OU', marking the dimension level.
  • LAST_UPDATE_DATE / CREATION_DATE — Greatest-of audit columns driving incremental extraction.

Common Use Cases and Queries

Typical use cases include HR Intelligence dimensional loads, cross-instance consolidation reporting, and operating unit validation queries within the enterprise data warehouse.

  • List all operating units with their legal entity and business group.
  • Filter operating units for a specific instance or legal entity.
  • Extract incremental changes based on LAST_UPDATE_DATE.

Sample query:

SELECT operating_unit_pk, name, legal_entity_fk, business_group, org_code, instance FROM apps.edwbv_orga_oper_unit_lcv WHERE instance = :p_instance ORDER BY name;

Because the view performs multi-table joins with string concatenation and a GREATEST/TO_NUMBER expression in later clauses, queries should apply selective predicates on OPERATING_UNIT_ID or INSTANCE to avoid unnecessary full scans during extraction.