Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Input Type contains errors, Please help me in this

Status
Not open for further replies.

rossvinson

Programmer
Jun 8, 2005
4
IN
Hi,

My input file is a EDIFACT file and I am mapping the same input file as ouput file, inorder to validate the input file.

When I mapped the input file, I am getting the error "INPUT TYPE CONTAINS ERRORS". I have checked the input file, nothing is wrong.

When I looked at the trace file to find the error, the trace file has the errors at some levels, " (Level 1: Offset 0, len 0, comp 1 of 6, #1, DI 00000001:)
Data at offset 0 ('UNA:+.? 'UNB+UNO...') does not match INITIATOR ''
of TYPE X'0005' (UNA Envelope Control EANCOM)."

I dont understand what exactly means " DOES NOT MATCH INITIATOR. I am worried about the line "('UNA:+.? 'UNB+UNO...') does not match INITIATOR '' ". There are several lines as like in the trace file.

Sample two line of the INPUT file is

UNA:+.?'
UNB+UNOA:2+4606272999910:14+4606272999910:14+050921:0908+000032595'

I am not getting any output, but the map is processing only the first two segements of the EDIFACT message.

Please help me in solving this problem. Also please help me to attach the files to this fourm. If not please give some personal ID's so that I can mail.

Regards,
Vikash
 
If your data is correct then the type tree must be wrong but it's usually the other way round. The initiator is defined in your type tree for a particular item/group. Check the initiator for UNA Envelope Control EANCOM in your type tree.
 
Hi janhes,

Thanks for the reply. The Initiator for UNA Envelope Control EANCOM in the type tree is " Literal" and value is "UNA". Hope both are fine.

I hope the type tree is also fine. But I think there is some invalid data in the Input, but I am unable to fine it. If the invalid data exists at some place, it should process to some segements. My concern is that it is processing the first 2 segements only.

Can you please give me you email ID so that I can upload the files to your mail.

You can check them and get back to me.

Regards,
Vikash
 
Hi,

I have rectified that error. But cropped up with new error.

(Level 2: Offset 3, len 2, comp 1 of 6, #1, DI 00000001:)
Data at offset 3 (':+...') not in RESTRICTION LIST of TYPE
X'0007' (Composite Delimiter Control EANCOM).

(Level 2: Offset 3, len 2, comp 1 of 6, #1, DI 00000001:)
Data at offset 3 (':+') is INVALID data of TYPE
X'0007' (Composite Delimiter Control EANCOM).

Can some one please help me in rectifying this problem.

Regards,
Vikash
 
The value ':+' is not in the restriction list for Composite Delimiter Control EANCOM in the typetree
 
Looks like your Composite Delimiter is defined as 2 characters rather than 1 (based on a 6.5 version of the typetree)
 
Hi Janhes,

My UNA is exactly the same as you specified. I pasted the first 3 segments of my EDIFACT message.

UNA:+.? '
UNB+UNOA:2+4606272999910:14+4606272999910:14+050921:0908+000032595'
UNH+000032595+RECADV:D:96A:EN:EAN003'

The type tree is build on Version 6.7, its not opening with 6.5. Please suggest me in solving this problem.

Regards,
Vikash
 
Check your Composite Delimiter is defined as 1 character.
 
Hi Vikash,

Are you using Edifact standard tree or customized tree.

If it is a customized tree, then possibly there could be some errors in type definitions the tree..like it might not be matching with the input file.

Please check on that.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top