Finance | Project Operations, Human Resources, ...

Document ID is invalid - eConnect Error

(0) Share

Report

Posted on by Vaidh

Getting the following error when creating sales transaction through eConnect

Sql procedure error codes returned:

Error Number = 68 Stored Procedure= taSopHdrIvcInsert Error Description = Document ID is invalid
Node Identifier Parameters: taSopHdrIvcInsert
SOPNUMBE = STDINV2300
SOPTYPE = 3
Related Error Code Parameters for Node : taSopHdrIvcInsert
DOCID = 1007647
SOPTYPE = 3

<taSopHdrIvcInsert>
<SOPTYPE>3</SOPTYPE>
<DOCID>1007647</DOCID>
<SOPNUMBE>STDINV2300</SOPNUMBE>
<TAXSCHID>ALL DETAILS</TAXSCHID>
<TAXAMNT>10</TAXAMNT>
<DOCDATE>09/03/2020</DOCDATE>
<CUSTNMBR>BEIE</CUSTNMBR>
<SUBTOTAL>68.74</SUBTOTAL>
<BACHNUMB>IASALES26042011124</BACHNUMB>
<USINGHEADERLEVELTAXES>1</USINGHEADERLEVELTAXES>
<CREATECOMM>1</CREATECOMM>
<CURNCYID>Z-US$</CURNCYID>
<INVODATE>09/03/2020</INVODATE>
</taSopHdrIvcInsert>

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (6)

Answers (0)

Richard Wheeler 75,852 Moderator on at

Like (0)

Report
Copy link

Link copied!

Do you really have a document ID of 1007647 setup under Tools->Setup->Sales->Sales Order Processing->Invoice? Doc IDs usually look like STDINV. Try typing an invoice into GP with the same values and see what you get.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report
Copy link

Link copied!

Richard,

When you look at the XML code, the Document Number is indeed STDINV2300, which looks correct (though the 4 digits number seems a little short to me).

The Document ID is something else and relates most of the time to the 'Vendor' document ID, and is expecting a 15 digit 'string' type of data.

And there are possibly 2 problems that can happen here:

1. Not sure if the Document ID needs to be unique, as it might be checked against SOP10100

2. It's supposed to be a string, and this looks like a numerical data.. maybe eConnect has run into some issue with trying to convert it ?

docs.microsoft.com/.../jj193404(v=msdn.10)

The table taErrorCode may hold more details about the error #68 returned by the process...

Here is a good blog post on how to deal with eConnect errors:

timwappat.info/.../Gracefully-dealing-with-eConnect-errors

Was this reply helpful? Yes No
Alaa Ramadan 4,130 on at

Like (0)

Report
Copy link

Link copied!

I believe this is specific error is about the DOCID as Richard mentioned related to sales order processing setup. usually it used to classify invoices and it should be more descriptive ID such StndInv, DomsInv, ForenInvc.

Please make sure this document id exist

Was this reply helpful? Yes No
Suggested answer

Ibrahim N. Omran 195 on at

Like (1)

Report
Copy link

Link copied!

Hello Vaidh

the Document ID filed is not a document number, please check the below snapshot

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report
Copy link

Link copied!

Ibrahim is correct,

(and I didn't check the exact source fields)..

The setup for the DOC ID can be found here in GP : Sales >> Setup >> Sales Order Processing >> Sales Document Setup button >> select the Order option

you can have multiple DOCID's setup with different setups to pre-populate your sales orders. The associated tables would be SOP40200 in the company DB.

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like (0)

Report
Copy link

Link copied!

As I said at the beginning of this thread go to Tools->Setup->Sales->Sales Order Processing->Invoice Doc IDs and see what document IDs you have setup. I would bet you do not have one called 1007647. This is a document number. You need to pass the document ID and the document number(SOPNUMBE) along with the SOPTYPE.

Was this reply helpful? Yes No