none
How to know wich file gave the error

    Question

  • Hello,

    My application retrieves attachments from emails and processes them.

    I'm getting error messages like this, in event viewer for the source BIZTALK SERVER 2006 EDI:

     

    Error: 1 (Field level error)

    SegmentID: W2

    Position in TS: 6

    Data Element ID: W205

    Position in Segment: 5

    Data Value:  

    7: Invalid code value

     

    Error: 2 (Field level error)

    SegmentID: Q5

    Position in TS: 7

    Data Element ID: Q501

    Position in Segment: 1

    Data Value:  

    7: Invalid code value

     

    Error: 3 (Field level error)

    SegmentID: V1

    Position in TS: 8

    Data Element ID: V102

    Position in Segment: 2

    Data Value:  

    4: Data element too short

     

    Error: 4 (Field level error)

    SegmentID: V1

    Position in TS: 8

    Data Element ID: V104

    Position in Segment: 4

    Data Value:  

    4: Data element too short

     

    Error: 5 (Field level error)

    SegmentID: R4

    Position in TS: 9

    Data Element ID: R404

    Position in Segment: 4

    Data Value:  

    4: Data element too short 


    But this doesn't give any information about in wich file had this error.
    How can I find it?

     

     

    Tuesday, August 03, 2010 10:38 AM

Answers

  • Hi,

       So start from the first error:

    Error: 1 (Field level error)

    SegmentID: W2

    Position in TS: 6

    Data Element ID: W205

    Position in Segment: 5

    Data Value:  

    7: Invalid code value

     

    Meaning of this error:

    1- It's a field level error. Means there is somthing wrong in segment field.

    2- Segment ID is the name of the segment in which there is a wrong field. And that is W2.

    3- Position in TS means Position in Transaction set. Means as you know One trasaction for X12 starts from ST and ends at SE. So count from ST and increment the count so in that Transaction it will come at 6th position.

    4- Data element ID: It is the data element in the Segment. So in the segment W2 , W205 field is wrong.

    5- Position in segment means position of field in Segment W2. And that is 5th postion in W2 segment.

    6- Data Value is the actual data at this position. In this case it is null.

    7- Error reason: So this field is Some kind of data type and "NULL" does not come under this data type. So invalid code value.

     

     

    In this way you can see what are other errors?

     

     

    Thanks

    Gyan

     


    If this answers your question, please mark it as "Answered".
    Tuesday, August 03, 2010 3:04 PM

All replies

  • Hi,

       So start from the first error:

    Error: 1 (Field level error)

    SegmentID: W2

    Position in TS: 6

    Data Element ID: W205

    Position in Segment: 5

    Data Value:  

    7: Invalid code value

     

    Meaning of this error:

    1- It's a field level error. Means there is somthing wrong in segment field.

    2- Segment ID is the name of the segment in which there is a wrong field. And that is W2.

    3- Position in TS means Position in Transaction set. Means as you know One trasaction for X12 starts from ST and ends at SE. So count from ST and increment the count so in that Transaction it will come at 6th position.

    4- Data element ID: It is the data element in the Segment. So in the segment W2 , W205 field is wrong.

    5- Position in segment means position of field in Segment W2. And that is 5th postion in W2 segment.

    6- Data Value is the actual data at this position. In this case it is null.

    7- Error reason: So this field is Some kind of data type and "NULL" does not come under this data type. So invalid code value.

     

     

    In this way you can see what are other errors?

     

     

    Thanks

    Gyan

     


    If this answers your question, please mark it as "Answered".
    Tuesday, August 03, 2010 3:04 PM
  • If the message is suspended you should be able to look at its details. It should tell you in the Context section.

     

    Hope this helps!

    Scott

     

    Thursday, August 05, 2010 8:18 PM