45
I have a strange problem with taPMTransactionInsert called from SQL. It will only accept a voucher number that is the same as the invoice number. It will not accept even the next voucher number from PM004100. Trying any other number generates the bizarre error 313 Tax table detail does not equal the tax Amount !! Does anyone have any bright ideas?
*This post is locked for comments
Hi Steve,
I'm running into an similar issue that is producing the same error. Based on the error do you also think there is a bug in the .NET code. I am able to manually create the transaction in GP but I get an error when running the connector. Is there a value I can change to test if this is the same bug?
Thanks
07/11/2019 16:35:31.51: Failed to import AP invoice 101 for vendor ACETRAVE0001: Sql procedure error codes returned:
Error Number = 313 Stored Procedure= taPMTransactionInsert Error Description = Tax table detail does not equal the tax amount
Node Identifier Parameters: taPMTransactionInsert
BACHNUMB = AP1906121727
VCHNUMWK = 00000000000001262
VENDORID = ACETRAVE0001
DOCNUMBR = 101
DOCTYPE = 1
DOCDATE = 6/12/2019 12:00:00 AM
Related Error Code Parameters for Node : taPMTransactionInsert
TAXAMNT = 10
<taPMTransactionInsert>
<BACHNUMB>AP1906121727</BACHNUMB>
<VCHNUMWK>00000000000001262</VCHNUMWK>
<VENDORID>ACETRAVE0001</VENDORID>
<DOCNUMBR>101</DOCNUMBR>
<DOCTYPE>1</DOCTYPE>
<DOCAMNT>110</DOCAMNT>
<DOCDATE>6/12/2019 12:00:00 AM</DOCDATE>
<PRCHAMNT>100</PRCHAMNT>
<CHRGAMNT>110</CHRGAMNT>
<TRXDSCRN>TEST</TRXDSCRN>
<TAXAMNT>10</TAXAMNT>
<PORDNMBR>PO2080</PORDNMBR>
<CREATEDIST>0</CREATEDIST>
</taPMTransactionInsert>
07/11/2019 16:35:31.51: Failed to import AP Invoice file: AP_Invoice_101_123.xml
After further review, I found that I had a bug in my .NET code that was causing the problem.
I had incorrectly assigned the invoice document number to the VCHRNMBR node in taPMTransactionTaxInsert.
So the tax node was serialized (and saved to PM10500 in the database) with an incorrect voucher number, preventing taPMTransactionInsert from locating the tax record in PM10500. Hence the error.
So it looks like eConnect 2010 is working just fine. Just make sure to double check the values assigned to taPMTransactionTaxInsert.
The above post is over 2 years old, but I thought I would chime in and share that I am experiencing the exact same problem with eConnect 2010.
I was getting the 313 Tax table detail error. I checked and double checked everything, and even traced the eConnect stored procedures to confirm the tax info was being saved properly, but everything looked fine.
I tried the above suggestion of setting the document number the same as the voucher number, and amazingly, the transaction imported okay.
So it would appear that this is a bug somewhere in taPMTransactionInsert or taPMTransactionTaxInsert.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (