SAP ABAP Data Element CNV_10020_CONF_DETECTION (Conflict detection on evaluation of non-transp. fields)
Hierarchy
☛ DMIS (Software Component) DMIS 2011_1
   ⤷ CA-GTF-BS (Application Component) Business Application Support
     ⤷ CNV_10020 (Package) CNV package 10020
Basic Data
Data Element CNV_10020_CONF_DETECTION
Short Description Conflict detection on evaluation of non-transp. fields  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CNV_10020_CONF_DETECTION    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
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 Conflict 
Medium 15 Conflict detec. 
Long 20 Conflict detection 
Heading 4 Conf 
Documentation

Definition

The structure of a non-transparent field is clearly defined for every single data record. When converting several components of the same non-transparent field there is some fear that copmonents or parts of them might be converted twice. There are two possibilites for this:

  1. The rule for a component is (partly) wrong.
  2. Packages that convert the same data but use different names for the same component are blended.

Although it might be possible in some cases to detect some conflicts in advance by comparing the rules, a general conflict detection is only possible at runtime. To do so, each component evaluated is compared with the already evaluated components of the current data record. If there is an overlapping an error message is triggered.

Be aware that conflict detection at runtime is time-consuming. Therefore it should only be used if absolutely necessary. Using the value "T", you can switch it on only for those tables that are defined in table CNV_10020_CFTAB (transaction CNV_10020_CFTAB).

Notes

  1. Be aware that conflict detection is no error detection. If a rule is (partly) wrong and the package runs on its own there will be no conflict.
  2. There should be no two packages that convert the same kind of data. If you have that case anyway, it is unlikely that both packages use different names for the same component. If you have that case anyway, you should decide in advance which one of the packages to blend instead of blending both packages.

History
Last changed by/on SAP  20141030 
SAP Release Created in 2010_1_620