none
837 Instit error appears not to like the decimal point in the charge amounts RRS feed

  • Question

  • Error: 1 (Field level error)
     SegmentID: CLM
     Position in TS: 22
     Data Element ID: CLM02__TotalClaimChargeAmount
     Position in Segment: 2
     Data Value: 8888.99
     6: Invalid character in data element

    Error: 2 (Field level error)
     SegmentID: SV2
     Position in TS: 40
     Data Element ID: SV203__LineItemChargeAmount
     Position in Segment: 3
     Data Value: 8888.99
     6: Invalid character in data element

    I have went into the Party edi properties and UN-checked the checkbox that says Convert implied decimal format Nn to base 10 Numeric value

    Thanks

    • Moved by Ben Cline1Moderator Thursday, November 4, 2010 9:57 PM Related to EDI (From:BizTalk Server General)
    Thursday, November 4, 2010 3:33 PM

Answers

All replies

  • You have to change the property in the trading partner definition to allow leading spaces and zeros.
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    Thursday, November 4, 2010 10:31 PM
  • Hi there Thanks for the Answer It did not work but that is the problem My data is 91.50 and that fails if I edit the file to 91.5 it works great!

    So your answer above seems like it should work, but I have them checked and it is still doing it????? It appears as if Biztalk is ignoring the checkbox? I re-started host instances. I even did a full stop and restarted the application  and re-started host instances???? This is Biztalk 2009.

     

    Thanks

    Friday, November 5, 2010 1:50 PM
  • In the validation section at the bottom of the EDI properties, there is the same setting, is that changed also?
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by Stoneman3735 Monday, November 8, 2010 5:37 PM
    Friday, November 5, 2010 5:25 PM
  • Eric's recommendation should work,

    If not could you please execute the following query in the BizTalkMgmtDb database and post the results.

    select IsSender,EdiEncoding,ValidateEDIType,IgnoreInvalidChars,ValidateExtended,TrailingDelimiters from
    dbo.EdiPartnerAckValidation ackv inner join dbo.bts_party part on ackv.PartyId = part.nID
    where part.nvcName = 'Your Party Name'


     Sathish - http://blog.tsathish.com

    Friday, November 5, 2010 6:45 PM
  • This worked I discovered it was not hitting the correct party fixed that now it works
    Monday, November 8, 2010 5:38 PM