Understanding Matching and Mapping Nodes

Matching and mapping request items enables you to match nodes being inserted into a mapping viewpoint with existing nodes of a different node type and then inserting the incoming nodes under the accepted match candidates in the mapping hierarchy.

Unlike merging or deduplication operations, mapping does not result in source and target nodes being merged. Instead, the result of a mapping operation is that an incoming source node is inserted into a hierarchy mapping viewpoint under the matched target parent. For an overview on mapping in Oracle Fusion Cloud Enterprise Data Management, see Mapping Source Nodes to Target Nodes.

Considerations

• The following conditions must be met in order to run a mapping operation:
  • You must be in the context of a request, and the request items must have an Insert action.
  • The request items be in a mapping viewpoint (that is, the viewpoint must have a mapping bound binding status, see Understanding Bindings and Bound Data Objects).
  • The mapping viewpoint cannot allow shared nodes.
• The incoming request items must have a different node type than the target nodes. You configure match rules on the target node type. See Creating, Editing, and Deleting Matching Rules.
• Because the source and target nodes are not merged, survivorship rules are not used in mapping operations.

After you accept the match results and apply your changes, the request items are modified to insert the nodes under the parents that you have accepted. See Matching and Mapping Nodes.

Process Overview

Configuring and using matching and mapping request items follows this general process:

1. A metadata manager or a dimension owner performs the initial setup of the matching process:
   • Creates the data sources if you are bringing in data from a source other than an Cloud EDM application.
   • Defines the matching rules that determine how nodes from other data sources are matched with existing nodes based on their property values.
   • Optionally, configures matching stopwords to ignore common words such as "The" and "Company" from being used when matching request items.
2. A business user creates and submits a request with nodes to map to existing nodes. The request items can be manually created, loaded from a file, or generated from compare results or a subscription.
3. A data manager runs matching against the incoming nodes, reviews the matching candidates, and accepts or rejects the matches. See Matching and Mapping Nodes.
4. The data manager applies the match results to the incoming request items. For those nodes that are accepted as a match, the parents in the request item are changed to the accepted match candidates so that the incoming nodes are inserted under them. See Reviewing Mapping Results and Applying Changes.

   Accepted match results are saved for each data source so that the next time request items are brought in from that data source they are matched automatically.