Results for “edw_relationmapping_md_v”
29 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
EDW_RELATIONMAPPING_MD_V is a read-only metadata view shipped within the Oracle E-Business Suite under the BIS (Business Intelligence System / Applications BIS) product family. It exposes relation-mapping metadata used by the Enterprise Data Warehouse (EDW) and ETL infrastructure to describe how source data entities are transformed into, or related to, target data entities. In the context of Oracle EBS 12.1.1 and 12.2.2, such metadata views are consulted by warehouse-loading programs, Oracle Business Intelligence components, and custom integration routines that need a programmatic catalog of entity relationships rather than hard-coded mappings.
The view is defined as a thin projection over CMPRELATIONMAPPING_V, a composite/compiled view belonging to the BIS schema layer. Because EDW_RELATIONMAPPING_MD_V is declared WITH READ ONLY, it functions purely as a query surface; no DML can be issued against it. ETRM documents indicate that the object is not implemented in every database — its presence depends on whether the E-Business Intelligence / daily business intelligence schemas have been installed and patched at the required level. Confirming availability via DBA_VIEWS or ALL_VIEWS is therefore the first diagnostic step before depending on it.
Underlying Base Objects
According to the documented view text, the only referenced object is CMPRELATIONMAPPING_V:
- CMPRELATIONMAPPING_V — the immediate parent view from which all five columns are selected. ETRM records no further documented base tables for EDW_RELATIONMAPPING_MD_V itself; the underlying physical tables reside beneath CMPRELATIONMAPPING_V and are resolved through that view's own definition.
- Restriction: the query is declared WITH READ ONLY, so the view is non-updatable regardless of whether the parent view is key-preserved.
- No documented owned synonyms, grants, or indexes apply to this view; access is inherited from the owner of CMPRELATIONMAPPING_V and any public synonym layered on top.
Because no base objects are separately documented, tuning a query against this view in practice means inspecting the plan generated for CMPRELATIONMAPPING_V and, if needed, tracing further down its dependency chain using DBA_DEPENDENCIES.
Key Columns
The view exposes five columns, each carrying entity-mapping metadata:
- SOURCEDATAENTITY — identifies the originating data entity in the mapping pair (the "from" side of a relation).
- TARGETDATAENTITY — identifies the destination data entity (the "to" side), i.e., the entity that the source is mapped or loaded into.
- ELEMENTID — the identifier of the individual mapping element or record that links the two entities.
- PARENTMODEL — the model under which the mapping is grouped; useful for filtering mappings belonging to a particular data model or warehouse construct.
- NAME — the descriptive name of the relation mapping, typically the human-readable label used in BI metadata administration.
Together these columns describe a directed relationship between two data entities within a named model, keyed by an element identifier.
Common Use Cases and Queries
Typical usage centres on metadata discovery and validation of EDW entity mappings:
- List all mappings for a model:
SELECT elementid, name, sourcedataentity, targetdataentity FROM edw_relationmapping_md_v WHERE parentmodel = :model_name ORDER BY name;
- Find the targets of a given source entity:
SELECT targetdataentity, name, parentmodel FROM edw_relationmapping_md_v WHERE sourcedataentity = :entity;
- Trace upstream/downstream chains across models by joining TARGETDATAENTITY back to SOURCEDATAENTITY in a self-join or CONNECT BY.
- Reconcile custom ETL: compare the view's mappings against custom warehouse-loading code to detect drift after patching.
- Availability check:
SELECT owner, view_name FROM dba_views WHERE view_name = 'EDW_RELATIONMAPPING_MD_V';
Because the object is read-only and not present in all databases, scripts should guard against ORA-00942 by verifying existence first, and all access should be treated as reporting-only against the BIS metadata layer.
-
EDW_RELATIONMAPPING_MD_V
APPS.EDW_RELATIONMAPPING_MD_V·↳ EDW_RELATIONMAPPING_MD·Explore BIS module →
-
EDW_RELATIONMAPPING_MD_V
Not implemented in this database·Explore BIS module →
-
PACKAGE: APPS.EDW_TRUNC_STG 12.1.1
-
PACKAGE: APPS.EDW_DEL_STG 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
eTRM - BIS Tables and Views 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - BIS Tables and Views 12.1.1