Search Results warehouse_fk

Overview

EDW_PMI_PMIL_PLOC_LTC_IV is an Oracle EBS database view belonging to the PMI — Process Manufacturing Intelligence product family. In Oracle EBS 12.1.1 and 12.2.2, PMI is documented as obsolete, and this object is explicitly recorded as "Not implemented in this database" within the ETRM metadata. The view functions as an interface (denoted by the _IV suffix) that projects a curated column set from an underlying Enterprise Data Warehouse staging table for Process Manufacturing location data. Its role in the EBS reporting and integration landscape is to expose location-level attributes — capacity, capacity unit of measure, descriptive text, instance codes, and user-defined attributes — in a form suitable for downstream extract, transform, and load (ETL) processes feeding analytical or warehouse reporting layers. Because it is an interface view rather than a transactional object, it does not participate in on-line transaction processing; it exists purely to standardize the shape of location data for consumers such as Oracle Business Intelligence or custom data marts.

Underlying Base Objects

The documented source is the single base object EDW_PMI_PMIL_PLOC_LTC. The ETRM metadata records no additional referenced base objects, so the view is a straightforward projection with column aliasing and no joins. The view text selects WAREHOUSE_FK, WAREHOUSE_FK_KEY, CAPACITY, CAPACITY_UM, DESCRIPTION, INSTANCE_CODE, LOCATION, LOCATION_DP, LOCATION_PK, LOCATION_PK_KEY, LOCATION_PK_ROWID, NAME, USER_ATTRIBUTE1 through USER_ATTRIBUTE5, and OPERATION_CODE from the base table. Two derived aliases are applied: LOCATION_PK_ROWID is exposed as the column ROW_ID, and the fifth user attribute is projected a second time as OPERATION_CODE. This duplication pattern is characteristic of EDW interface views, where a generic attribute slot is repurposed to carry an operational discriminator. Because the metadata documents no join relationships, the view inherits the row cardinality of the base table directly.

Key Columns

• WAREHOUSE_FK and WAREHOUSE_FK_KEY — the foreign key and its surrogate key value identifying the owning warehouse or organization context.
• LOCATION_PK and LOCATION_PK_KEY — the primary key of the location record and its surrogate key. The presence of LOCATION_PK_KEY directly addresses searches for location_pk_key, which is the integration-stable key used to resolve a location across source and target systems.
• ROW_ID — derived from LOCATION_PK_ROWID, providing the physical row identifier.
• CAPACITY and CAPACITY_UM — the location capacity value and its unit of measure.
• DESCRIPTION, NAME, LOCATION, LOCATION_DP, INSTANCE_CODE — descriptive and instance-identifying attributes.
• USER_ATTRIBUTE1–USER_ATTRIBUTE5 — configurable attribute slots; USER_ATTRIBUTE5 is additionally surfaced as OPERATION_CODE.

Common Use Cases and Queries

The view is typically consumed in warehouse load routines and reconciliation reports that must align location records between EBS and an external data model. A representative query joining the view back to warehouse reference data would be:

SELECT v.LOCATION_PK_KEY, v.WAREHOUSE_FK, v.NAME, v.CAPACITY, v.CAPACITY_UM, v.OPERATION_CODE FROM EDW_PMI_PMIL_PLOC_LTC_IV v WHERE v.INSTANCE_CODE = :instance AND v.OPERATION_CODE = 'INSERT';

Because the view carries no WHERE clause of its own, filters on INSTANCE_CODE or OPERATION_CODE are essential when extracting delta records. Practitioners should note that in both 12.1.1 and 12.2.2 the object is documented as not implemented, so any dependency on it must be validated against the actual database before deployment.