none
EDISend pipeline and EDIFACT PAYMUL problems. RRS feed

  • Question

  • Hi all,

     

    I have run into a strange problem while working on a EDIFACT PAYMUL project.

     

    When processing my message through the EDISend pipeline, I receive the following error message from BizTalk.

     

    Error Message:

     

    Event Type: Error
    Event Source: BizTalk Server 2006 EDI
    Event Category: None
    Event ID: 8116
    Date:  04-08-2008
    Time:  13:23:06
    User:  N/A
    Computer: RJALAP01


    Description:


    Error: 1 (Segment level error)
     SegmentID: MOA
     Position in TS: 34
     37: Invalid character(s) found in data element

     

    Error: 2 (Field level error)
     SegmentID: MOA
     Position in TS: 34
     Data Element ID: C51602
     Position in Segment: 2
     Position in Field: 2
     Data Value: 1545.10
     37: Invalid character(s) found in data element

     

    Error: 3 (Segment level error)
     SegmentID: MOA
     Position in TS: 37
     37: Invalid character(s) found in data element

     

    Error: 4 (Field level error)
     SegmentID: MOA
     Position in TS: 37
     Data Element ID: C51602
     Position in Segment: 2
     Position in Field: 2
     Data Value: 1545.10
     37: Invalid character(s) found in data element


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    The error only occurs when the value in the data element ends with ".*0". If I change the value to ex. "1545.01" the pipeline executes without any problems.

     

    I could easily trim the data value to remove the trailing zeroes, but I would like to keep my input data unchanged.

     

    Any help would be greatly appreciated.

     

    /Jaeger

     

     

     

     

     

     


     

     

    Tuesday, August 5, 2008 6:52 AM

Answers

All replies

  • Jaeger,

     

    When you say that problem is seen for data element ending with ".*0", I am assuming that * is just a place holder for other digits and not part of actual data. Is that correect? If so then the problem is only related to trailing zeros. Go to Party settings -> Edifact properties -> Party as interchange receiver -> Validation and ack processing and check "Allow leading and trailing zeros and spaces". This should solve the problem.

     

    Koushik

    Tuesday, August 5, 2008 7:45 AM
  •  

    Hi Koushik,

     

    It worked!

     

    Thanks for your help.

     

    /Jaeger

    Tuesday, August 5, 2008 8:38 AM
  • Hi

     

    We have come across a very similar problem, only the solution doesn't seem to work for us. We are using BizTalk 2009.  In our case the error looks like this:

     

    Error: 1 (Field level error)

                                 SegmentID: FTX

                                 Position in TS: 212

                                 Data Element ID: C10803

                                 Position in Segment: 5

                                 Position in Field: 3

                                 Data Value:                                    ","

                                 37: Invalid character(s) found in data element

     

    We have checked "Allow leading and trailing zeros and spaces".

     

    Any help is greatly appreciated.

     

    /Michael Christensen

    Friday, December 17, 2010 12:55 PM