Results for “dim_pk_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The EDW_TRD_PARTNER_MPV view is a dictionary object owned by the APPS schema within the Oracle E-Business Suite, catalogued under the PO - Purchasing product family. Its documented purpose is to serve as the EDW Trading Partner Mapping View, a lightweight projection used by Enterprise Data Warehouse (EDW) extraction and integration routines to resolve trading partner location identifiers into surrogate key values suitable for dimensional modelling. In the context of Oracle EBS 12.1.1 and 12.2.2, this view belongs to the broader family of EDW staging and mapping objects that bridge operational purchasing and receiving data with the analytical reporting layer maintained outside the transactional application. Its status is recorded as VALID, confirming the object compiles cleanly against the underlying EDW tables in a supported installation.

Underlying Base Objects

Per the documented view text, EDW_TRD_PARTNER_MPV is defined as a simple selection from a single underlying object:

• EDW_TPRT_TPARTNER_LOC_LCV — the trading partner location structure that supplies the source rows and columns for the mapping view.

The projection is minimal, selecting only TPARTNER_LOC_PK and LAST_UPDATE_DATE from that source. No additional joins, filters, or aggregation are documented, which indicates the view functions as a thin exposure layer rather than a transformation layer. The ETRM metadata for 12.2.2 lists no documented referenced base objects, so the dependency relationship with EDW_TPRT_TPARTNER_LOC_LCV is inferred directly from the published view text rather than from an expanded dependency listing. Because the object is owned by APPS and the source carries the EDW_ prefix, the underlying table resides in the EDW integration area rather than in the core transactional purchasing tables (PO_VENDORS, PO_VENDOR_SITES_ALL, and similar).

Key Columns

The view exposes a narrow column set that reflects its mapping role:

• TPARTNER_LOC_PK — the primary key of the trading partner location record. This is the value most commonly sought by downstream processes and is the column associated with the search term tpartner_loc_pk. It provides a stable surrogate identifier for a trading partner location as defined in the EDW model.
• LAST_UPDATE_DATE — the standard Oracle audit column recording the last modification timestamp of the source row. It enables incremental extraction, watermarking, and change-detection logic in ETL processes that read this view.

The metadata also records column names DIM_PK and DIM_PK_DATE in the documented column listing, reflecting the dimensional key naming conventions used across the EDW view set. Consumers should verify the exact exposed column set in their specific patch level, since the view text shown documents only the two projected columns.

Common Use Cases and Queries

This view is typically consumed by EDW extraction programs, interfaces, and ad-hoc reconciliation queries that need a lightweight, decoupled handle on trading partner location keys without touching the broader location value set. A representative query follows:

• SELECT TPARTNER_LOC_PK, LAST_UPDATE_DATE FROM APPS.EDW_TRD_PARTNER_MPV; — full listing of mapping keys.
• SELECT TPARTNER_LOC_PK FROM APPS.EDW_TRD_PARTNER_MPV WHERE LAST_UPDATE_DATE >= :p_since; — incremental/watermarked extraction.
• SELECT ... FROM APPS.EDW_TRD_PARTNER_MPV m, <fact_source> f WHERE f.tpartner_loc_pk = m.tpartner_loc_pk; — key resolution during dimensional loading.

Because it is a read-only APPS-owned view, use should be restricted to SELECT statements, and grants should be reviewed before exposing it to external ETL accounts.