Creating custom data validation levels

When values are mapped from one business object to another based on transformation code, incorrect data can result. The data validation feature checks each operation in a map and logs an error when data in the incoming business object cannot be transformed to data in the outgoing business object according to certain rules.

Example: Suppose that a map transforms a string value in the source business object to an integer value in the destination business object. This type conversion works properly when an incoming string value represents an integer (for example, "1234" represents the integer 1234). However, the conversion does not work properly if the string value does not represent an integer (for example, "ABCD" might indicate invalid data).

Coding a data validation level

The map development system defines data validation levels 0 and 1; levels 2 and greater are available for you to define. Table 55 summarizes the data validation levels:

Table 55. Data Validation Levels

Level Description
0 Default; no data validation
1 IBM-defined data type checks
2 and greater User-defined validation checks

Copyright IBM Corp. 2003