I'm getting this error from Econnect:

 - Sql procedure error codes returned:
Error Number = 712  Stored Procedure taRMTransaction  Error Description = Tax amount (TAXAMNT) does not equal tax details in RM10601
Node Identifier Parameters: taRMTransaction                                   
RMDTYPAL = 1
DOCNUMBR = 999-99999-112007-R2
DOCDATE = 03-12-2008
BACHNUMB = GEM200711013600
CUSTNMBR = 999-99999
Related Error Code Parameters for Node : taRMTransaction                                   
TAXAMNT = 1892.73000

<taRMTransaction><RMDTYPAL>1</RMDTYPAL><DOCNUMBR>999-99999-112007-R2</DOCNUMBR><DOCDATE>03-12-2008</DOCDATE><BACHNUMB>GEM200711013600</BACHNUMB><CUSTNMBR>999-99999</CUSTNMBR><DOCAMNT>34941.00000</DOCAMNT><SLSAMNT>25530.34000</SLSAMNT><FRTAMNT>7517.93000</FRTAMNT><TAXAMNT>1892.73000</TAXAMNT><LSTUSRED>239</LSTUSRED></taRMTransaction>

I've checked, and in my xml I'm sending econnect the taxamnt fields have the same number, so I don't think it's the xml I'm sending econnect.  Also it only happens on 2 customers and works fine on others.  Is there something I'm missing?

Brad

I'm going to repeat the advice that I gave here

http://vstoolsforum.com/forums/t/436.aspx

This is a front end error. Manually key this transaction into Dynamics and I'll bet you get the same error. There is something that has to be changed in the front end (probably) and this will start working. My first guess (you didn't sent the entire XML doc) would be that these customers don't have the same 'default tax schedule' as your other customers.

If I'm wrong, post the entire XML doc and we'll look at it.

HTH,

I've talked to the guys that work with great plains, and we've compared one customer that worked and the other that failed.  We can't see a difference though.  I changed the default tax ID to see if that changed anything.  However I just got a new error telling me that ID wasn't in great plains.  I've run a different invoice and got the same error, I've included both the error and the xml I sent.  Thanks for all your help, this website has been a lifesaver for me. 

Brad

XML Sent:
<eConnect xmlns:xsi="" xmlns:xsd="">
  <RMTransactionType>
    <eConnectProcessInfo xsi:nil="true" />
    <taUpdateCreateCustomerRcd xsi:nil="true" />
    <taCreateCustomerAddress_Items xsi:nil="true" />
    <taRMCommissions_Items xsi:nil="true" />
    <taRMTransactionTaxInsert_Items>
      <taRMTransactionTaxInsert>
        <CUSTNMBR>999-99999</CUSTNMBR>
        <DOCNUMBR>999-99999-112007-R1</DOCNUMBR>
        <RMDTYPAL>7</RMDTYPAL>
        <BACHNUMB>GEM200711013618</BACHNUMB>
        <TAXDTLID>DEFAULT</TAXDTLID>
        <TAXAMNT>542.37000</TAXAMNT>
        <STAXAMNT>0</STAXAMNT>
        <TAXDTSLS>0</TAXDTSLS>
      </taRMTransactionTaxInsert>
    </taRMTransactionTaxInsert_Items>
    <taRMDistribution_Items xsi:nil="true" />
    <taRMTransaction>
      <RMDTYPAL>7</RMDTYPAL>
      <DOCNUMBR>999-99999-112007-R1</DOCNUMBR>
      <DOCDATE>02-01-2008</DOCDATE>
      <BACHNUMB>GEM200711013618</BACHNUMB>
      <CUSTNMBR>999-99999</CUSTNMBR>
      <DOCAMNT>33767.24000</DOCAMNT>
      <SLSAMNT>25691.97000</SLSAMNT>
      <FRTAMNT>7532.90000</FRTAMNT>
      <TAXAMNT>542.37000</TAXAMNT>
      <LSTUSRED>239</LSTUSRED>
    </taRMTransaction>
    <taMdaUpdate_Items xsi:nil="true" />
  </RMTransactionType>
</eConnect>

Error:

 - Sql procedure error codes returned:
Error Number = 712  Stored Procedure taRMTransaction  Error Description = Tax amount (TAXAMNT) does not equal tax details in RM10601
Node Identifier Parameters: taRMTransaction                                   
RMDTYPAL = 7
DOCNUMBR = 999-99999-112007-R1
DOCDATE = 02-01-2008
BACHNUMB = GEM200711013618
CUSTNMBR = 999-99999
Related Error Code Parameters for Node : taRMTransaction                                   
TAXAMNT = 542.37000

<taRMTransaction><RMDTYPAL>7</RMDTYPAL><DOCNUMBR>999-99999-112007-R1</DOCNUMBR><DOCDATE>02-01-2008</DOCDATE><BACHNUMB>GEM200711013618</BACHNUMB><CUSTNMBR>999-99999</CUSTNMBR><DOCAMNT>33767.24000</DOCAMNT><SLSAMNT>25691.97000</SLSAMNT><FRTAMNT>7532.90000</FRTAMNT><TAXAMNT>542.37000</TAXAMNT><LSTUSRED>239</LSTUSRED></taRMTransaction>

I'm convinced that there is a difference between what you have coded and what is being keyed in Dynamics.

Rekey this doc, manually, and carefully note the things that you have to key. If you have to key a taxscheduleid, they you must code it. If it defaults, you don't need to code it.

Same with the tax window. If the taxes default correctly, then don't code them.

I'm guessing that either you need to specify the TAXSCHEDID in code, or you don't need to code the taxes. They should default.

One more time for emphasis.

• rekey the doc manually
• carefully note every keystroke
• if you have to enter something manually (TAXSCHEDID), you must code it.
• if you don't have to enter it manually (if it defaults), don't code it.

The answer is in there somewhere.

I did eventually figure this out, and wanted to post my solution for anyone that might need it.  It turns out the invoice number was to long.  Their are at a least 2 different stored procs that were being called.  One of them had an invoice number field that was 20 char and the other had one that was 17.  So the invoice number was being truncated and not matching up.  Which is why it had such a strange error message that didn't point to the actual problem.

Brad