Search Results legal_entity_fk




Overview
Explore in AI Chat

Overview

EDW_ORGA_OPER_UNIT_LCV is an Oracle E-Business Suite collection view owned by the APPS schema, delivered as part of the HRI (Human Resources Intelligence) product family. Within the Oracle EBS 12.1.1 and 12.2.2 releases, the view exposes the Operating Units level of the Organization dimension for use in the Human Resources Intelligence data warehouse and associated reporting and integration layers. Its stated purpose in the ETRM repository is to serve as the collection view that flattens organizational hierarchy data into a single, query-ready structure. The view is currently VALID and is defined over the base object EDWBV_ORGA_OPER_UNIT_LCV, which handles the underlying derivation logic while EDW_ORGA_OPER_UNIT_LCV presents a stable, denormalized column layout to downstream consumers such as ETL mappings, BI Publisher reports, and custom extracts.

Underlying Base Objects

The ETRM metadata does not document any referenced base tables explicitly, but the embedded view text establishes the definitive lineage: EDW_ORGA_OPER_UNIT_LCV is defined as a SELECT projecting a fixed column list from EDWBV_ORGA_OPER_UNIT_LCV. Because the object name carries the EDW prefix, the underlying object is a Business Intelligence (BI) view rather than a transactional application table. That base view resolves operating unit data from the Human Resources and general ledger organization structures at load or query time. The wrapper view therefore acts as a controlled presentation layer over the BI view, and any column-level changes or additions made downstream to EDWBV_ORGA_OPER_UNIT_LCV should be assessed against this view before they are relied upon in reports or interfaces.

Key Columns

  • OPERATING_UNIT_PK — Surrogate primary key for the operating unit record in the Organization dimension; used to join to fact tables and sibling dimension views.
  • LEGAL_ENTITY_FK — Foreign key linking the operating unit to its owning legal entity. This is the column most relevant to the search term "legal_entity_fk" and provides the join path between organization-dimension reporting and legal-entity attributes.
  • NAME — Descriptive name of the operating unit.
  • OPERATING_UNIT_DP — Disambiguated or descriptive prefix used to distinguish operating units with otherwise identical names.
  • BUSINESS_GROUP — Business group to which the operating unit belongs, providing the HRMS security and organizational boundary.
  • DATE_FROM / DATE_TO — Effective dating range for the operating unit record, supporting date-tracked joins in the warehouse.
  • INT_EXT_FLAG — Internal/external classification indicator.
  • ORG_TYPE / ORG_CODE — Organization classification and short code.
  • PRIMARY_CST_MTHD — Primary costing method associated with the operating unit, important for inventory and cost reporting.
  • INSTANCE — Source instance identifier for multi-instance warehouse consolidation.
  • OPERATING_UNIT_ID — Transactional operating unit identifier, allowing reconciliation back to EBS application data.
  • LEVEL_NAME — Hierarchy level label for the organization dimension.
  • LAST_UPDATE_DATE / CREATION_DATE — Audit timestamps.
  • USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Placeholder extensibility columns projected as NULL in the view text for downstream customization.

Common Use Cases and Queries

Typical usage includes operating-unit-level headcount and cost reporting, legal-entity rollups, and cross-instance consolidation in HR Intelligence. A representative query joining operating units to their legal entity follows:

SELECT ou.operating_unit_id,
ou.name operating_unit,
ou.legal_entity_fk,
ou.business_group,
ou.primary_cst_mthd
FROM apps.edw_orga_oper_unit_lcv ou
WHERE ou.date_to IS NULL
ORDER BY ou.name;

To constrain reporting by legal entity, filter on the foreign key: SELECT operating_unit_pk, name FROM apps.edw_orga_oper_unit_lcv WHERE legal_entity_fk = :p_legal_entity_fk;. Because the view exposes both the surrogate (OPERATING_UNIT_PK) and transactional (OPERATING_UNIT_ID) keys, it supports both warehouse-style star joins and application-level reconciliation, making it a dependable anchor for EBS 12.1.1 and 12.2.2 HR Intelligence reporting.