Search Results location_pk




Overview
Explore in AI Chat

Overview

The view EDW_PMI_PMIL_PLOC_LCV belongs to the Process Manufacturing Intelligence (PMI) product family, now classified as obsolete within the Oracle EBS 12.1.1 and 12.2.2 documentation sets. It is one of the EDW (Enterprise Data Warehouse) local instance views that PMI historically populated to feed its analytical and reporting layer. Its purpose is to present a unified, de-normalized list of "locations" as understood by the Operational Planning and Manufacturing (OPM) schema, reconciling three conceptually distinct entities — inventory locations, warehouses, and organizations — into a single conformed dimension suitable for downstream star-schema or extract use.

The view does not represent a transactional entity; it is a derived staging object. The ETRM metadata explicitly notes that it is "Not implemented in this database," meaning it is not created as a physical object in every environment and exists only when PMI's EDW schema has been deployed. This is consistent with the obsolete status: the object is retained in documentation for backward reference but is no longer part of active product maintenance.

Underlying Base Objects

The view text defines three SELECT branches combined with UNION ALL, drawn from the following base tables:

  • IC_LOCT_MST — the OPM location master, providing warehouse-scoped inventory locations.
  • IC_WHSE_MST — the OPM warehouse master, supplying the warehouse-level rows.
  • SY_ORGN_MST — the OPM organization master, supplying organization-level rows.
  • EDW_LOCAL_INSTANCE — a PMI local-instance descriptor used to stamp each row with an INSTANCE_CODE, enabling multi-instance consolidation.

Although the documented metadata lists "none documented" under referenced base objects, the view definition itself clearly depends on the four tables above. The absence of documented base objects reflects the obsolete classification rather than a technical gap.

Key Columns

  • LOCATION_PK — Composite primary key concatenating WHSE_CODE, LOCATION, INSTANCE_CODE and the literal 'OPM'. For warehouse-level rows the literal 'PWHS' substitutes for the location code; for organization-level rows 'PORG' is used.
  • INSTANCE_CODE — Identifies which EDW local instance sourced the row.
  • WAREHOUSE_FK — Foreign key to the corresponding warehouse dimension record.
  • LOCATION — The OPM location code; NULL for the warehouse and organization roll-up rows.
  • DESCRIPTION — From LOCT_DESC on the location master; NULL for synthetic rows.
  • CAPACITY / CAPACITY_UM — Capacity value and unit of measure held against the location; both NULL in the roll-up rows.
  • LOCATION_DP and NAME — Display values, formatted as WHSE-LOCATION for real locations and ALL LOCATIONS(<code>) for the warehouse and organization aggregates.
  • CREATION_DATE / LAST_UPDATE_DATE — Audit timestamps inherited from the source master rows.
  • USER_ATTIBUTE1 through USER_ATTRIBUTE5 — Placeholder columns, all set to NULL. Note the misspellings in the view text (USER_ATTIBUTE1, USER_ATRIBUTE1) alongside correctly spelled columns; consumers should select the correctly named variants.

Common Use Cases and Queries

Because the view consolidates three granularity levels, it is typically used to build a location dimension for OPM warehouse, inventory, or capacity analytics without writing three separate extracts. A representative query is:

SELECT LOCATION_PK, INSTANCE_CODE, WAREHOUSE_FK,
       LOCATION, DESCRIPTION, CAPACITY, CAPACITY_UM
FROM   EDW_PMI_PMIL_PLOC_LCV
WHERE  LOCATION_DP NOT LIKE 'ALL LOCATIONS%';

Filtering on LOCATION_DP isolates true location-level rows, while omitting the filter produces the full roll-up set for warehouse and organization summaries. Joining WAREHOUSE_FK to other EDW PMI views aligns location facts with warehouse facts across instances. Given the object's obsolete status, new development should migrate to supported OPM location master tables rather than relying on this view.