SAP ABAP Data Element SIC_FM_MULTI_NODE_STRATEGY (Definition of Comparison Strategy for Node Instances)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-EIM-IQM-IC (Application Component) Information Consistency
     ⤷ S_IC_FINE_MATCH_CONFIG (Package) Information Consolidation Fine-Match Configuration
Basic Data
Data Element SIC_FM_MULTI_NODE_STRATEGY
Short Description Definition of Comparison Strategy for Node Instances  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SIC_FM_MULTI_NODE_STRATEGY    
Data Type NUMC   Character string with only digits 
Length 2    
Decimal Places 0    
Output Length 2    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 MultiValue 
Medium 20 Multi-Value Strategy 
Long 20 Multi-Value Strategy 
Heading 20 Multi-Value Strategy 
Documentation

Definition

Node

Strategy if there is more than one instance for a node.

This strategy is only valid for child nodes of hierarchic objects. This field is initial for flat objects and for the uppermost node of a hierarchic object.

Field

Strategy if multiple values or tokens are to be compared for a field.

This strategy is also valid for field groups. In this case you need a strategy for obtaining a similarity value for the field or field group from the similarity values of the value pairs.

Strategies

There are the following strategies:

  1. One value / token must match

    The similarity value of the field is defined by the similarity value of a value pair. In this case the similarity values of all value pairs are determined. The largest value obtained is the similarity value of the field.

  2. All values / tokens must match without order

    Here, too, each value of the source field is compared with each value of the target field, resulting in a similarity matrix. The similarity value of the field is defined as follows: All possible sums of similarity values are calculated from the similarity matrix; there is exactly one value from each row and each column. The similarity value of the field is defined by the largest sum that you get in this way divided by the number of addends.

  3. All values / tokens must match in order

    The procedure is as described under point 2, but a value of the source field may only be compared with values of the target field following the last compared value of the target field. In this way you retain the order of the field values. The similarity value of the field is reflected by the largest sum you obtain in this way divided by the number of addends.

  4. More than one value / token must match without order

    The procedure is as described under point 2, but sub-matrixes of the similarity matrix are also taken into consideration. The smallest sub-matrix has two rows and two columns. The similarity value of the field is reflected by the largest sum that you obtain in this way divided by the number of addends. In contrast to point 2, you might get a larger similarity value by not taking all values into consideration.

  5. More than one value / token must match in order

    The procedure for this strategy is a combination of the strategies described under points 2 and 4.

In the case of strategies 2 5, you use strategy 1 if either the source field or the target field has only one field value.

Use

Dependencies

Example

History
Last changed by/on SAP  20110908 
SAP Release Created in 710