Search Results operating_unit_fk_key

Overview

The view EDW_ORGA_ORG_LTC_IV is a Business Intelligence System (BIS) reporting object within Oracle EBS 12.1.1 and 12.2.2. It is a denormalized, integration-oriented read-only view presenting organization and operating unit level data drawn from the enterprise data warehouse (EDW) star-schema layer. The suffix convention (EDW enterprise data warehouse, ORGA organization analytics, ORG organization, LTC level-to-currency / level table conformed, IV interface/integration view) indicates that the object is designed for extract consumption rather than transactional use.

Its primary role is to surface a flat, analytics-ready projection of the organization dimension alongside the operating unit foreign key (OPERATING_UNIT_FK), enabling downstream ETL jobs, OBIEE/DAC loads, and custom reports to resolve the relationship between an inventory organization and its owning operating unit without traversing the base HR and inventory organization tables. The view is documented as Not implemented in this database, meaning the definition may ship as documentation or template metadata but is instantiated only in environments where the DAL (Data Access Layer) / pre-built EDW schema is deployed.

Underlying Base Objects

The view text selects exclusively from a single base object, EDW_ORGA_ORG_LTC, which is the conformed organization level table in the EDW staging/warehouse layer. No other referenced base objects are documented in the ETRM metadata; therefore the view inherits all business logic from that single source and does not perform joins, unions, or aggregations. The columns exposed by EDW_ORGA_ORG_LTC_IV map one-to-one to columns on EDW_ORGA_ORG_LTC, with the exception of the literal OPERATION_CODE, which is added as a constant blank space via the expression ' ' OPERATION_CODE. The ROW_ID column is materialized from the base table's ROWID, providing a stable pseudo-key for row-level change detection in incremental loads. Because the underlying table is not a transactional EBS entity, the view does not enforce the security profiles, MOAC (Multi-Org Access Control), or org-hierarchy validations found on operational views such as HR_OPERATING_UNITS or ORG_ORGANIZATION_DEFINITIONS.

Key Columns

• ROW_ID — the physical ROWID of the underlying EDW_ORGA_ORG_LTC row, used for fast refresh and deduplication.
• BUSINESS_GROUP — the HR business group identifier to which the organization belongs.
• DATE_FROM, DATE_TO — date-effective range governing the validity of the organization/operating unit relationship.
• OPERATING_UNIT_FK — the operating unit foreign key; this is the column most commonly searched by implementers attempting to join organization records to an operating unit context.
• OPERATING_UNIT_FK_KEY — the surrogate key corresponding to the operating unit foreign key, suitable for dimensional joins in the EDW.
• ORGANIZATION_DP, ORGANIZATION_PK, ORGANIZATION_PK_KEY — organization-level descriptor, primary key, and surrogate key values.
• ORG_CODE, ORG_TYPE, ORG_INT_EXT_FLAG, ORG_PRIM_CST_MTHD — operational attributes describing the organization's code, classification, internal/external indicator, and primary costing method.
• NAME, INSTANCE, CREATION_DATE, LAST_UPDATE_DATE — identity and audit columns.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — ten flex attributes for customer-specific extensions.
• LEVEL_NAME — organizational hierarchy level descriptor.
• OPERATION_CODE — a literal blank placeholder column, typically used by the ETL framework as a slot for operation codes during incremental processing.

Common Use Cases and Queries

Typical uses include mapping organizations to operating units for multi-org reporting, feeding organization dimension loads, and resolving the OPERATING_UNIT_FK for an inventory organization.

SELECT ORGANIZATION_PK, ORG_CODE, OPERATING_UNIT_FK, OPERATING_UNIT_FK_KEY
FROM   EDW_ORGA_ORG_LTC_IV
WHERE  ORG_TYPE = 'INV';

Date-effective filtering supports as-of reporting:

SELECT ORG_CODE, OPERATING_UNIT_FK
FROM   EDW_ORGA_ORG_LTC_IV
WHERE  DATE_FROM <= SYSDATE
AND   (DATE_TO IS NULL OR DATE_TO >= SYSDATE);

A third pattern joins the view to a fact table on OPERATING_UNIT_FK_KEY to slice balances by operating unit, exploiting the EDW surrogate key rather than the transactional FK.