Data Transformation Engine Map Designer Reference Guide

Chapter 17 - Debugging a Map Negative Messages Not Fatal
Map Designer Reference Guide
267
The optional Message is missing from the data. After finding the Header, the
next data object searched for is Message. However, the next object in the data is
not a Message, it is a LineItem.
H 1379,05/09/97,TSI,Alpha Water Sports
D Jet Skis,3,135.75
D Snorkle,4,13.35
D Inflatable boat,1,145.55
T Valerie,05/16/97
This data object is first
assumed to be a
Message
The trace file indicates that the initiator of the data object is not M which is the
initiator of a Message. After it is determined that the data object is not a
Message, the LineItem is validated as a LineItem. Shown below are the trace
messages for this scenario:
Data at offset 40 ('D Jet
Skis,3,135...') does not match INITIATOR
'M '
of TYPE X'0008' (Message Data).
COMPONENT number 2 of TYPE X'0002' (PO Data):
occurrence 1 is optional and does not exist.
Data at offset 42 ('Jet Skis') was found to
be of TYPE
X'000C' (Item Data).
Data at offset 51 ('3') was found to be of
TYPE
X'000D' (Qty Data).
Data at offset 53 ('135.75') was found to
be of TYPE
X'000E' (Price Data).
Data at offset 42 ('Jet Skis,3,135.7') was
found to be of TYPE
X'000B' (LineItem Data).
Remember, if you see a message in the trace file saying that a data object does
not exist, this is not necessarily the error causing the entire input object to be
invalid. Keep in mind the data being validated, and the optional data. Your
understanding of optional data is important when reading the trace file.