Hierarchy
⤷ BC-I18-UNI (Application Component) I18N Unicode
⤷ SUMIG (Package) Unicode Migration: Tabellen Umsetzer + Reparatur Tool
Basic Data
Data Element | UMGACOLLRES |
Short Description | Collision resolution |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | UMGOCOLLRES | |
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 | Coll. Res. |
Medium | 20 | Collision resolution |
Long | 20 | Collision resolution |
Heading | 20 | Collision resolution |
Documentation
Definition
The Collision Resolution determines the behaviour of the Reprocess scan. It has two value:
- "Character based (fine)"
- "Code Page based (coarse)"
Defaut value
The default value is "Character based (fine)".
The option cannot be changed after the Consistency Check has been started.
Use
Whenever possible set the option to "Character based (fine)". This reduces the number of entries in the "Reprocess Logs".
Example:
A data records contains two words which have been maintained with German (code page 1100) and Hungarian (code page 1401) in the vocabulary.
If the collision resolution is set to "Code page based (coarse)" a log is written in the Reprocess log for this record because code pages 1100 and 1401 are not compatible. If the collision resolution is set to "Character based (fine)" a check is made for both words: if the first word maintained in German contains only characters which are also included in code page 1401, no log is written.
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 700 |