Search Results edw_orga_oper_unit_ltc_iv

Overview

EDW_ORGA_OPER_UNIT_LTC_IV is a reporting and integration view exposed under the BIS (Business Intelligence System) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents operating unit information in a flattened, analytics-ready form suitable for extract, transform, and load (ETL) processes, data warehouse staging, and operational reporting. The "_IV" suffix indicates an interface view, and "_LTC" denotes its association with the operating unit lineage and current-state style of data sourcing typical of Oracle's EDW (Enterprise Data Warehouse) public views.

The view is not implemented as a physical database object in the standard installation; the ETRM documentation explicitly notes "Not implemented in this database." Its definition is therefore supplied as a DDL template that customers may deploy when building EDW extraction layers. The user's search term, "operating_unit_pk_key," maps directly to the OPERATING_UNIT_PK_KEY column, which is central to the view's role as a keyed operating unit reference.

Underlying Base Objects

The view is defined over a single documented base object: EDW_ORGA_OPER_UNIT_LTC. That base object is itself a delivery-layer construct that supplies the operating unit attribute set, including business group, org code, org type, primary costing method, and validity date ranges. The view wraps this base by projecting all its columns and appending a derived literal column, OPERATION_CODE, populated with a single space. This design preserves column-level lineage with the source while giving downstream consumers a stable, purpose-built interface.

No other base tables or views are documented as participating in the definition. Because the view is not physically present in the database, it must be created from the documented SELECT statement before any query executes against it.

Key Columns

• ROW_ID — the ROWID of the underlying base record, exposed for uniqueness and change tracking.
• OPERATING_UNIT_PK and OPERATING_UNIT_PK_KEY — the primary key value and its associated key reference for the operating unit, corresponding directly to the "operating_unit_pk_key" search term.
• BUSINESS_GROUP — the business group context in which the operating unit resides.
• LEGAL_ENTITY_FK and LEGAL_ENTITY_FK_KEY — foreign key references to the legal entity owning or associated with the operating unit.
• NAME, ORG_CODE, ORG_TYPE — the operating unit's descriptive name, organization code, and classification type.
• DATE_FROM, DATE_TO, CREATION_DATE, LAST_UPDATE_DATE — effective-dating and audit columns supporting point-in-time and change-data-capture reporting.
• INSTANCE, INT_EXT_FLAG — internal/external classification and instance identification flags.
• PRIMARY_CST_MTHD — the primary costing method used by the operating unit.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — extensibility placeholders for customer-defined attributes.
• LEVEL_NAME — indicates the hierarchy or level to which the operating unit record belongs.
• OPERATION_CODE — a derived column always populated with a single space, retained for interface compatibility with downstream processes.

Common Use Cases and Queries

The view is most commonly deployed as a key lookup for operating units in EDW mappings, enabling joins between transactional fact data and the operating unit dimension using OPERATING_UNIT_PK_KEY. A typical query retrieving active operating units and their costing method is:

SELECT OPERATING_UNIT_PK_KEY, NAME, ORG_CODE, ORG_TYPE, PRIMARY_CST_MTHD, LEVEL_NAME
FROM EDW_ORGA_OPER_UNIT_LTC_IV
WHERE TRUNC(SYSDATE) BETWEEN DATE_FROM AND DATE_TO
ORDER BY NAME;

Because the view is not installed by default, deployment precedes use:

CREATE OR REPLACE VIEW EDW_ORGA_OPER_UNIT_LTC_IV AS
SELECT ROWID ROW_ID, BUSINESS_GROUP, CREATION_DATE, DATE_FROM, DATE_TO, INSTANCE, INT_EXT_FLAG, LAST_UPDATE_DATE, LEGAL_ENTITY_FK, LEGAL_ENTITY_FK_KEY, NAME, OPERATING_UNIT_DP, OPERATING_UNIT_PK, OPERATING_UNIT_PK_KEY, ORG_CODE, ORG_TYPE, PRIMARY_CST_MTHD, USER_ATTRIBUTE1, USER_ATTRIBUTE2, USER_ATTRIBUTE3, USER_ATTRIBUTE4, USER_ATTRIBUTE5, LEVEL_NAME, ' ' OPERATION_CODE
FROM EDW_ORGA_OPER_UNIT_LTC;

After creation, the view is joined to other EDW interface views on BUSINESS_GROUP or LEGAL_ENTITY_FK_KEY to reconcile operating unit assignments across reporting layers. Administrators should treat the view as read-only and regenerate it whenever the underlying LTC delivery object changes.