Interpretting the .MTR file

[dgerdner]

I have a 301 EDI message that causes an error when I try to run my map. The final line in the MTR file says:

"INPUT 1 was valid, but it contained invalid objects."

Is there anyway to read the MTR and discover what is causing the problem? Here is a copy of the entire MTR file:




(Level 2: Offset 3, len 0, comp 1 of 6, #1, DI 00000001
Type X'000F' (Partner Inbound ISA Segment Control ANSI EDI) is known to exist.

(Level 3: Offset 3, len 1, comp 1 of 4, #1, DI 00000001
Data at offset 3 ('*') was found to be of TYPE
X'0011' (Element Delimiter Control ANSI EDI).

(Level 4: Offset 4, len 2, comp 1 of 15, #1, DI 00000002
Data at offset 4 ('00') was found to be of TYPE
X'0014' (Auth'nInfoQual'r Element Control ANSI EDI).

(Level 4: Offset 7, len 10, comp 2 of 15, #1, DI 00000003
Data at offset 7 (' ') was found to be of TYPE
X'0015' (Auth'nInfo Element Control ANSI EDI).

(Level 4: Offset 18, len 2, comp 3 of 15, #1, DI 00000003
Data at offset 18 ('00') was found to be of TYPE
X'0016' (SecurityInfoQual'r Element Control ANSI EDI).

(Level 4: Offset 21, len 10, comp 4 of 15, #1, DI 00000004
Data at offset 21 (' ') was found to be of TYPE
X'0017' (SecurityInfo Element Control ANSI EDI).

(Level 4: Offset 32, len 2, comp 5 of 15, #1, DI 00000004
Data at offset 32 ('ZZ') was found to be of TYPE
X'0019' (Sender InterchangeIDQual'r Element Control ANSI EDI).

(Level 4: Offset 35, len 15, comp 6 of 15, #1, DI 00000005
Data at offset 35 ('WLWH ') was found to be of TYPE
X'001A' (InterchangeSenderID Element Control ANSI EDI).

(Level 4: Offset 51, len 2, comp 7 of 15, #1, DI 00000006
Data at offset 51 ('02') was found to be of TYPE
X'001B' (Receiver InterchangeIDQual'r Element Control ANSI EDI).

(Level 4: Offset 54, len 15, comp 8 of 15, #1, DI 00000007
Data at offset 54 ('AROF ') was found to be of TYPE
X'001C' (InterchangeRcv'rID Element Control ANSI EDI).

(Level 4: Offset 70, len 6, comp 9 of 15, #1, DI 00000008
Data at offset 70 ('051025') was found to be of TYPE
X'001D' (InterchangeDate Element Control ANSI EDI).

(Level 4: Offset 77, len 4, comp 10 of 15, #1, DI 00000009
Data at offset 77 ('1300') was found to be of TYPE
X'001E' (InterchangeTime Element Control ANSI EDI).

(Level 4: Offset 82, len 1, comp 11 of 15, #1, DI 0000000A
Data at offset 82 ('U') was found to be of TYPE
X'001F' (InterchangeCtrlStandardsID Element Control ANSI EDI).

(Level 4: Offset 84, len 5, comp 12 of 15, #1, DI 0000000B
Data at offset 84 ('00401') was found to be of TYPE
X'0020' (InterchangeCtrlVersion# Element Control ANSI EDI).

(Level 4: Offset 90, len 9, comp 13 of 15, #1, DI 0000000C
Data at offset 90 ('000000004') was found to be of TYPE
X'0021' (InterchangeCtrl# Element Control ANSI EDI).

(Level 4: Offset 100, len 1, comp 14 of 15, #1, DI 0000000D
Data at offset 100 ('0') was found to be of TYPE
X'0022' (Ack'tRequested Element Control ANSI EDI).

(Level 4: Offset 102, len 1, comp 15 of 15, #1, DI 0000000E
Data at offset 102 ('T') was found to be of TYPE
X'0023' (TestIndicator Element Control ANSI EDI).

(Level 3: Offset 4, len 100, comp 2 of 4, #1, DI 0000000F
Data at offset 4 ('00* *00') was found to be of TYPE
X'0012' (ISAPartnerInfo Control ANSI EDI).

(Level 3: Offset 104, len 1, comp 3 of 4, #1, DI 00000010
Data at offset 104 (':') was found to be of TYPE
X'0024' (Composite Delimiter Control ANSI EDI).

(Level 3: Offset 105, len 1, comp 4 of 4, #1, DI 00000011
Data at offset 105 ('~') was found to be of TYPE
X'0025' (Terminator Delimiter Control ANSI EDI).

(Level 2: Offset 3, len 103, comp 1 of 6, #1, DI 00000012
Data at offset 3 ('*00* *0') was found to be of TYPE
X'000F' (Partner Inbound ISA Segment Control ANSI EDI).

(Level 2: Offset 3, len 103, comp 1 of 6, #1, DI 00000013
Data at offset 3 ('*00* *0') was found to be of TYPE
X'000E' (Inbound ISA Segment Control ANSI EDI).

(Level 2: Offset 3, len 103, comp 1 of 6, #1, DI 00000013
Data at offset 3 ('*00* *0') was found to be of TYPE
X'000D' (ISA Segment Control ANSI EDI).

(Level 2: Offset 3, len 103, comp 1 of 6, #1, DI 00000013
Data at offset 3 ('*00* *0') was found to be of TYPE
X'000C' (Segment Control ANSI EDI).

(Level 2: Offset 3, len 103, comp 1 of 6, #1, DI 00000013
Type X'0009' (Partner X12 Inbound Interchange EDI) is known to exist.

(Level 2: Offset 106, len 0, comp 2 of 6, #1, DI 00000013
Data at offset 106 ('GS*RO*WLWH*AROF*...') does not match INITIATOR 'ISB'
of TYPE X'0026' (ISB Segment Control ANSI EDI).

(Level 2: Offset 106, len 0, comp 2 of 6, #1, DI 00000013
COMPONENT number 2 of TYPE X'0009' (Partner X12 Inbound Interchange EDI):
occurrence 1 is optional and does not exist.

(Level 2: Offset 106, len 0, comp 3 of 6, #1, DI 00000013
Data at offset 106 ('GS*RO*WLWH*AROF*...') does not match INITIATOR 'ISE'
of TYPE X'0028' (ISE Segment Control ANSI EDI).

(Level 2: Offset 106, len 0, comp 3 of 6, #1, DI 00000013
COMPONENT number 3 of TYPE X'0009' (Partner X12 Inbound Interchange EDI):
occurrence 1 is optional and does not exist.

(Level 2: Offset 106, len 0, comp 4 of 6, #1, DI 00000013
Data at offset 106 ('GS*RO*WLWH*AROF*...') does not match INITIATOR 'TA1'
of TYPE X'002C' (TA1 Segment Control ANSI EDI).

(Level 2: Offset 106, len 0, comp 4 of 6, #1, DI 00000013
COMPONENT number 4 of TYPE X'0009' (Partner X12 Inbound Interchange EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 109, len 0, comp 1 of 8, #1, DI 00000013
Type X'0035' (GS Segment V4010 ANSI EDI) is known to exist.

(Level 4: Offset 109, len 2, comp 1 of 8, #1, DI 00000013
Data at offset 109 ('RO') was found to be of TYPE
X'0037' (Funct'lIDCd Element V4010 ANSI EDI).

(Level 4: Offset 112, len 4, comp 2 of 8, #1, DI 00000014
Data at offset 112 ('WLWH') was found to be of TYPE
X'0038' (App'nSenderCd Element V4010 ANSI EDI).

(Level 4: Offset 117, len 4, comp 3 of 8, #1, DI 00000015
Data at offset 117 ('AROF') was found to be of TYPE
X'0039' (App'nRcv'rCd Element V4010 ANSI EDI).

(Level 4: Offset 122, len 8, comp 4 of 8, #1, DI 00000016
Data at offset 122 ('20051025') was found to be of TYPE
X'003A' (Date Element V4010 ANSI EDI).

(Level 4: Offset 131, len 4, comp 5 of 8, #1, DI 00000017
Data at offset 131 ('1300') was found to be of TYPE
X'003B' (Time Element V4010 ANSI EDI).

(Level 4: Offset 136, len 4, comp 6 of 8, #1, DI 00000018
Data at offset 136 ('0004') was found to be of TYPE
X'003C' (GroupCtrl# Element V4010 ANSI EDI).

(Level 4: Offset 141, len 1, comp 7 of 8, #1, DI 00000019
Data at offset 141 ('X') was found to be of TYPE
X'003D' (RspAgencyCd Element V4010 ANSI EDI).

(Level 4: Offset 143, len 6, comp 8 of 8, #1, DI 0000001A
Data at offset 143 ('004010') was found to be of TYPE
X'003E' (VersionReleaseIndustryIDCd Element V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001B
Data at offset 108 ('*RO*WLWH*AROF*20') was found to be of TYPE
X'0035' (GS Segment V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001C
Data at offset 108 ('*RO*WLWH*AROF*20') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001D
Type X'0032' (F4010 Inbound Partner Funct'lGroup ANSI EDI) is known to exist.

(Level 4: Offset 109, len 0, comp 1 of 8, #1, DI 00000013
Type X'0035' (GS Segment V4010 ANSI EDI) is known to exist.

(Level 4: Offset 109, len 2, comp 1 of 8, #1, DI 00000013
Data at offset 109 ('RO') was found to be of TYPE
X'0037' (Funct'lIDCd Element V4010 ANSI EDI).

(Level 4: Offset 112, len 4, comp 2 of 8, #1, DI 00000014
Data at offset 112 ('WLWH') was found to be of TYPE
X'0038' (App'nSenderCd Element V4010 ANSI EDI).

(Level 4: Offset 117, len 4, comp 3 of 8, #1, DI 00000015
Data at offset 117 ('AROF') was found to be of TYPE
X'0039' (App'nRcv'rCd Element V4010 ANSI EDI).

(Level 4: Offset 122, len 8, comp 4 of 8, #1, DI 00000016
Data at offset 122 ('20051025') was found to be of TYPE
X'003A' (Date Element V4010 ANSI EDI).

(Level 4: Offset 131, len 4, comp 5 of 8, #1, DI 00000017
Data at offset 131 ('1300') was found to be of TYPE
X'003B' (Time Element V4010 ANSI EDI).

(Level 4: Offset 136, len 4, comp 6 of 8, #1, DI 00000018
Data at offset 136 ('0004') was found to be of TYPE
X'003C' (GroupCtrl# Element V4010 ANSI EDI).

(Level 4: Offset 141, len 1, comp 7 of 8, #1, DI 00000019
Data at offset 141 ('X') was found to be of TYPE
X'003D' (RspAgencyCd Element V4010 ANSI EDI).

(Level 4: Offset 143, len 6, comp 8 of 8, #1, DI 0000001A
Data at offset 143 ('004010') was found to be of TYPE
X'003E' (VersionReleaseIndustryIDCd Element V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001B
Data at offset 108 ('*RO*WLWH*AROF*20') was found to be of TYPE
X'0035' (GS Segment V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001C
Data at offset 108 ('*RO*WLWH*AROF*20') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001D
Data at offset 108 ('*RO*WLWH*AROF*20...') failed COMPONENT RULE test
for component number 1, TYPE X'0044' (QO F4010 Inbound Partner Funct'lGroup ANSI EDI).

(Level 4: Offset 109, len 0, comp 1 of 8, #1, DI 00000013
Type X'0035' (GS Segment V4010 ANSI EDI) is known to exist.

(Level 4: Offset 109, len 2, comp 1 of 8, #1, DI 00000013
Data at offset 109 ('RO') was found to be of TYPE
X'0037' (Funct'lIDCd Element V4010 ANSI EDI).

(Level 4: Offset 112, len 4, comp 2 of 8, #1, DI 00000014
Data at offset 112 ('WLWH') was found to be of TYPE
X'0038' (App'nSenderCd Element V4010 ANSI EDI).

(Level 4: Offset 117, len 4, comp 3 of 8, #1, DI 00000015
Data at offset 117 ('AROF') was found to be of TYPE
X'0039' (App'nRcv'rCd Element V4010 ANSI EDI).

(Level 4: Offset 122, len 8, comp 4 of 8, #1, DI 00000016
Data at offset 122 ('20051025') was found to be of TYPE
X'003A' (Date Element V4010 ANSI EDI).

(Level 4: Offset 131, len 4, comp 5 of 8, #1, DI 00000017
Data at offset 131 ('1300') was found to be of TYPE
X'003B' (Time Element V4010 ANSI EDI).

(Level 4: Offset 136, len 4, comp 6 of 8, #1, DI 00000018
Data at offset 136 ('0004') was found to be of TYPE
X'003C' (GroupCtrl# Element V4010 ANSI EDI).

(Level 4: Offset 141, len 1, comp 7 of 8, #1, DI 00000019
Data at offset 141 ('X') was found to be of TYPE
X'003D' (RspAgencyCd Element V4010 ANSI EDI).

(Level 4: Offset 143, len 6, comp 8 of 8, #1, DI 0000001A
Data at offset 143 ('004010') was found to be of TYPE
X'003E' (VersionReleaseIndustryIDCd Element V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001B
Data at offset 108 ('*RO*WLWH*AROF*20') was found to be of TYPE
X'0035' (GS Segment V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001C
Data at offset 108 ('*RO*WLWH*AROF*20') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001D
Type X'0099' (RO F4010 Inbound Partner Funct'lGroup ANSI EDI) is known to exist.

(Level 5: Offset 153, len 0, comp 1 of 2, #1, DI 0000001D
Type X'0048' (ST Segment V4010 ANSI EDI) is known to exist.

(Level 5: Offset 153, len 3, comp 1 of 2, #1, DI 0000001D
Data at offset 153 ('301') was found to be of TYPE
X'0049' (TSIDCd Element V4010 ANSI EDI).

(Level 5: Offset 157, len 4, comp 2 of 2, #1, DI 0000001E
Data at offset 157 ('0004') was found to be of TYPE
X'004A' (TSCtrl# Element V4010 ANSI EDI).

(Level 4: Offset 152, len 9, comp 1 of 19, #1, DI 0000001F
Data at offset 152 ('*301*0004') was found to be of TYPE
X'0048' (ST Segment V4010 ANSI EDI).

(Level 4: Offset 152, len 9, comp 1 of 19, #1, DI 00000020
Data at offset 152 ('*301*0004') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 4: Offset 152, len 9, comp 1 of 19, #1, DI 00000021
Data at offset 152 ('*301*0004...') failed COMPONENT RULE test
for component number 1, TYPE X'009C' (#300 Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 5: Offset 153, len 0, comp 1 of 2, #1, DI 0000001D
Type X'0048' (ST Segment V4010 ANSI EDI) is known to exist.

(Level 5: Offset 153, len 3, comp 1 of 2, #1, DI 0000001D
Data at offset 153 ('301') was found to be of TYPE
X'0049' (TSIDCd Element V4010 ANSI EDI).

(Level 5: Offset 157, len 4, comp 2 of 2, #1, DI 0000001E
Data at offset 157 ('0004') was found to be of TYPE
X'004A' (TSCtrl# Element V4010 ANSI EDI).

(Level 4: Offset 152, len 9, comp 1 of 17, #1, DI 0000001F
Data at offset 152 ('*301*0004') was found to be of TYPE
X'0048' (ST Segment V4010 ANSI EDI).

(Level 4: Offset 152, len 9, comp 1 of 17, #1, DI 00000020
Data at offset 152 ('*301*0004') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 4: Offset 152, len 9, comp 1 of 17, #1, DI 00000021
Type X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI) is known to exist.

(Level 5: Offset 165, len 0, comp 1 of 4, #1, DI 00000021
Type X'009D' (B1 Segment V4010 ANSI EDI) is known to exist.

(Level 5: Offset 165, len 0, comp 1 of 4, #1, DI 00000021
COMPONENT number 1 of TYPE X'009D' (B1 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 5: Offset 166, len 7, comp 2 of 4, #1, DI 00000021
Data at offset 166 ('ABC5364') was found to be of TYPE
X'009F' (Ship'tID# Element V4010 ANSI EDI).

(Level 5: Offset 174, len 8, comp 3 of 4, #1, DI 00000022
Data at offset 174 ('20051122') was found to be of TYPE
X'003A' (Date Element V4010 ANSI EDI).

(Level 5: Offset 183, len 1, comp 4 of 4, #1, DI 00000023
Data at offset 183 ('A') was found to be of TYPE
X'00A0' (ReservationActionCd Element V4010 ANSI EDI).

(Level 4: Offset 164, len 20, comp 2 of 17, #1, DI 00000024
Data at offset 164 ('**ABC5364*200511') was found to be of TYPE
X'009D' (B1 Segment V4010 ANSI EDI).

(Level 4: Offset 164, len 20, comp 2 of 17, #1, DI 00000025
Data at offset 164 ('**ABC5364*200511') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 4: Offset 185, len 0, comp 3 of 17, #1, DI 00000026
Data at offset 185 ('Y3*USQMV308758*A...') does not match INITIATOR 'G61'
of TYPE X'00A1' (G61 Segment V4010 ANSI EDI).

(Level 4: Offset 185, len 0, comp 3 of 17, #1, DI 00000026
COMPONENT number 3 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 185, len 0, comp 4 of 17, #1, DI 00000026
Data at offset 185 ('Y3*USQMV308758*A...') does not match INITIATOR 'Y6'
of TYPE X'00A7' (Y6 Segment V4010 ANSI EDI).

(Level 4: Offset 185, len 0, comp 4 of 17, #1, DI 00000026
COMPONENT number 4 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 5: Offset 188, len 0, comp 1 of 10, #1, DI 00000026
Type X'012E' (Y3 Segment V4010 ANSI EDI) is known to exist.

(Level 5: Offset 188, len 11, comp 1 of 10, #1, DI 00000026
Data at offset 188 ('USQMV308758') was found to be of TYPE
X'012F' (Booking# Element V4010 ANSI EDI).

(Level 5: Offset 200, len 4, comp 2 of 10, #1, DI 00000027
Data at offset 200 ('AROF') was found to be of TYPE
X'009E' (SCAC Element V4010 ANSI EDI).

(Level 4: Offset 187, len 17, comp 5 of 17, #1, DI 00000028
Data at offset 187 ('*USQMV308758*ARO') was found to be of TYPE
X'012E' (Y3 Segment V4010 ANSI EDI).

(Level 4: Offset 187, len 17, comp 5 of 17, #1, DI 00000029
Data at offset 187 ('*USQMV308758*ARO') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 205, len 0, comp 1 of 2, #1, DI 0000002A
Data at offset 205 ('N1*FW*"R" COMPAN...') does not match INITIATOR 'Y4'
of TYPE X'0135' (Y4 Segment V4010 ANSI EDI).

(Level 5: Offset 205, len 0, comp 1 of 2, #1, DI 0000002A
COMPONENT number 1 of TYPE X'0134' (LoopY4 RO301 RO Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.

(Level 4: Offset 205, len 0, comp 6 of 17, #1, DI 0000002A
COMPONENT number 6 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 205, len 0, comp 7 of 17, #1, DI 0000002A
Data at offset 205 ('N1*FW*"R" COMPAN...') does not match INITIATOR 'N9'
of TYPE X'005B' (N9 Segment V4010 ANSI EDI).

(Level 4: Offset 205, len 0, comp 7 of 17, #1, DI 0000002A
COMPONENT number 7 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 205, len 0, comp 8 of 17, #1, DI 0000002A
Data at offset 205 ('N1*FW*"R" COMPAN...') does not match INITIATOR 'R2A'
of TYPE X'00C7' (R2A Segment V4010 ANSI EDI).

(Level 4: Offset 205, len 0, comp 8 of 17, #1, DI 0000002A
COMPONENT number 8 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 208, len 0, comp 1 of 4, #1, DI 0000002A
Type X'0063' (N1 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 208, len 2, comp 1 of 4, #1, DI 0000002A
Data at offset 208 ('FW') was found to be of TYPE
X'0064' (EntityIDCd Element V4010 ANSI EDI).

(Level 6: Offset 211, len 15, comp 2 of 4, #1, DI 0000002B
Data at offset 211 ('"R" COMPANY LTD') was found to be of TYPE
X'0065' (Name Element V4010 ANSI EDI).

(Level 5: Offset 207, len 19, comp 1 of 5, #1, DI 0000002C
Data at offset 207 ('*FW*"R" COMPANY ') was found to be of TYPE
X'0063' (N1 Segment V4010 ANSI EDI).

(Level 5: Offset 207, len 19, comp 1 of 5, #1, DI 0000002D
Data at offset 207 ('*FW*"R" COMPANY ') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 227, len 0, comp 2 of 5, #1, DI 0000002E
Data at offset 227 ('N3*123458 TALLIN...') does not match INITIATOR 'N2'
of TYPE X'00CD' (N2 Segment V4010 ANSI EDI).

(Level 5: Offset 227, len 0, comp 2 of 5, #1, DI 0000002E
COMPONENT number 2 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 230, len 0, comp 1 of 1, #1, DI 0000002E
Type X'00CE' (N3 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 230, len 26, comp 1 of 1, #1, DI 0000002E
Data at offset 230 ('123458 TALLINSKA') was found to be of TYPE
X'00CF' (AddressInfo Element V4010 ANSI EDI).

(Level 6: Offset 257, len 17, comp 1 of 1, #2, DI 0000002F
Data at offset 257 ('TEL:7-095-754744') was found to be of TYPE
X'00CF' (AddressInfo Element V4010 ANSI EDI).

(Level 5: Offset 229, len 45, comp 3 of 5, #1, DI 00000030
Data at offset 229 ('*123458 TALLINSK') was found to be of TYPE
X'00CE' (N3 Segment V4010 ANSI EDI).

(Level 5: Offset 229, len 45, comp 3 of 5, #1, DI 00000031
Data at offset 229 ('*123458 TALLINSK') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 275, len 0, comp 3 of 5, #2, DI 00000032
Data at offset 275 ('N4*MOSCOW***RU~N...') does not match INITIATOR 'N3'
of TYPE X'00CE' (N3 Segment V4010 ANSI EDI).

(Level 5: Offset 275, len 0, comp 3 of 5, #2, DI 00000032
COMPONENT number 3 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 2 is optional and does not exist.

(Level 6: Offset 278, len 0, comp 1 of 6, #1, DI 00000032
Type X'00D0' (N4 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 278, len 6, comp 1 of 6, #1, DI 00000032
Data at offset 278 ('MOSCOW') was found to be of TYPE
X'008F' (CityName Element V4010 ANSI EDI).

(Level 6: Offset 285, len 0, comp 2 of 6, #1, DI 00000033
COMPONENT number 2 of TYPE X'00D0' (N4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 286, len 0, comp 3 of 6, #1, DI 00000033
COMPONENT number 3 of TYPE X'00D0' (N4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 287, len 2, comp 4 of 6, #1, DI 00000033
Data at offset 287 ('RU') was found to be of TYPE
X'0070' (CountryCd Element V4010 ANSI EDI).

(Level 5: Offset 277, len 12, comp 4 of 5, #1, DI 00000034
Data at offset 277 ('*MOSCOW***RU') was found to be of TYPE
X'00D0' (N4 Segment V4010 ANSI EDI).

(Level 5: Offset 277, len 12, comp 4 of 5, #1, DI 00000035
Data at offset 277 ('*MOSCOW***RU') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 290, len 0, comp 5 of 5, #1, DI 00000036
Data at offset 290 ('N1*SH*SURFACE DE...') does not match INITIATOR 'G61'
of TYPE X'00A1' (G61 Segment V4010 ANSI EDI).

(Level 5: Offset 290, len 0, comp 5 of 5, #1, DI 00000036
COMPONENT number 5 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 205, len 85, comp 9 of 17, #1, DI 00000036
Data at offset 205 ('N1*FW*"R" COMPAN') was found to be of TYPE
X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI).

(Level 6: Offset 293, len 0, comp 1 of 4, #1, DI 00000037
Type X'0063' (N1 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 293, len 2, comp 1 of 4, #1, DI 00000037
Data at offset 293 ('SH') was found to be of TYPE
X'0064' (EntityIDCd Element V4010 ANSI EDI).

(Level 6: Offset 296, len 50, comp 2 of 4, #1, DI 00000038
Data at offset 296 ('SURFACE DEPLOYME') was found to be of TYPE
X'0065' (Name Element V4010 ANSI EDI).

(Level 5: Offset 292, len 54, comp 1 of 5, #1, DI 00000039
Data at offset 292 ('*SH*SURFACE DEPL') was found to be of TYPE
X'0063' (N1 Segment V4010 ANSI EDI).

(Level 5: Offset 292, len 54, comp 1 of 5, #1, DI 0000003A
Data at offset 292 ('*SH*SURFACE DEPL') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 347, len 0, comp 2 of 5, #1, DI 0000003B
Data at offset 347 ('N3*DO NOT USE~N4...') does not match INITIATOR 'N2'
of TYPE X'00CD' (N2 Segment V4010 ANSI EDI).

(Level 5: Offset 347, len 0, comp 2 of 5, #1, DI 0000003B
COMPONENT number 2 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 350, len 0, comp 1 of 1, #1, DI 0000003B
Type X'00CE' (N3 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 350, len 10, comp 1 of 1, #1, DI 0000003B
Data at offset 350 ('DO NOT USE') was found to be of TYPE
X'00CF' (AddressInfo Element V4010 ANSI EDI).

(Level 5: Offset 349, len 11, comp 3 of 5, #1, DI 0000003C
Data at offset 349 ('*DO NOT USE') was found to be of TYPE
X'00CE' (N3 Segment V4010 ANSI EDI).

(Level 5: Offset 349, len 11, comp 3 of 5, #1, DI 0000003D
Data at offset 349 ('*DO NOT USE') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 361, len 0, comp 3 of 5, #2, DI 0000003E
Data at offset 361 ('N4****US~R4*D*D*...') does not match INITIATOR 'N3'
of TYPE X'00CE' (N3 Segment V4010 ANSI EDI).

(Level 5: Offset 361, len 0, comp 3 of 5, #2, DI 0000003E
COMPONENT number 3 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 2 is optional and does not exist.

(Level 6: Offset 364, len 0, comp 1 of 6, #1, DI 0000003E
Type X'00D0' (N4 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 364, len 0, comp 1 of 6, #1, DI 0000003E
COMPONENT number 1 of TYPE X'00D0' (N4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 365, len 0, comp 2 of 6, #1, DI 0000003E
COMPONENT number 2 of TYPE X'00D0' (N4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 366, len 0, comp 3 of 6, #1, DI 0000003E
COMPONENT number 3 of TYPE X'00D0' (N4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 367, len 2, comp 4 of 6, #1, DI 0000003E
Data at offset 367 ('US') was found to be of TYPE
X'0070' (CountryCd Element V4010 ANSI EDI).

(Level 5: Offset 363, len 6, comp 4 of 5, #1, DI 0000003F
Data at offset 363 ('****US') was found to be of TYPE
X'00D0' (N4 Segment V4010 ANSI EDI).

(Level 5: Offset 363, len 6, comp 4 of 5, #1, DI 00000040
Data at offset 363 ('****US') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 370, len 0, comp 5 of 5, #1, DI 00000041
Data at offset 370 ('R4*D*D*USBAL*BAL...') does not match INITIATOR 'G61'
of TYPE X'00A1' (G61 Segment V4010 ANSI EDI).

(Level 5: Offset 370, len 0, comp 5 of 5, #1, DI 00000041
COMPONENT number 5 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 290, len 80, comp 9 of 17, #2, DI 00000041
Data at offset 290 ('N1*SH*SURFACE DE') was found to be of TYPE
X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI).

(Level 5: Offset 370, len 0, comp 1 of 5, #1, DI 00000042
Data at offset 370 ('R4*D*D*USBAL*BAL...') does not match INITIATOR 'N1'
of TYPE X'0063' (N1 Segment V4010 ANSI EDI).

(Level 5: Offset 370, len 0, comp 1 of 5, #1, DI 00000042
COMPONENT number 1 of TYPE X'0136' (LoopN1 RO301 RO Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.

(Level 4: Offset 370, len 0, comp 9 of 17, #3, DI 00000042
COMPONENT number 9 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 3 is optional and does not exist.

(Level 6: Offset 373, len 0, comp 1 of 7, #1, DI 00000042
Type X'0080' (R4 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 373, len 1, comp 1 of 7, #1, DI 00000042
Data at offset 373 ('D') was found to be of TYPE
X'0081' (PortFunctionCd Element V4010 ANSI EDI).

(Level 7: Offset 375, len 1, comp 1 of 2, #1, DI 00000043
Data at offset 375 ('D') was found to be of TYPE
X'0059' (LocQual'r Element V4010 ANSI EDI).

(Level 7: Offset 377, len 5, comp 2 of 2, #1, DI 00000044
Data at offset 377 ('USBAL') was found to be of TYPE
X'0058' (LocID Element V4010 ANSI EDI).

(Level 6: Offset 375, len 7, comp 2 of 7, #1, DI 00000045
Data at offset 375 ('D*USBAL') was found to be of TYPE
X'0082' (Loc MComposite V4010 ANSI EDI).

(Level 6: Offset 383, len 13, comp 3 of 7, #1, DI 00000046
Data at offset 383 ('BALTIMORE, MD') was found to be of TYPE
X'0083' (PortName Element V4010 ANSI EDI).

(Level 6: Offset 397, len 0, comp 4 of 7, #1, DI 00000047
COMPONENT number 4 of TYPE X'0080' (R4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 398, len 6, comp 5 of 7, #1, DI 00000047
Data at offset 398 ('USBAL1') was found to be of TYPE
X'0084' (TerminalName Element V4010 ANSI EDI).

(Level 5: Offset 372, len 32, comp 1 of 2, #1, DI 00000048
Data at offset 372 ('*D*D*USBAL*BALTI') was found to be of TYPE
X'0080' (R4 Segment V4010 ANSI EDI).

(Level 5: Offset 372, len 32, comp 1 of 2, #1, DI 00000049
Data at offset 372 ('*D*D*USBAL*BALTI') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 405, len 0, comp 2 of 2, #1, DI 0000004A
Data at offset 405 ('R4*L*K*DEBRH*BRE...') does not match INITIATOR 'DTM'
of TYPE X'0087' (DTM Segment V4010 ANSI EDI).

(Level 5: Offset 405, len 0, comp 2 of 2, #1, DI 0000004A
COMPONENT number 2 of TYPE X'0137' (LoopR4 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 370, len 35, comp 10 of 17, #1, DI 0000004A
Data at offset 370 ('R4*D*D*USBAL*BAL') was found to be of TYPE
X'0137' (LoopR4 RO301 RO Inbound Partner Set V4010 ANSI EDI).

(Level 6: Offset 408, len 0, comp 1 of 7, #1, DI 0000004B
Type X'0080' (R4 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 408, len 1, comp 1 of 7, #1, DI 0000004B
Data at offset 408 ('L') was found to be of TYPE
X'0081' (PortFunctionCd Element V4010 ANSI EDI).

(Level 7: Offset 410, len 1, comp 1 of 2, #1, DI 0000004C
Data at offset 410 ('K') was found to be of TYPE
X'0059' (LocQual'r Element V4010 ANSI EDI).

(Level 7: Offset 412, len 5, comp 2 of 2, #1, DI 0000004D
Data at offset 412 ('DEBRH') was found to be of TYPE
X'0058' (LocID Element V4010 ANSI EDI).

(Level 6: Offset 410, len 7, comp 2 of 7, #1, DI 0000004E
Data at offset 410 ('K*DEBRH') was found to be of TYPE
X'0082' (Loc MComposite V4010 ANSI EDI).

(Level 6: Offset 418, len 11, comp 3 of 7, #1, DI 0000004F
Data at offset 418 ('BREMERHAVEN') was found to be of TYPE
X'0083' (PortName Element V4010 ANSI EDI).

(Level 6: Offset 430, len 0, comp 4 of 7, #1, DI 00000050
COMPONENT number 4 of TYPE X'0080' (R4 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 431, len 6, comp 5 of 7, #1, DI 00000050
Data at offset 431 ('DEBRH2') was found to be of TYPE
X'0084' (TerminalName Element V4010 ANSI EDI).

(Level 5: Offset 407, len 30, comp 1 of 2, #1, DI 00000051
Data at offset 407 ('*L*K*DEBRH*BREME') was found to be of TYPE
X'0080' (R4 Segment V4010 ANSI EDI).

(Level 5: Offset 407, len 30, comp 1 of 2, #1, DI 00000052
Data at offset 407 ('*L*K*DEBRH*BREME') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 438, len 0, comp 2 of 2, #1, DI 00000053
Data at offset 438 ('LX*1~L0*1***2571...') does not match INITIATOR 'DTM'
of TYPE X'0087' (DTM Segment V4010 ANSI EDI).

(Level 5: Offset 438, len 0, comp 2 of 2, #1, DI 00000053
COMPONENT number 2 of TYPE X'0137' (LoopR4 RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 405, len 33, comp 10 of 17, #2, DI 00000053
Data at offset 405 ('R4*L*K*DEBRH*BRE') was found to be of TYPE
X'0137' (LoopR4 RO301 RO Inbound Partner Set V4010 ANSI EDI).

(Level 5: Offset 438, len 0, comp 1 of 2, #1, DI 00000054
Data at offset 438 ('LX*1~L0*1***2571...') does not match INITIATOR 'R4'
of TYPE X'0080' (R4 Segment V4010 ANSI EDI).

(Level 5: Offset 438, len 0, comp 1 of 2, #1, DI 00000054
COMPONENT number 1 of TYPE X'0137' (LoopR4 RO301 RO Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.

(Level 4: Offset 438, len 0, comp 10 of 17, #3, DI 00000054
COMPONENT number 10 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 3 is optional and does not exist.

(Level 4: Offset 438, len 0, comp 11 of 17, #1, DI 00000054
Data at offset 438 ('LX*1~L0*1***2571...') does not match INITIATOR 'W09'
of TYPE X'00BF' (W09 Segment V4010 ANSI EDI).

(Level 4: Offset 438, len 0, comp 11 of 17, #1, DI 00000054
COMPONENT number 11 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 438, len 0, comp 12 of 17, #1, DI 00000054
Data at offset 438 ('LX*1~L0*1***2571...') does not match INITIATOR 'H3'
of TYPE X'00D3' (H3 Segment V4010 ANSI EDI).

(Level 4: Offset 438, len 0, comp 12 of 17, #1, DI 00000054
COMPONENT number 12 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 438, len 0, comp 13 of 17, #1, DI 00000054
Data at offset 438 ('LX*1~L0*1***2571...') does not match INITIATOR 'EA'
of TYPE X'00D8' (EA Segment V4010 ANSI EDI).

(Level 4: Offset 438, len 0, comp 13 of 17, #1, DI 00000054
COMPONENT number 13 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 441, len 0, comp 1 of 1, #1, DI 00000054
Type X'00E0' (LX Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 441, len 1, comp 1 of 1, #1, DI 00000054
Data at offset 441 ('1') was found to be of TYPE
X'00E1' (Assigned# Element V4010 ANSI EDI).

(Level 5: Offset 440, len 2, comp 1 of 9, #1, DI 00000055
Data at offset 440 ('*1') was found to be of TYPE
X'00E0' (LX Segment V4010 ANSI EDI).

(Level 5: Offset 440, len 2, comp 1 of 9, #1, DI 00000056
Data at offset 440 ('*1') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 443, len 0, comp 2 of 9, #1, DI 00000057
Data at offset 443 ('L0*1***2571*G*22...') does not match INITIATOR 'N7'
of TYPE X'00E2' (N7 Segment V4010 ANSI EDI).

(Level 5: Offset 443, len 0, comp 2 of 9, #1, DI 00000057
COMPONENT number 2 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 5: Offset 443, len 0, comp 3 of 9, #1, DI 00000057
Data at offset 443 ('L0*1***2571*G*22...') does not match INITIATOR 'W09'
of TYPE X'00BF' (W09 Segment V4010 ANSI EDI).

(Level 5: Offset 443, len 0, comp 3 of 9, #1, DI 00000057
COMPONENT number 3 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 5: Offset 443, len 0, comp 4 of 9, #1, DI 00000057
Data at offset 443 ('L0*1***2571*G*22...') does not match INITIATOR 'K1'
of TYPE X'012C' (K1 Segment V4010 ANSI EDI).

(Level 5: Offset 443, len 0, comp 4 of 9, #1, DI 00000057
COMPONENT number 4 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 446, len 0, comp 1 of 11, #1, DI 00000057
Type X'00F1' (L0 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 446, len 1, comp 1 of 11, #1, DI 00000057
Data at offset 446 ('1') was found to be of TYPE
X'00F2' (LadingLineItem# Element V4010 ANSI EDI).

(Level 6: Offset 449, len 0, comp 2 of 11, #1, DI 00000058
COMPONENT number 2 of TYPE X'00F1' (L0 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 7: Offset 450, len 4, comp 1 of 2, #1, DI 00000058
Data at offset 450 ('2571') was found to be of TYPE
X'0072' (Wt Element V4010 ANSI EDI).

(Level 7: Offset 455, len 1, comp 2 of 2, #1, DI 00000059
Data at offset 455 ('G') was found to be of TYPE
X'0073' (WtQual'r Element V4010 ANSI EDI).

(Level 6: Offset 450, len 6, comp 3 of 11, #1, DI 0000005A
Data at offset 450 ('2571*G') was found to be of TYPE
X'00E3' (WtWtQual'r MComposite V4010 ANSI EDI).

(Level 7: Offset 457, len 6, comp 1 of 2, #1, DI 0000005B
Data at offset 457 ('22.121') was found to be of TYPE
X'0078' (Vol Element V4010 ANSI EDI).

(Level 7: Offset 464, len 1, comp 2 of 2, #1, DI 0000005C
Data at offset 464 ('E') was found to be of TYPE
X'0079' (VolUnitQual'r Element V4010 ANSI EDI).

(Level 6: Offset 457, len 8, comp 4 of 11, #1, DI 0000005D
Data at offset 457 ('22.121*E') was found to be of TYPE
X'0077' (VolUnitQual MComposite V4010 ANSI EDI).

(Level 7: Offset 466, len 1, comp 1 of 2, #1, DI 0000005E
Data at offset 466 ('1') was found to be of TYPE
X'0071' (LadingQty Element V4010 ANSI EDI).

(Level 7: Offset 468, len 3, comp 2 of 2, #1, DI 0000005F
Data at offset 468 ('VEH') was found to be of TYPE
X'00F7' (Pkg'gFormCd Element V4010 ANSI EDI).

(Level 6: Offset 466, len 5, comp 5 of 11, #1, DI 00000060
Data at offset 466 ('1*VEH') was found to be of TYPE
X'00F6' (LadingQtyPkg'gForm MComposite V4010 ANSI EDI).

(Level 6: Offset 472, len 0, comp 6 of 11, #1, DI 00000061
COMPONENT number 6 of TYPE X'00F1' (L0 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 473, len 1, comp 7 of 11, #1, DI 00000061
Data at offset 473 ('K') was found to be of TYPE
X'007A' (WtUnitCd Element V4010 ANSI EDI).

(Level 5: Offset 445, len 29, comp 5 of 9, #1, DI 00000062
Data at offset 445 ('*1***2571*G*22.1') was found to be of TYPE
X'00F1' (L0 Segment V4010 ANSI EDI).

(Level 5: Offset 445, len 29, comp 5 of 9, #1, DI 00000063
Data at offset 445 ('*1***2571*G*22.1') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 6: Offset 478, len 0, comp 1 of 8, #1, DI 00000064
Type X'00FA' (L5 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 478, len 1, comp 1 of 8, #1, DI 00000064
Data at offset 478 ('1') was found to be of TYPE
X'00F2' (LadingLineItem# Element V4010 ANSI EDI).

(Level 6: Offset 480, len 16, comp 2 of 8, #1, DI 00000065
Data at offset 480 ('POV AIRCRAFT NOS') was found to be of TYPE
X'00FB' (LadingDesc'n Element V4010 ANSI EDI).

(Level 6: Offset 498, len 0, comp 3 of 8, #1, DI 00000066
COMPONENT number 3 of TYPE X'00FA' (L5 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 499, len 0, comp 4 of 8, #1, DI 00000066
COMPONENT number 4 of TYPE X'00FA' (L5 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 500, len 16, comp 5 of 8, #1, DI 00000066
Data at offset 500 ('AWHU900D00050XXX') was found to be of TYPE
X'0102' (MarksAnd# Element V4010 ANSI EDI).

(Level 5: Offset 477, len 39, comp 6 of 9, #1, DI 00000067
Data at offset 477 ('*1*POV AIRCRAFT ') was found to be of TYPE
X'00FA' (L5 Segment V4010 ANSI EDI).

(Level 5: Offset 477, len 39, comp 6 of 9, #1, DI 00000068
Data at offset 477 ('*1*POV AIRCRAFT ') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 6: Offset 520, len 0, comp 1 of 6, #1, DI 00000069
Type X'0106' (L4 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 520, len 7, comp 1 of 6, #1, DI 00000069
Data at offset 520 ('421.600') was found to be of TYPE
X'0098' (Length Element V4010 ANSI EDI).

(Level 6: Offset 528, len 7, comp 2 of 6, #1, DI 0000006A
Data at offset 528 ('210.800') was found to be of TYPE
X'00EE' (Width Element V4010 ANSI EDI).

(Level 6: Offset 536, len 7, comp 3 of 6, #1, DI 0000006B
Data at offset 536 ('248.900') was found to be of TYPE
X'00ED' (Height Element V4010 ANSI EDI).

(Level 6: Offset 544, len 1, comp 4 of 6, #1, DI 0000006C
Data at offset 544 ('C') was found to be of TYPE
X'0107' (Meas'tUnitQual'r Element V4010 ANSI EDI).

(Level 5: Offset 519, len 26, comp 7 of 9, #1, DI 0000006D
Data at offset 519 ('*421.600*210.800') was found to be of TYPE
X'0106' (L4 Segment V4010 ANSI EDI).

(Level 5: Offset 519, len 26, comp 7 of 9, #1, DI 0000006E
Data at offset 519 ('*421.600*210.800') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 546, len 0, comp 8 of 9, #1, DI 0000006F
Data at offset 546 ('LX*2~L0*2***2571...') does not match INITIATOR 'L1'
of TYPE X'0109' (L1 Segment V4010 ANSI EDI).

(Level 5: Offset 546, len 0, comp 8 of 9, #1, DI 0000006F
COMPONENT number 8 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 546, len 0, comp 1 of 2, #1, DI 0000006F
Data at offset 546 ('LX*2~L0*2***2571...') does not match INITIATOR 'H1'
of TYPE X'011D' (H1 Segment V4010 ANSI EDI).

(Level 6: Offset 546, len 0, comp 1 of 2, #1, DI 0000006F
COMPONENT number 1 of TYPE X'0139' (LoopH1 RO301 RO Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.

(Level 5: Offset 546, len 0, comp 9 of 9, #1, DI 0000006F
COMPONENT number 9 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 438, len 108, comp 14 of 17, #1, DI 0000006F
Data at offset 438 ('LX*1~L0*1***2571') was found to be of TYPE
X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI).

(Level 6: Offset 549, len 0, comp 1 of 1, #1, DI 00000070
Type X'00E0' (LX Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 549, len 1, comp 1 of 1, #1, DI 00000070
Data at offset 549 ('2') was found to be of TYPE
X'00E1' (Assigned# Element V4010 ANSI EDI).

(Level 5: Offset 548, len 2, comp 1 of 9, #1, DI 00000071
Data at offset 548 ('*2') was found to be of TYPE
X'00E0' (LX Segment V4010 ANSI EDI).

(Level 5: Offset 548, len 2, comp 1 of 9, #1, DI 00000072
Data at offset 548 ('*2') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 551, len 0, comp 2 of 9, #1, DI 00000073
Data at offset 551 ('L0*2***2571*G*22...') does not match INITIATOR 'N7'
of TYPE X'00E2' (N7 Segment V4010 ANSI EDI).

(Level 5: Offset 551, len 0, comp 2 of 9, #1, DI 00000073
COMPONENT number 2 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 5: Offset 551, len 0, comp 3 of 9, #1, DI 00000073
Data at offset 551 ('L0*2***2571*G*22...') does not match INITIATOR 'W09'
of TYPE X'00BF' (W09 Segment V4010 ANSI EDI).

(Level 5: Offset 551, len 0, comp 3 of 9, #1, DI 00000073
COMPONENT number 3 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 5: Offset 551, len 0, comp 4 of 9, #1, DI 00000073
Data at offset 551 ('L0*2***2571*G*22...') does not match INITIATOR 'K1'
of TYPE X'012C' (K1 Segment V4010 ANSI EDI).

(Level 5: Offset 551, len 0, comp 4 of 9, #1, DI 00000073
COMPONENT number 4 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 554, len 0, comp 1 of 11, #1, DI 00000073
Type X'00F1' (L0 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 554, len 1, comp 1 of 11, #1, DI 00000073
Data at offset 554 ('2') was found to be of TYPE
X'00F2' (LadingLineItem# Element V4010 ANSI EDI).

(Level 6: Offset 557, len 0, comp 2 of 11, #1, DI 00000074
COMPONENT number 2 of TYPE X'00F1' (L0 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 7: Offset 558, len 4, comp 1 of 2, #1, DI 00000074
Data at offset 558 ('2571') was found to be of TYPE
X'0072' (Wt Element V4010 ANSI EDI).

(Level 7: Offset 563, len 1, comp 2 of 2, #1, DI 00000075
Data at offset 563 ('G') was found to be of TYPE
X'0073' (WtQual'r Element V4010 ANSI EDI).

(Level 6: Offset 558, len 6, comp 3 of 11, #1, DI 00000076
Data at offset 558 ('2571*G') was found to be of TYPE
X'00E3' (WtWtQual'r MComposite V4010 ANSI EDI).

(Level 7: Offset 565, len 6, comp 1 of 2, #1, DI 00000077
Data at offset 565 ('22.121') was found to be of TYPE
X'0078' (Vol Element V4010 ANSI EDI).

(Level 7: Offset 572, len 1, comp 2 of 2, #1, DI 00000078
Data at offset 572 ('E') was found to be of TYPE
X'0079' (VolUnitQual'r Element V4010 ANSI EDI).

(Level 6: Offset 565, len 8, comp 4 of 11, #1, DI 00000079
Data at offset 565 ('22.121*E') was found to be of TYPE
X'0077' (VolUnitQual MComposite V4010 ANSI EDI).

(Level 7: Offset 574, len 1, comp 1 of 2, #1, DI 0000007A
Data at offset 574 ('1') was found to be of TYPE
X'0071' (LadingQty Element V4010 ANSI EDI).

(Level 7: Offset 576, len 3, comp 2 of 2, #1, DI 0000007B
Data at offset 576 ('VEH') was found to be of TYPE
X'00F7' (Pkg'gFormCd Element V4010 ANSI EDI).

(Level 6: Offset 574, len 5, comp 5 of 11, #1, DI 0000007C
Data at offset 574 ('1*VEH') was found to be of TYPE
X'00F6' (LadingQtyPkg'gForm MComposite V4010 ANSI EDI).

(Level 6: Offset 580, len 0, comp 6 of 11, #1, DI 0000007D
COMPONENT number 6 of TYPE X'00F1' (L0 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 581, len 1, comp 7 of 11, #1, DI 0000007D
Data at offset 581 ('K') was found to be of TYPE
X'007A' (WtUnitCd Element V4010 ANSI EDI).

(Level 5: Offset 553, len 29, comp 5 of 9, #1, DI 0000007E
Data at offset 553 ('*2***2571*G*22.1') was found to be of TYPE
X'00F1' (L0 Segment V4010 ANSI EDI).

(Level 5: Offset 553, len 29, comp 5 of 9, #1, DI 0000007F
Data at offset 553 ('*2***2571*G*22.1') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 6: Offset 586, len 0, comp 1 of 8, #1, DI 00000080
Type X'00FA' (L5 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 586, len 1, comp 1 of 8, #1, DI 00000080
Data at offset 586 ('1') was found to be of TYPE
X'00F2' (LadingLineItem# Element V4010 ANSI EDI).

(Level 6: Offset 588, len 16, comp 2 of 8, #1, DI 00000081
Data at offset 588 ('POV AIRCRAFT NOS') was found to be of TYPE
X'00FB' (LadingDesc'n Element V4010 ANSI EDI).

(Level 6: Offset 606, len 0, comp 3 of 8, #1, DI 00000082
COMPONENT number 3 of TYPE X'00FA' (L5 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 607, len 0, comp 4 of 8, #1, DI 00000082
COMPONENT number 4 of TYPE X'00FA' (L5 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 6: Offset 608, len 16, comp 5 of 8, #1, DI 00000082
Data at offset 608 ('AWHU900D00550XXX') was found to be of TYPE
X'0102' (MarksAnd# Element V4010 ANSI EDI).

(Level 5: Offset 585, len 39, comp 6 of 9, #1, DI 00000083
Data at offset 585 ('*1*POV AIRCRAFT ') was found to be of TYPE
X'00FA' (L5 Segment V4010 ANSI EDI).

(Level 5: Offset 585, len 39, comp 6 of 9, #1, DI 00000084
Data at offset 585 ('*1*POV AIRCRAFT ') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 6: Offset 628, len 0, comp 1 of 6, #1, DI 00000085
Type X'0106' (L4 Segment V4010 ANSI EDI) is known to exist.

(Level 6: Offset 628, len 7, comp 1 of 6, #1, DI 00000085
Data at offset 628 ('421.600') was found to be of TYPE
X'0098' (Length Element V4010 ANSI EDI).

(Level 6: Offset 636, len 7, comp 2 of 6, #1, DI 00000086
Data at offset 636 ('210.800') was found to be of TYPE
X'00EE' (Width Element V4010 ANSI EDI).

(Level 6: Offset 644, len 7, comp 3 of 6, #1, DI 00000087
Data at offset 644 ('248.900') was found to be of TYPE
X'00ED' (Height Element V4010 ANSI EDI).

(Level 6: Offset 652, len 1, comp 4 of 6, #1, DI 00000088
Data at offset 652 ('C') was found to be of TYPE
X'0107' (Meas'tUnitQual'r Element V4010 ANSI EDI).

(Level 5: Offset 627, len 26, comp 7 of 9, #1, DI 00000089
Data at offset 627 ('*421.600*210.800') was found to be of TYPE
X'0106' (L4 Segment V4010 ANSI EDI).

(Level 5: Offset 627, len 26, comp 7 of 9, #1, DI 0000008A
Data at offset 627 ('*421.600*210.800') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 5: Offset 654, len 0, comp 8 of 9, #1, DI 0000008B
Data at offset 654 ('V1*TOG*TOURCOING...') does not match INITIATOR 'L1'
of TYPE X'0109' (L1 Segment V4010 ANSI EDI).

(Level 5: Offset 654, len 0, comp 8 of 9, #1, DI 0000008B
COMPONENT number 8 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 6: Offset 654, len 0, comp 1 of 2, #1, DI 0000008B
Data at offset 654 ('V1*TOG*TOURCOING...') does not match INITIATOR 'H1'
of TYPE X'011D' (H1 Segment V4010 ANSI EDI).

(Level 6: Offset 654, len 0, comp 1 of 2, #1, DI 0000008B
COMPONENT number 1 of TYPE X'0139' (LoopH1 RO301 RO Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.

(Level 5: Offset 654, len 0, comp 9 of 9, #1, DI 0000008B
COMPONENT number 9 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 4: Offset 546, len 108, comp 14 of 17, #2, DI 0000008B
Data at offset 546 ('LX*2~L0*2***2571') was found to be of TYPE
X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI).

(Level 5: Offset 654, len 0, comp 1 of 9, #1, DI 0000008C
Data at offset 654 ('V1*TOG*TOURCOING...') does not match INITIATOR 'LX'
of TYPE X'00E0' (LX Segment V4010 ANSI EDI).

(Level 5: Offset 654, len 0, comp 1 of 9, #1, DI 0000008C
COMPONENT number 1 of TYPE X'0138' (LoopLX RO301 RO Inbound Partner Set V4010 ANSI EDI)
is required, but does not exist.

(Level 4: Offset 654, len 0, comp 14 of 17, #3, DI 0000008C
COMPONENT number 14 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 3 is optional and does not exist.

(Level 5: Offset 657, len 0, comp 1 of 9, #1, DI 0000008C
Type X'0129' (V1 Segment V4010 ANSI EDI) is known to exist.

(Level 5: Offset 657, len 3, comp 1 of 9, #1, DI 0000008C
Data at offset 657 ('TOG') was found to be of TYPE
X'006F' (VesselCd Element V4010 ANSI EDI).

(Level 5: Offset 661, len 9, comp 2 of 9, #1, DI 0000008D
Data at offset 661 ('TOURCOING') was found to be of TYPE
X'0076' (VesselName Element V4010 ANSI EDI).

(Level 5: Offset 671, len 0, comp 3 of 9, #1, DI 0000008E
COMPONENT number 3 of TYPE X'0129' (V1 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 5: Offset 672, len 5, comp 4 of 9, #1, DI 0000008E
Data at offset 672 ('EF528') was found to be of TYPE
X'0074' (FlightVoyage# Element V4010 ANSI EDI).

(Level 5: Offset 678, len 0, comp 5 of 9, #1, DI 0000008F
COMPONENT number 5 of TYPE X'0129' (V1 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 5: Offset 679, len 0, comp 6 of 9, #1, DI 0000008F
COMPONENT number 6 of TYPE X'0129' (V1 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 5: Offset 680, len 0, comp 7 of 9, #1, DI 0000008F
COMPONENT number 7 of TYPE X'0129' (V1 Segment V4010 ANSI EDI):
occurrence 1 is optional and has no content.

(Level 5: Offset 681, len 1, comp 8 of 9, #1, DI 0000008F
Data at offset 681 ('Z') was found to be of TYPE
X'0075' (VesselCdQual'r Element V4010 ANSI EDI).

(Level 4: Offset 656, len 26, comp 15 of 17, #1, DI 00000090
Data at offset 656 ('*TOG*TOURCOING**') was found to be of TYPE
X'0129' (V1 Segment V4010 ANSI EDI).

(Level 4: Offset 656, len 26, comp 15 of 17, #1, DI 00000091
Data at offset 656 ('*TOG*TOURCOING**') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 4: Offset 683, len 0, comp 15 of 17, #2, DI 00000092
Data at offset 683 ('SE*21*0004~GE*1*...') does not match INITIATOR 'V1'
of TYPE X'0129' (V1 Segment V4010 ANSI EDI).

(Level 4: Offset 683, len 0, comp 15 of 17, #2, DI 00000092
COMPONENT number 15 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 2 is optional and does not exist.

(Level 4: Offset 683, len 0, comp 16 of 17, #1, DI 00000092
Data at offset 683 ('SE*21*0004~GE*1*...') does not match INITIATOR 'V9'
of TYPE X'008C' (V9 Segment V4010 ANSI EDI).

(Level 4: Offset 683, len 0, comp 16 of 17, #1, DI 00000092
COMPONENT number 16 of TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI):
occurrence 1 is optional and does not exist.

(Level 5: Offset 686, len 0, comp 1 of 2, #1, DI 00000092
Type X'006B' (SE Segment V4010 ANSI EDI) is known to exist.

(Level 5: Offset 686, len 2, comp 1 of 2, #1, DI 00000092
Data at offset 686 ('21') was found to be of TYPE
X'006C' (InclSegments Element V4010 ANSI EDI).

(Level 5: Offset 689, len 4, comp 2 of 2, #1, DI 00000093
Data at offset 689 ('0004') was found to be of TYPE
X'004A' (TSCtrl# Element V4010 ANSI EDI).

(Level 4: Offset 685, len 8, comp 17 of 17, #1, DI 00000094
Data at offset 685 ('*21*0004') was found to be of TYPE
X'006B' (SE Segment V4010 ANSI EDI).

(Level 4: Offset 685, len 8, comp 17 of 17, #1, DI 00000095
Data at offset 685 ('*21*0004') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 3: Offset 150, len 544, comp 2 of 3, #1, DI 00000096
Data at offset 150 ('ST*301*0004~B1**') was found to be of TYPE
X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 3: Offset 150, len 544, comp 2 of 3, #1, DI 00000097
Data at offset 150 ('ST*301*0004~B1**') was found to be of TYPE
X'009B' (Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 4: Offset 694, len 0, comp 1 of 19, #1, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') does not match INITIATOR 'ST'
of TYPE X'0048' (ST Segment V4010 ANSI EDI).

(Level 4: Offset 694, len 0, comp 1 of 19, #1, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') failed COMPONENT RULE test
for component number 1, TYPE X'009C' (#300 Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 4: Offset 694, len 0, comp 1 of 17, #1, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') does not match INITIATOR 'ST'
of TYPE X'0048' (ST Segment V4010 ANSI EDI).

(Level 4: Offset 694, len 0, comp 1 of 17, #1, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') failed COMPONENT RULE test
for component number 1, TYPE X'012D' (#301 Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 4: Offset 694, len 0, comp 1 of 6, #1, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') does not match INITIATOR 'ST'
of TYPE X'0048' (ST Segment V4010 ANSI EDI).

(Level 4: Offset 694, len 0, comp 1 of 6, #1, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') failed COMPONENT RULE test
for component number 1, TYPE X'013A' (#303 Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 3: Offset 694, len 0, comp 2 of 3, #2, DI 00000098
Data at offset 694 ('GE*1*0004~IEA*1*...') failed PARTITIONing for TYPE
X'009B' (Transaction RO Inbound Partner Set V4010 ANSI EDI).

(Level 3: Offset 694, len 0, comp 2 of 3, #2, DI 00000098
COMPONENT number 2 of TYPE X'0099' (RO F4010 Inbound Partner Funct'lGroup ANSI EDI):
occurrence 2 is optional and does not exist.

(Level 4: Offset 697, len 0, comp 1 of 2, #1, DI 00000098
Type X'0042' (GE Segment V4010 ANSI EDI) is known to exist.

(Level 4: Offset 697, len 1, comp 1 of 2, #1, DI 00000098
Data at offset 697 ('1') was found to be of TYPE
X'0043' (TSIncl Element V4010 ANSI EDI).

(Level 4: Offset 699, len 4, comp 2 of 2, #1, DI 00000099
Data at offset 699 ('0004') was found to be of TYPE
X'003C' (GroupCtrl# Element V4010 ANSI EDI).

(Level 3: Offset 696, len 7, comp 3 of 3, #1, DI 0000009A
Data at offset 696 ('*1*0004') was found to be of TYPE
X'0042' (GE Segment V4010 ANSI EDI).

(Level 3: Offset 696, len 7, comp 3 of 3, #1, DI 0000009B
Data at offset 696 ('*1*0004') was found to be of TYPE
X'0034' (Segment V4010 ANSI EDI).

(Level 2: Offset 106, len 598, comp 5 of 6, #1, DI 0000009C
Data at offset 106 ('GS*RO*WLWH*AROF*') was found to be of TYPE
X'0099' (RO F4010 Inbound Partner Funct'lGroup ANSI EDI).

(Level 2: Offset 106, len 598, comp 5 of 6, #1, DI 0000009D
Data at offset 106 ('GS*RO*WLWH*AROF*') was found to be of TYPE
X'0032' (F4010 Inbound Partner Funct'lGroup ANSI EDI).

(Level 2: Offset 106, len 598, comp 5 of 6, #1, DI 0000009E
Data at offset 106 ('GS*RO*WLWH*AROF*') was found to be of TYPE
X'0031' (Inbound Partner Funct'lGroup ANSI EDI).

(Level 3: Offset 704, len 0, comp 1 of 3, #1, DI 0000009F
Data at offset 704 ('IEA*1*000000004~...') does not match INITIATOR 'GS'
of TYPE X'0035' (GS Segment V4010 ANSI EDI).

(Level 3: Offset 704, len 0, comp 1 of 3, #1, DI 0000009F
Data at offset 704 ('IEA*1*000000004~...') failed COMPONENT RULE test
for component number 1, TYPE X'0032' (F4010 Inbound Partner Funct'lGroup ANSI EDI).

(Level 2: Offset 704, len 0, comp 5 of 6, #2, DI 0000009F
Data at offset 704 ('IEA*1*000000004~...') failed PARTITIONing for TYPE
X'0031' (Inbound Partner Funct'lGroup ANSI EDI).

(Level 2: Offset 704, len 0, comp 5 of 6, #2, DI 0000009F
COMPONENT number 5 of TYPE X'0009' (Partner X12 Inbound Interchange EDI):
occurrence 2 is optional and does not exist.

(Level 3: Offset 708, len 0, comp 1 of 2, #1, DI 0000009F
Type X'013C' (IEA Segment Control ANSI EDI) is known to exist.

(Level 3: Offset 708, len 1, comp 1 of 2, #1, DI 0000009F
Data at offset 708 ('1') was found to be of TYPE
X'013D' (#InclFunct'lGroups Element Control ANSI EDI).

(Level 3: Offset 710, len 9, comp 2 of 2, #1, DI 000000A0
Data at offset 710 ('000000004') was found to be of TYPE
X'0021' (InterchangeCtrl# Element Control ANSI EDI).

(Level 2: Offset 707, len 12, comp 6 of 6, #1, DI 000000A1
Data at offset 707 ('*1*000000004') was found to be of TYPE
X'013C' (IEA Segment Control ANSI EDI).

(Level 2: Offset 707, len 12, comp 6 of 6, #1, DI 000000A2
Data at offset 707 ('*1*000000004') was found to be of TYPE
X'000C' (Segment Control ANSI EDI).

(Level 1: Offset 0, len 720, comp 1 of 1, #1, DI 000000A2
Data at offset 0 ('ISA*00* ') was found to be of TYPE
X'0009' (Partner X12 Inbound Interchange EDI).

(Level 1: Offset 0, len 720, comp 1 of 1, #1, DI 000000A3
Data at offset 0 ('ISA*00* ') was found to be of TYPE
X'0008' (X12 Inbound Interchange EDI).

(Level 1: Offset 0, len 720, comp 1 of 1, #1, DI 000000A3
Data at offset 0 ('ISA*00* ') was found to be of TYPE
X'0007' (Inbound Interchange EDI).

(Level 2: Offset 720, len 0, comp 1 of 6, #1, DI 000000A3
Data at offset 720 ('<CR><LF>...') does not match INITIATOR 'ISA'
of TYPE X'000F' (Partner Inbound ISA Segment Control ANSI EDI).

(Level 2: Offset 720, len 0, comp 1 of 6, #1, DI 000000A3
COMPONENT number 1 of TYPE X'0009' (Partner X12 Inbound Interchange EDI)
is required, but does not exist.

(Level 1: Offset 720, len 0, comp 1 of 1, #2, DI 000000A3
Attempting RESTART at offset 720 ('<CR><LF>...') for TYPE
X'0009' (Partner X12 Inbound Interchange EDI).

(Level 1: Offset 722, len 0, comp 1 of 1, #2, DI 000000A6
RESTART completed at offset 722 ('(end of data)...') with TYPE
X'0005' (Partner X12 Inbound Transmission EDI).

(Level 0: Offset 0, len 722, comp 1 of 0, #1, DI 000000A6
Data at offset 0 ('ISA*00* ') was found to be of TYPE
X'0005' (Partner X12 Inbound Transmission EDI).

INPUT 1 was valid, but it contained invalid objects.

End of Validation messages for INPUT CARD 1.


End of Execution messages.

 

[eyetry]

looks like this is just a section of the trace file. Did you do a find for 'invalid'?

 

[Samji]

This will not help.
I suggest you to first understand the trace mechanism.
So to understand first read the material or guide provided with the software.

In the guide you can find how to debug.

 

[janhes]

look for entries with the following text
failed COMPONENT RULE test

 

[dgerdner]

I did a search for "invalid", and the only occurance is the last line in the trace file:

"INPUT 1 was valid, but it contained invalid objects."

As for reading the manual; I've tried that, but have not found it helpful with this specific problem.

 

[dgerdner]

I just noticed the message regarding "Failed Component Rule Test". There are several of those, but I also receive those messages on files that process successfully. I will look closer at them.

If you can help, here is the first one:

(Level 3: Offset 108, len 41, comp 1 of 3, #1, DI 0000001D
Data at offset 108 ('*RO*WLWH*AROF*20...') failed COMPONENT RULE test for component number 1, TYPE X'0044' (QO F4010 Inbound Partner Funct'lGroup ANSI EDI).

And here is the GS record (it's a 301 message):

GS*RO*WLWH*AROF*20051025*1300*0004*X*004010~


Any insight that can be provided will be much appreciated.

 

[janhes]

you ned to look at your type tree so see the validation rules.

 

[janhes]

The trace file you pasted is not complete so there may be other errors. Look for 'required but does not exist' for mandatory objects if you have nothing Invalid.

 

[pvb1]

It takes practice. Here an mini explantion I had made up for someone. There are notes where the asterisks are that give a bit of explanation as to what the trace is saying.

The trace can be misleading without a proper understanding of how the data is validated. For instance, the trace you sent seems to indicate that the data is failing at byte 1619. Although objects are failing validation, that doesn't mean that the data itself is invalid. To really see what's happening you have to match the trace with the data and type tree and understand some validation rules. Read my observations below for each validation segment.

(Level 9: Offset 1619, len 0, comp 1 of 27, #1, DI 0000016B
Data at offset 1619 ('PRV*BI*EI*330057...') does not match INITIATOR 'LX'

of TYPE X'0126' (LX Segment V3041 ANSI EDI).

***This simply means that for the object to be valid, the data must start with an initiator of LX. This data starts with PRV. ***



(Level 9: Offset 1619, len 0, comp 1 of 27, #1, DI 0000016B

COMPONENT number 1 of TYPE X'0125' (LoopLX #837 Inbound Partner Set V3041 ANSI EDI)

is required, but does not exist.

***This can be misleading because it says it is required but doesn't exist. In actuality it's component 1 of the LoopLX group that is required so the bigger question is whether LoopLX is a required or optional component of another group. This can be determined by looking at the tree.***



(Level 8: Offset 1619, len 0, comp 27 of 28, #5, DI 0000016B

COMPONENT number 27 of TYPE X'009A' (LoopCLM #837 Inbound Partner Set V3041 ANSI EDI):

occurrence 5 is optional and does not exist.

***Here it is stating that component 27 of LoopCLM is optional and the 5th occurence doesn't exist. This also implies that there are 4 previous occurences.***



(Level 9: Offset 1619, len 0, comp 1 of 3, #1, DI 0000016B

Data at offset 1619 ('PRV*BI*EI*330057...') does not match INITIATOR 'LS'

of TYPE X'0121' (LS Segment V3041 ANSI EDI).


***This simply means that for the object to be valid, the data must start with an initiator of LS. This data starts with PRV. ***



(Level 9: Offset 1619, len 0, comp 1 of 3, #1, DI 0000016B

Data at offset 1619 ('PRV*BI*EI*330057...') failed COMPONENT RULE test

for component number 1, TYPE X'0166' (SBR2500 Block #837 Inbound Partner Set V3041 ANSI EDI).

***This is stating that the data failed the component rule for the SBR2500 Block group, but this doesn't mean the data is invalid. It's just saying it doesn't match that rule, so let's move on to the next object.***



(Level 8: Offset 1619, len 0, comp 28 of 28, #1, DI 0000016B

COMPONENT number 28 of TYPE X'009A' (LoopCLM #837 Inbound Partner Set V3041 ANSI EDI):

occurrence 1 is optional and does not exist.

***Simply states component 28 of LoopCLM isn't required and isn't there.***



(Level 7: Offset 901, len 718, comp 3 of 3, #1, DI 0000016B

Data at offset 901 ('CLM*BENO378400*1') was found to be of TYPE

X'009A' (LoopCLM #837 Inbound Partner Set V3041 ANSI EDI).

***Here is a good example of what's happening with validation. Notice that the offset has gone all the way back to offset 901 and its stating that 718 bytes were found to be of type LoopCLM. This indicates that all of the data from 901 to 1619 was being validated against the components of LoopCLM. It also appears from the validation segment directly above it that there were 28 components of LoopCLM that the validation was checked against, some required, some optional. The fact it says LoopCLM was found indicates that all of the component definitions or rules were satisfied. We must remember though, that those components can be groups that have components that will be validated. Thats how you can get the "is required, but does not exist." message and have the data still be valid. A required component of an optional component failed validation.

(Level 8: Offset 1619, len 0, comp 1 of 28, #1, DI 0000016C

Data at offset 1619 ('PRV*BI*EI*330057...') does not match INITIATOR 'CLM'

of TYPE X'009B' (CLM Segment V3041 ANSI EDI).

***This simply means that for the object to be valid, the data must start with an initiator of CLM. This data starts with PRV. ***



(Level 8: Offset 1619, len 0, comp 1 of 28, #1, DI 0000016C

COMPONENT number 1 of TYPE X'009A' (LoopCLM #837 Inbound Partner Set V3041 ANSI EDI)

is required, but does not exist.

***This means component 1 failed validation and is required, therefore the second occurence of LoopCLM doesn't exist and we will move on to the next component.***



Here are some important validation rules:

1) If all components up to and including its identifier are found and valid, the TYPE of the component exists. Note that this does not imply that the component exists.

2) A component exists if its type exists AND its rule is satisfied.

2.1) If the type of a component of an implied group exists, but the component rule isn't satisfied, the component doesn't exists and we throw away the type we found.

2.2) If the type of the component of a fixed or delimited group exists, but the component rule isn't satisfied, the component exists but it is invalid.
-------------------

It just requires some practice and patience matching the trace, tree, and data, step by step.

 

[eyetry]

Ok, I ran into something similar to your issue the other day.

As you've noted, the problem is that some times the tool isn't very good at providing specific messages when certain conditions are present. The tool knows the data is bad and if you are versed enough you can usually figure our what's wrong with minimal to modest effort. In my case the trace file was in excess of 6GB. The problem file contained 1 ISA, 1 GS and over 200 ST loops. On average the transactions contained over 10,000 segments. The mtr stated there was invalid data but was vague about the actual issue.

The issue that we faced last week was where segments looked like....

(assume * is element delimiter and '~' is the segment terminator)

N3~ (no delimiters or segment data)

N3*addr 1*******~ (to many element for segment type)

N3addr 1~ (missing delimiter)

~~ (terminator without segment data)

N3N4*city*... (missing segment data and terminator terminator)

and so on..... Essentially, the trace file said there was an error but wasn't clear on what the error was. I needed to find an mtr file message that looked suspicious and back track thru the mtr until I found what I was looking for.

the problem in reading the trace files is that messages like the ones below aren't neccessarily stating the file element or segment is bad....

...does not match INITIATOR 'CLM' (as stated above, unless it's tied tied to the word 'Required')

...failed COMPONENT RULE test for component number (is an alert to a potential problem but not neccessarily a real issue. You'd have to look at the actual file and backtrac from here)

Also check for envelope errors. Mismatch control numbers, bad counts etc....

If you have a large file with an issue that's hard to find, sometimes, it can be usefull to parse it into smaller pieces and validate each until you find a bad loop. Once you identify the first problem look for it everywhere in the file/transaction.

You probably figured out your issue by now but thought I'd add my 13 cents.