Site Search:
Sign in | Join | Help

The stored procedure 'VENDORID' doesn't exist.

Last post 05-30-2008 6:05 AM by pramodhc. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 05-28-2008 8:22 AM

    The stored procedure 'VENDORID' doesn't exist.

    Hi

    I am using econnect for inserting vendor information into GreatPlain .  The code segment is shown below

     

    string strconnstring = "Data Source=192.168.0.75;Initial Catalog=TWO;User ID=sa;password=password-1;Integrated Security=SSPI;Persist Security Info=False;";

    string strdataxml = "<econnect><taUpdateCreateVendorRcd><VENDORID>110TE001</VENDORID><VENDNAME>110 Technology</VENDNAME><VENDSHNM>110 Technology</VENDSHNM><VNDCHKNM>110 Technology</VNDCHKNM><HOLD>1</HOLD><VENDSTTS>1</VENDSTTS><VNDCLSID>F</VNDCLSID><VADDCDPR>PRIMARY</VADDCDPR><VADCDPAD>PRIMARY</VADCDPAD><VADCDTRO>PRIMARY</VADCDTRO><TXIDNMBR></TXIDNMBR><TEN99TYPE>1</TEN99TYPE></taUpdateCreateVendorRcd><taCreateVendorAddress ><VENDORID>110TE001</VENDORID><ADRSCODE>PRIMARY</ADRSCODE><VNDCNTCT>AR</VNDCNTCT><ADDRESS1>27 Technology Way</ADDRESS1><ADDRESS2>Millyard Technology Park</ADDRESS2><COUNTRY>UNITED STATES OF AMERICA</COUNTRY><CITY>Nashua</CITY><STATE>New Hampshire</STATE><ZIPCODE>03060-3245</ZIPCODE><PHNUMBR1>(999) 999-9999</PHNUMBR1></taCreateVendorAddress ></econnect>";

    try

    {

    Microsoft.GreatPlains.eConnect.
    eConnectMethods econnectinstance = new Microsoft.GreatPlains.eConnect.eConnectMethods();

    econnectinstance.eConnect_EntryPoint(strconnstring, Microsoft.GreatPlains.eConnect.EnumTypes.ConnectionStringType.SqlClient, strdataxml, Microsoft.GreatPlains.eConnect.EnumTypes.SchemaValidationType.None, "");

    }

    catch (Exception ex)

    {

    string strex = ex.ToString();

    }

    I am getting the exception The stored procedure 'VENDORID' doesn't exist. Can anybody help on this?

    thanks in advance

     

     

     

    • 61.8.153.203
  • 05-28-2008 9:02 AM In reply to

    Re: The stored procedure 'VENDORID' doesn't exist.

    Look carefully at your XML doc, then at the sample doc that is in the code that install with eConnect. You're missing a node inbetween eConnect and taUpdateCreateVendorRcd.

    It's be a 'transactionType' node, probably.

    Steve Gray, MCDBA
    Technical Editor
    steve@VSToolsForum.com
    • 71.100.135.32
  • 05-29-2008 6:34 AM In reply to

    Re: The stored procedure 'VENDORID' doesn't exist.

    Thanks for the quick reply. I couldnt able to find any sample docs(am sorry and  new to econnect programming). Can you provide some sample documents or website URL that will be providing the same 

    thanks

     

    • 61.8.153.203
  • 05-29-2008 8:23 AM In reply to

    Re: The stored procedure 'VENDORID' doesn't exist.

    In GP 9 they're installed under C:\PROGRAM FILES\MICROSOFT GREAT PLAINS, in GP 10 they're installed under C:\PROGRAM FILES\COMMON\MICROSOFT COMMON\ECONNECT

    Those are not exactly correct, but they're close, you'll find them. Additionally, I have posted quite a few docs here

    http://forum.4penny.net/forums/p/351/732.aspx#732

    You can navigate to them from the home page of this site, toward the bottom you'll see a link that says 'Introduction to eConnect'

     

    Steve Gray, MCDBA
    Technical Editor
    steve@VSToolsForum.com
    • 71.100.135.32
  • 05-30-2008 4:57 AM In reply to

    Re: The stored procedure 'VENDORID' doesn't exist.

    Thanks for the reply. I have solved the tag issue. Now I am getting the following error:

     "Sql procedure error codes returned:\r\nError Number = 233  Stored Procedure taUpdateCreateVendorRcd  Error Description = The Vendor Class does not exist in the Payables Class Master Table\r\nNode Identifier Parameters: taUpdateCreateVendorRcd                            \r\nVENDORID = 110TE001\r\nRelated Error Code Parameters for Node : taUpdateCreateVendorRcd             "

     

    The input xml given is as follows

    "<econnect><PMTransactionType><taUpdateCreateVendorRcd><VENDORID>110TE001</VENDORID><VENDNAME>110 Technology</VENDNAME><VENDSHNM>110 Technology</VENDSHNM><VNDCHKNM>110 Technology</VNDCHKNM><HOLD>1</HOLD><VENDSTTS>1</VENDSTTS><VNDCLSID>F</VNDCLSID><VADDCDPR>PRIMARY</VADDCDPR><VADCDPAD>PRIMARY</VADCDPAD><VADCDTRO>PRIMARY</VADCDTRO><TXIDNMBR></TXIDNMBR><TEN99TYPE>1</TEN99TYPE></taUpdateCreateVendorRcd><taCreateVendorAddress ><VENDORID>110TE001</VENDORID><ADRSCODE>PRIMARY</ADRSCODE><VNDCNTCT>AR</VNDCNTCT><ADDRESS1>27 Technology Way</ADDRESS1><ADDRESS2>Millyard Technology Park</ADDRESS2><COUNTRY>UNITED STATES OF AMERICA</COUNTRY><CITY>Nashua</CITY><STATE>New Hampshire</STATE><ZIPCODE>03060-3245</ZIPCODE><PHNUMBR1>(999) 999-9999</PHNUMBR1></taCreateVendorAddress ><taPMTransactionInsert><BACHNUMB>1001</BACHNUMB><VCHNUMWK>12345</VCHNUMWK><VENDORID>110TE001</VENDORID><DOCNUMBR>123</DOCNUMBR><DOCTYPE>1</DOCTYPE><DOCAMNT>10000</DOCAMNT><DOCDATE>02/04/2008</DOCDATE></taPMTransactionInsert></PMTransactionType></econnect>";

     

    Can you help

     

    thanks

    Pramodh C

     

     

    • 61.8.153.203
  • 05-30-2008 6:05 AM In reply to

    Re: The stored procedure 'VENDORID' doesn't exist.

    I have solved the issue by changing the value of VNDCLSID  to the existing values in GP

     

    thanks

    • 61.8.153.203
Page 1 of 1 (6 items)