Results for “operating_unit_dp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EDW_HR_OPERATING_UNITS_LCV is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 release streams, owned by the PER (Human Resources) product module. It is categorized within the ETRM documentation as an Enterprise Data Warehouse (EDW) "LCV" — a logical/collection view — and is designed to expose Oracle HR operating units in a denormalized form suitable for downstream reporting, warehouse loads, and integration scenarios. The view presents operating unit records together with their associated legal entity references, business group assignments, cost method information, and descriptive flexfield segments.

The view is defined over EDWBV_HR_OPERATING_UNITS_LCV, which appears to be the base EDW layer view feeding this public LCV interface. The naming convention ("EDW" prefix, "LCV" suffix) is characteristic of Oracle's E-Business Intelligence/EDW views, which typically aggregate and flatten HRMS (Human Resource Management System) operating unit data for consumption by external reporting tools. Importantly, ETRM documentation records that this view is "Not implemented in this database" for the referencing environment, meaning the definition is documented but the object is not physically deployed in every EBS instance. The column list includes five null placeholder columns (USER_ATTRIBUTE1 through USER_ATTRIBUTE5), which are declared in the select list but are projected as NULL — a common pattern when the underlying base view does not yet populate descriptive flexfield user attributes in the deployed release.

Underlying Base Objects

The ETRM metadata documents only a single referenced object: EDWBV_HR_OPERATING_UNITS_LCV. No base tables (such as PER_OPERATING_UNITS, HR_OPERATING_UNITS, or HR_ALL_ORGANIZATION_UNITS) are explicitly documented as referenced. However, given the column semantics — OPERATING_UNIT_ID, NAME, DATE_FROM, DATE_TO, BUSINESS_GROUP — the underlying EDWBV view is almost certainly built over HR organization and operating unit entities. The EDW layer typically sources its data from the standard HRMS date-tracked operating unit table joined to legal entity information from the Financials/legal entity model.

Key Columns

• OPERATING_UNIT_PK / OPERATING_UNIT_ID — Surrogate primary key and the native operating unit identifier respectively.
• LEGAL_ENTITY_FK — Foreign key to the legal entity (LE) that the operating unit is associated with.
• OPERATING_UNIT_DP — Operating unit descriptive identifier; this column is the specific target the user searched for ("operating_unit_dp").
• NAME — Display name of the operating unit.
• BUSINESS_GROUP — The business group (HR security organization) to which the operating unit belongs.
• DATE_FROM / DATE_TO — Date-tracked effective range for the operating unit record.
• INT_EXT_FLAG — Internal/external classification flag.
• ORG_TYPE / ORG_CODE — Organization classification and code attributes.
• PRIMARY_CST_MTHD — Primary cost method associated with the organization.
• INSTANCE / LEVEL_NAME — Instance identifier and hierarchy level name.
• USER_ATTRIBUTE1–5 — Declared as NULL placeholder columns in the current definition.

Common Use Cases and Queries

This view is typically queried to resolve operating unit metadata for cross-module reporting, particularly where a report must map an operating unit to its legal entity and business group without joining native HRMS tables directly. A representative query follows:

SELECT operating_unit_id, name, operating_unit_dp, legal_entity_fk, business_group, date_from, date_to FROM edw_hr_operating_units_lcv WHERE date_to IS NULL OR date_to > SYSDATE;

Because ETRM notes the object may not be implemented in all databases, deployments should verify existence in ALL_VIEWS or ALL_OBJECTS before referencing it in custom code. Where it is absent, the underlying HR operating unit and legal entity views should be used directly.