Search Results target_usage_id




Overview
Explore in AI Chat

Overview

APPS.EDW_PVT_MAP_TARGETS_MD_V is a lightweight reporting view in the Oracle E-Business Suite data warehouse / Enterprise Data Warehouse (EDW) layer. It exposes the target-side metadata used by the EDW mapping engine, which pairs source data objects with target data objects as part of the extract, transform, and load (ETL) configuration. In EBS 12.1.1 and 12.2.2 this view belongs to the APPS schema and serves as the publicly accessible projection of the underlying mapping-target metadata, allowing report developers, integration specialists, and ETL administrators to inspect how a given mapping is associated with its target identifiers and aliases without querying the private base table directly.

The view does not perform any join, aggregation, or transformation. Its role is therefore primarily one of controlled exposure and naming stability: the APPS synonym / APPS-schema view interface lets custom code reference mapping-target metadata while the EDW private package (indicated by the EDW_PVT_ prefix) retains ownership of the base table and its lifecycle. Because the view is read-only in practice, it is a safe dependency for diagnostic queries and integration extracts.

Underlying Base Objects

The ETRM metadata documents that this view has no referenced base objects other than the single table named in its defining text. The view is defined directly over EDW_PVT_MAP_TARGETS_MD:

SELECT "MAPPING_ID", "TARGET_ID", "TARGET_USAGE_ID", "TARGET_ALIAS"
FROM EDW_PVT_MAP_TARGETS_MD

Consequently, all four exposed columns correspond one-to-one with columns of the same name in EDW_PVT_MAP_TARGETS_MD. No filtering predicate, WHERE clause, DISTINCT, or join is applied, so the view returns exactly the rows present in the base table. This is significant for performance purposes: querying the view is equivalent to querying the table with column projection, and any access path or index defined on the base table remains fully available. The "_MD" suffix conventionally denotes metadata in the EDW naming standards, and the "_PVT" prefix confirms that the base object is intended for internal package use with the view acting as the sanctioned external interface.

Key Columns

  • MAPPING_ID — Identifier of the EDW mapping to which the target association belongs. This is the primary correlation key linking target metadata back to the mapping definition.
  • TARGET_ID — Identifier of the target object (table, staging object, or logical target) that receives data for the mapping.
  • TARGET_USAGE_ID — The usage classification of the target within the mapping. This is the column most commonly searched for, since it distinguishes how the target is employed (for example, insert, update, or reference behavior) within a specific mapping definition.
  • TARGET_ALIAS — The alias assigned to the target, used to disambiguate targets and to provide a stable logical name in generated ETL or BI metadata. Aliases frequently appear in place of raw target identifiers in downstream reporting.

Common Use Cases and Queries

The most frequent requirement is to resolve a target to its mapping and usage context, which is exactly what the searched term target_usage_id implies. A typical query joins this view to a mapping definition for reporting:

SELECT m.mapping_id,
       v.target_id,
       v.target_usage_id,
       v.target_alias
FROM   apps.edw_pvt_map_targets_md_v v
WHERE  v.target_usage_id = :p_usage_id;

To enumerate all targets for a specific mapping:

SELECT target_id, target_usage_id, target_alias
FROM   apps.edw_pvt_map_targets_md_v
WHERE  mapping_id = :p_mapping_id
ORDER BY target_id;

These queries support ETL validation, impact analysis before changing a mapping, and troubleshooting when a load writes to an unexpected target. Because the view is a straight projection, an index on MAPPING_ID or TARGET_USAGE_ID in the base table will satisfy these predicates efficiently. No DML should ever be issued against the view; it is strictly a read-only metadata surface.