Skip to content
+1-888-319-3663

COMMUNITY FORUM

Order not going from CRM to GP

Tony Iacono asked 7 years ago
STR_GP_ORDERS_RT: Sql procedure error codes returned:
Error Number = 56 Stored Procedure= taSopHdrIvcInsert Error Description = Input variable contains a duplicate document
Node Identifier Parameters: taSopHdrIvcInsert
SOPNUMBE = ORD-01046-G1B6L1
SOPTYPE = 2
Related Error Code Parameters for Node : taSopHdrIvcInsert
SOPNUMBE = ORD-01046-G1B6L1
SOPTYPE = 2

<taSopHdrIvcInsert>
<UpdateIfExists>1</UpdateIfExists>
<TRDISAMT>0.0000</TRDISAMT>
<SOPNUMBE>ORD-01046-G1B6L1</SOPNUMBE>
<FREIGHT></FREIGHT>
<BACHNUMB>CRMBAT0001</BACHNUMB>
<ADDRESS2></ADDRESS2>
<COUNTRY></COUNTRY>
<CUSTNMBR>WILSONBROWN0001</CUSTNMBR>
<ADDRESS1></ADDRESS1>
<ORIGNUMB>ORD-01046-G1B6L1</ORIGNUMB>
<DEFTAXSCHDS>1</DEFTAXSCHDS>
<ADDRESS3></ADDRESS3>
<SHIPMTHD></SHIPMTHD>
<CITY></CITY>
<PHNUMBR1></PHNUMBR1>
<SOPTYPE>2</SOPTYPE>
<ShipToName></ShipToName>
<DEFPRICING>1</DEFPRICING>
<UpdateExisting>0</UpdateExisting>
<CSTPONBR>0000003</CSTPONBR>
<CUSTNAME>Wilson Brown</CUSTNAME>
<INTEGRATIONID>CRM</INTEGRATIONID>
<DOCID>STDORD</DOCID>
<DOCDATE>3/22/2015 12:00:00 AM</DOCDATE>
</taSopHdrIvcInsert>
Answers
patrick answered 7 years ago
Tony,
The error means that this document (ORD-01046-G1B6L1) already exists in GP.
Your UpdateExisting flag is set to 0 meaning “insert new document only, fail if exists” and it does exist and so does fail.
You would want to either check the “update if exists” flag or make sure to only do inserts from CRM to GP.
patrick
Tony Iacono replied 7 years ago

Hi Patrick,
thanks for you relpy. I have read that for work orders and order lines the store procedure that the map calls works differently that is: the “Update existing” checkbox (outside the columns) should be set to true and for the “Update if exists” option (inside the columns) set to false. Isn’t this the case?
Thanks,
Tony

Brandon Germaine replied 6 years ago

Hi there,

Tony, did you ever come up with a solution to this? I am experiencing the same thing, where I have an abundant number of SOP documents that have integration from CRM to GP, however updates continue to receive the same eConnect message. We dont really want the details updated, as the CRM document is locked once they are fulfilled anyways, but I would love to clear the Event Viewer log so that it would easier to debug any actual errors.

Patrick – if you can assist with the appropriate SOP HDR and Line settings as well, I’d greatly appreciate it. I imagine its something very small but SOP does behave differently then other eConnect calls and all changes I have made prevent the documents from being integrated at all.

Thank you very much,

Brandon


If you would like to submit an answer or comment, please sign in to the eOne portal.