Data Transformation Engine Type Designer Reference Guide

Chapter 14 - Type Tree Analyzer Why You Should Analyze Your Type Trees
Why You Should Analyze Your Type Trees
This section describes reasons for analyzing your trees.
Internal Consistency
The analyzer checks the logic of your data definitions. For example, suppose you
defined a group PO as fixed and consists of Line(s). For the PO to be fixed, it
cannot have an indefinite number of Lines. An analysis error would occur,
indicating that you defined PO as fixed but it has a variable number of
components.
Mapping Effects
The analyzer helps you define your data by locating objects in your input data and
creating the objects in your output data. The analysis indicates whether there is
something in your definition that may prevent a correct mapping your data.
In the preceding example using orders.mtt, if the orders data was your input and
you did not terminate each record with a CR/LF, the Map Designer would not know
when a record ends. It would not be able to find each record in the input.
If the orders data was the output and you did not define the terminator, CR/LF
would not be placed at the end of each record and the records would be received
one after the other, wrapped, with no line breaks.
If you do not analyze a tree before you map the data or you analyze a tree and do
not resolve the errors, you will be warned that you may receive unpredictable
results when you map. The following Warning message box will appear in the
Map Designer
When to Analyze Structure or Logic
You can choose to analyze the structure or the logic of your type definitions, or
both.