Results for “mapping_id”

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

Overview

EDW_PVT_MAP_COLUMNS_MD_V is a metadata-oriented database view belonging to the BIS (Business Intelligence System) product family within Oracle E-Business Suite. It is a component of the Enterprise Data Warehouse (EDW) private metadata layer, which supports the extraction, transformation, and loading infrastructure used to populate the EBS reporting and analytics environment. The view resolves the column-level lineage between source and target structures participating in a column mapping relationship, effectively exposing how an individual column in a source object is mapped to its counterpart column in a target object. It is a private ("_PVT_") object, meaning it is intended for internal consumption by EDW metadata processing logic rather than for direct end-user or customer reporting.

In the context of EBS 12.1.1 and 12.2.2, this view is documented as belonging to the BI/EDW metadata schema. The ETRM metadata notes that it is not implemented in this database, indicating that the view may exist conditionally or only in environments where the relevant EDW metadata objects have been deployed.

Underlying Base Objects

The view is defined over a set of intermediary metadata views rather than physical base tables: CMPWBITEMUSAGE_V, CMPITEM_V, CMPWBRELATIONUSAGE_V, and CMPWBACTUALPARAMETER_V. These constitute the "CMP" family of mapping metadata views used by the EDW mapping engine. The join logic links a source relation usage (SRC_RU) to a target relation usage (TGT_RU) via the CMPRELATIONMAPPING key, then resolves the respective item usages (SRC_IU, TGT_IU) and their underlying items (SRC_IT, TGT_IT), and finally correlates function-level usage through the actual parameter views (SRC_AP, TGT_AP). The predicate SRC_RU.SOURCE=1 identifies the source side of the mapping, while TGT_RU.DMLTYPE IS NOT NULL restricts the target to meaningful DML operations, and SRC_AP.CMPWBFUNCTIONUSAGE=TGT_AP.CMPWBFUNCTIONUSAGE ties the mapping together at the function-usage level. No physical base tables are documented; the metadata explicitly lists no referenced base objects beyond these views.

Key Columns

• MAPPING_ID — The CMPRELATIONMAPPING identifier that defines the overall relationship between source and target.
• SOURCE_USAGE_ID / TARGET_USAGE_ID — Element IDs of the source and target relation usages participating in the mapping.
• SOURCE_COLUMN_USAGE_ID / TARGET_COLUMN_USAGE_ID — Element IDs of the specific column usages on each side.
• SOURCE_COLUMN_ID / TARGET_COLUMN_ID — The underlying item (column) identifiers, providing the physical column lineage.
• FUNC_USAGE_ID — The CMPWBFUNCTIONUSAGE identifier linking the transformation function applied across source and target.

Common Use Cases and Queries

This view is typically used to audit or trace column-level mapping lineage within EDW metadata. A common query retrieves all column mappings for a given mapping definition:

• SELECT mapping_id, source_column_id, target_column_id, func_usage_id FROM edw_pvt_map_columns_md_v WHERE mapping_id = :p_mapping_id;
• Identify unmapped or partially mapped columns by comparing source and target column usage IDs.
• Trace which transformation functions are applied between a source and target column pair using the FUNC_USAGE_ID.
• Validate that every source column has a corresponding target column before executing an EDW load.

Because the view is private and not implemented in every database, queries should be preceded by an existence check against the data dictionary before use in production scripts.