web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Procedure or function taSopLineIvcInsertPre has too many arguments specified

(0) ShareShare
ReportReport
Posted on by 35

After upgrade Dynamics GP from 2010 to 2013, the eConnect throw out an exception when export a PO into GP, which says "Procedure or function taSopLineIvcInsertPre has too many arguments specified."

I got this excption when calling the method CreateTransactionEntity(). What changes were made between eConnect 11 and eConnect 12 about it?

Thank you.

*This post is locked for comments

I have the same question (0)
  • Josh P Profile Picture
    2,895 on at

    Hi Helen,

    Your question about changes in eConnect is very general. Here is a link to Microsoft's developer reference including version changes to the integration suite. msdn.microsoft.com/.../bb219081.aspx

    Regarding the error you are receiving, if you can provide a copy of the generated xml being sent through eConnect from the serialized PO data, perhaps we may be able to help a little better.

    Regards,

    Joshua Pelkola

  • Bill Vanselow Profile Picture
    115 on at

    Some more information on the error Helen is seeing.

    We are using  GP Dynamics versioon 12.00.1042 (RTM), Deterity 12.00.0107.000, eConnect 12.1.1045.0

    This is the Beta version.  We just got the full version, and will be testing this on that version.

    The error is on a fresh GP 2013 install, using the same code and xml we used with GP 2010.  We are trying to create a SalesOrder in GP.

    Here is the error trace...

    System.Data.SqlClient.SqlException (0x80131904): Procedure or function taSopLineIvcInsertPre has too many arguments specified.

      at Microsoft.Dynamics.GP.eConnect.ServiceProxy.HandleSqlException(FaultException`1 ex)

      at Microsoft.Dynamics.GP.eConnect.ServiceProxy.CreateTransactionEntity(String connectionString, String xml)

      at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction)

      at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessEntityImport(String connectionString, String sXML, Boolean isTransaction)

      at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateTransactionEntity(String connectionString, String sXML)

     

    Here is the xml we are passing to eConnect function CreateTransactionEntity()...

    <eConnect xmlns:dt="urn:schemas-microsoftcom:datatypes">

    <SOPTransactionType>

    <taSopLineIvcInsert_Items>

    <taSopLineIvcInsert>

    <SOPNUMBE>ORDST2235</SOPNUMBE>

    <SOPTYPE>2</SOPTYPE>

    <CUSTNMBR>ADAMPARK0001</CUSTNMBR>

    <DOCDATE>2010-02-04</DOCDATE>

    <ITEMNMBR>256SDRAM</ITEMNMBR>

    <UNITPRCE>12.4</UNITPRCE>

    <XTNDPRCE>74.4</XTNDPRCE>

    <QUANTITY>6</QUANTITY>

    <ITEMDESC>256meg SDRAM</ITEMDESC>

    <DEFPRICING>1</DEFPRICING>

    <QtyShrtOpt>2</QtyShrtOpt>

    <NONINVEN>0</NONINVEN>

    <ReqShipDate>2010-02-19</ReqShipDate>

    <CURNCYID>Z-US$</CURNCYID>

    <DROPSHIP>1</DROPSHIP>

    </taSopLineIvcInsert>

    <taSopLineIvcInsert>

    <SOPNUMBE>ORDST2235</SOPNUMBE>

    <SOPTYPE>2</SOPTYPE>

    <CUSTNMBR>ADAMPARK0001</CUSTNMBR>

    <DOCDATE>2010-02-04</DOCDATE>

    <ITEMNMBR>4.5HD</ITEMNMBR>

    <UNITPRCE>12.4</UNITPRCE>

    <XTNDPRCE>24.8</XTNDPRCE>

    <QUANTITY>2</QUANTITY>

    <ITEMDESC>4.5 gig Hard Drive</ITEMDESC>

    <DEFPRICING>1</DEFPRICING>

    <QtyShrtOpt>2</QtyShrtOpt>

    <NONINVEN>0</NONINVEN>

    <ReqShipDate>2010-02-19</ReqShipDate>

    <CURNCYID>Z-US$</CURNCYID>

    <DROPSHIP>1</DROPSHIP>

    </taSopLineIvcInsert>

    </taSopLineIvcInsert_Items>

    <taSopHdrIvcInsert>

    <SOPNUMBE>ORDST2235</SOPNUMBE>

    <SOPTYPE>2</SOPTYPE>

    <DOCID>STDORD</DOCID>

    <DOCDATE>2010-02-04</DOCDATE>

    <CUSTNMBR>ADAMPARK0001</CUSTNMBR>

    <CSTPONBR>JE98765-1234</CSTPONBR>

    <SUBTOTAL>99.2</SUBTOTAL>

    <DOCAMNT>99.2</DOCAMNT>

    <BACHNUMB>EDI12/25/2012</BACHNUMB>

    <PRSTADCD>PRIMARY</PRSTADCD>

    <ORDRDATE>2010-02-04</ORDRDATE>

    <CREATETAXES>1</CREATETAXES>

    <DEFTAXSCHDS>1</DEFTAXSCHDS>

    <DEFPRICING>1</DEFPRICING>

    <ReqShipDate>2010-02-19</ReqShipDate>

    </taSopHdrIvcInsert>

    <taSopUserDefined>

    <SOPNUMBE>ORDST2235</SOPNUMBE>

    <SOPTYPE>2</SOPTYPE>

    <USRDEF03>PATTERSON</USRDEF03>

    </taSopUserDefined>

    <TCEDI>

    <StoreNumber>PD089031157</StoreNumber>

    <DCCode>TCEDI</DCCode>

    <MarkForCode>TCEDI</MarkForCode>

    <DepartmentNumber>TCEDI</DepartmentNumber>

    <User1>TCEDI</User1>

    <User2>TCEDI</User2>

    </TCEDI></SOPTransactionType>

    </eConnect>

  • Josh P Profile Picture
    2,895 on at

    Hi Bill,

    "System.Data.SqlClient.SqlException (0x80131904): Procedure or function taSopLineIvcInsertPre has too many arguments specified."

    Have you extended your business logic on the prior implementation of eConnect - specifically the "taSopLineIvcInsertPre" object? With eConnect, there are typically three stored procedures that run for each transaction call. There is a -Pre and a -Post version for all objects where custom business logic can extend the eConnect integration.

    They are executed on sql in the Pre > normal > Post fashion through the eCon calls to the database.

    It looks like you have extended this object, and you need to possibly update the stored procedure originally modified on the previous version of eConnect, but not on the 2013 version. If this is the case, you are getting the error because you are passing parameters which are not standard for SOP Order line item detail.

    Right off the top, I do not see anything funky on the source file passing, but I also do not have the detail changes to 2013 eConnect sprocs. If you have the full implementation, there should be a developer's manual for this object. You need to make sure the parameters have not slightly changed.

    Regards,

    Josh Pelkola

  • Helen He Profile Picture
    35 on at

    Josh,

    Thank you for your quick response. We've figured out the problem now. The stored procedures in GP 2013 have different parameters.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans