Mapping ParameterDirect or simple comparison of attributes is an ideal scenario but it may not always be possible. In situations where a direct match cannot be guaranteed, there are another ways to specify that a “similar” value will qualify as a match. These are described below. Comparison of String Attributes Where the identifying attribute is a string field, then the strings of different length can complicate the comparison. Also, the identifying string may be embedded in a larger string. To accommodate such situations, the comparison can be confined to a particular substring. Map operation has the "n" figure as a value which specifies the length of any substring. This substring must exist both in Valuemation and the SM object in the appropriate field. The following three notations are possible:
One of the three notations can always be selected, both for Valuemation and the SM definition. If the specified length is higher than the attribute length, it’s reduced to the attribute length. Example:
Two results are written to the Compare results:
Comparison of Numeric Attributes In the case of numeric attributes, it may be difficult to obtain an exact match. Rounding, inaccuracies on both sides and the difficulty of comparing decimal numbers mean that an exact match may be difficult to guarantee. For this situation, we can specify a percentage range which the numbers can differ within (but where they are close enough to say that we accept them as a match at the same time). A map operation for numeric attributes specifies the allowed percentage deviation from the initial reference value for the corresponding figure on the opposite side. The deviation value can be specified both in Valuemation and the SM object.
| |||||||||