I am importing SOP invoices from XML files prepared by a client.  The file appears to be correct, but when I attempt to import it, I get the error "Subtotal does not match the line item totals".

I have asked them to include the Subtotal node in their XML because the transactions are coming from an eCommerce web site, and I want to ensure that the data and subtotals being imported from the XML files matches what GP calculates.  In theory, this shouldn't be a problem, as there should be no issue including the Subtotal node (and I've done other eConnect imports that have the Subtotal node that work fine).

To try and rule out any issues with tax and freight and do a basic test, I have even tried modifying the file so that it only has one line line item with no tax or freight, but the same error occurs.  Entering the transaction directly into GP doesn't give any errors or other clues.

I'm hoping it's something simple, like a missing node or a simple mistake, but I'm not seeing it...

Any help would be appreciated...

 

 eConnect error: Microsoft.GreatPlains.eConnect.eConnectException: Error Number = 67  Stored Procedure taSopHdrIvcInsert  Error Description = Subtotal does not match the line item totals

Sql procedure error codes returned:
Error Number = 67  Stored Procedure taSopHdrIvcInsert  Error Description = Subtotal does not match the line item totals
Node Identifier Parameters: taSopHdrIvcInsert                                  
SOPNUMBE = 940843-123557
SOPTYPE = 3
Related Error Code Parameters for Node : taSopHdrIvcInsert                                  
SUBTOTAL = 30.00

<taSopHdrIvcInsert><SOPTYPE>3</SOPTYPE><DOCID>INV CONSOLE</DOCID><SOPNUMBE>940843-123557</SOPNUMBE><ORIGNUMB>940843</ORIGNUMB><LOCNCODE>INNO-BB</LOCNCODE><DOCDATE>08/01/2006</DOCDATE><FREIGHT>0</FREIGHT><TAXAMNT>0</TAXAMNT><MISCAMNT>0</MISCAMNT><TRDISAMT>0</TRDISAMT><CUSTNMBR>0029</CUSTNMBR><CUSTNAME>SOAPnet Store</CUSTNAME><SUBTOTAL>30.00</SUBTOTAL><DOCAMNT>30.00</DOCAMNT><BACHNUMB>CONSOLE01</BACHNUMB><USER2ENT>sa</USER2ENT><FRTTXAMT>0</FRTTXAMT><MSCTXAMT>0</MSCTXAMT><ORDRDATE>01/03/2006</ORDRDATE><INVODATE>01/03/2006</INVODATE><CMMTTEXT>9611804625277200128060</CMMTTEXT></taSopHdrIvcInsert>
Processing complete: 6/23/2009 12:15:14 PM

 

 <?xml version="1.0" encoding="utf-8"?>
<eConnect xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <SOPTransactionType>
    <taSopHdrIvcInsert>
      <SOPTYPE>3</SOPTYPE>
      <DOCID>INV CONSOLE</DOCID>
      <SOPNUMBE>940843-123557</SOPNUMBE>
      <ORIGNUMB>940843</ORIGNUMB>
      <LOCNCODE>INNO-BB</LOCNCODE>
      <DOCDATE>08/01/2006</DOCDATE>
      <CUSTNMBR>0029</CUSTNMBR>
      <CUSTNAME>SOAPnet Store</CUSTNAME>
      <SUBTOTAL>30.00</SUBTOTAL>
      <DOCAMNT>30.00</DOCAMNT>
      <BACHNUMB>CONSOLE01</BACHNUMB>
      <USER2ENT>sa</USER2ENT>
      <ORDRDATE>01/03/2006</ORDRDATE>
      <INVODATE>01/03/2006</INVODATE>
      <CMMTTEXT>9611804625277200128060</CMMTTEXT>
    </taSopHdrIvcInsert>
    <taSopLineIvcInsert_Items>
      <taSopLineIvcInsert>
        <SOPTYPE>3</SOPTYPE>
        <SOPNUMBE>940843-123557</SOPNUMBE>
        <CUSTNMBR>0029</CUSTNMBR>
        <DOCDATE>08/01/2006</DOCDATE>
        <LOCNCODE>INNO-BB</LOCNCODE>
        <ITEMNMBR>406-3598</ITEMNMBR>
        <UNITPRCE>30.00</UNITPRCE>
        <XTNDPRCE>30.00</XTNDPRCE>
        <QUANTITY>1</QUANTITY>
      </taSopLineIvcInsert>
    </taSopLineIvcInsert_Items>
  </SOPTransactionType>
</eConnect>

 Well, mystery solved.

The client's XML file had the taSopHdrIvcInsert node first, and then subsequently supplied the taSopLineIvcInsert node(s).

After reviewing some sample XML files that I created using eConnect's serialization, I saw that the lines were first.  So apparently the eConnect XML parsing routine needs to have the lines first so that it can accumulate the line extended prices, and then it compares that subtotal with the amount specified in the invoice header node.