Search Results organization_pk_key




Overview
Explore in AI Chat

Overview

The view EDW_PMI_PMIL_PORG_LTC_IV is a reporting and integration artifact belonging to the PMI – Process Manufacturing Intelligence product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows Oracle's Enterprise Data Warehouse (EDW) naming convention, where the _IV suffix denotes an "interface view" designed to expose process-manufacturing organization data in a flattened, denormalized form suitable for extraction, transformation, and loading into downstream analytical or warehouse systems. The object is documented in the ETRM metadata repository for release 12.2.2, where it is flagged as "Not implemented in this database," indicating that the view exists as a shipped definition but is not necessarily created or populated in every environment. ETRM records no owner and no documented referenced base objects, so the authoritative source of its structure is the embedded view text itself.

The view is organized around process-manufacturing organization records and the surrogate key columns that EBS uses to resolve foreign-key relationships — most notably ORGANIZATION_PK_KEY, the column a user searched for when locating this object. It serves as a stable, read-only contract for reporting consumers, shielding them from the physical layout of the underlying Process Manufacturing tables.

Underlying Base Objects

The view text defines a direct SELECT over a single base object: EDW_PMI_PMIL_PORG_LTC. No joins, unions, or aggregations appear in the definition. ETRM documents no referenced base objects, so the relationship between the view and its source table must be inferred from the SQL: EDW_PMI_PMIL_PORG_LTC_IV is a one-to-one projection of EDW_PMI_PMIL_PORG_LTC, adding only a column alias — ORGANIZATION_PK_ROWID is renamed to ROW_ID, and USER_ATTRIBUTE5 is projected a second time under the alias OPERATION_CODE. This aliasing pattern is characteristic of EDW interface views, which frequently remap descriptive attribute columns to semantic business names while preserving the underlying data verbatim.

Key Columns

  • COMPANY_FK and COMPANY_FK_KEY — the foreign-key value and its surrogate key form for the owning company/legal entity, enabling dimensional joins in the warehouse.
  • ORGANIZATION_PK, ORGANIZATION_PK_KEY, and ROW_ID — the primary identifier of the process organization, its surrogate key used for referential resolution, and the row identifier (aliased from ORGANIZATION_PK_ROWID). ORGANIZATION_PK_KEY is the key consumers typically use to join organization data to facts and other dimensions.
  • ORGANIZATION and ORGANIZATION_DP — the organization identifier and its display/description form.
  • NAME, DESCRIPTION, and INSTANCE_CODE — descriptive and instance-level attributes of the organization record.
  • USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — the standard Oracle descriptive flexfield attribute columns, with USER_ATTRIBUTE5 additionally surfaced as OPERATION_CODE.

Common Use Cases and Queries

The primary use case is extracting process-manufacturing organization reference data into an EDW or analytics platform, resolving ORGANIZATION_PK_KEY against organizational dimensions. A typical extract might read:

  • SELECT ORGANIZATION_PK, ORGANIZATION_PK_KEY, NAME, DESCRIPTION FROM EDW_PMI_PMIL_PORG_LTC_IV;
  • SELECT ORGANIZATION_PK_KEY, ORGANIZATION, OPERATION_CODE FROM EDW_PMI_PMIL_PORG_LTC_IV WHERE COMPANY_FK_KEY = :company;
  • SELECT ORGANIZATION_PK_KEY, ROW_ID FROM EDW_PMI_PMIL_PORG_LTC_IV WHERE INSTANCE_CODE = :instance;

Because ETRM records the view as not implemented, DBAs should confirm its existence via ALL_VIEWS before relying on it, and validate that the base table EDW_PMI_PMIL_PORG_LTC is present and populated in the target instance.