Software informational articles

Microsoft great plains ecommerce ? stored procedures accost - software


Since Account 8. 0 Microsoft Commerce Solutions Great Plains & Great Plains Accepted are obtainable on Microsoft SQL Ma?tre d' and MSDE (which is in fact MS SQL with folder size limit of 2GB). As eCommerce designer you must be aware of more than a few options and customization tools in your disposition, when you exploit Microsoft Great Plains 8. 5 (June 2005), 8. 0, 7. 5, Great Plains Dynamics/eEnterprise 7. 0, 6. 0, 5. 5 or 5. 0 Great Plains Dynamics C/S+. When you have old versions (7. 5 and prior) we believe that you are on MS SQL Ma?tre d' 2000/7. 0, since if you are on Ctree or Invasive SQL/Btrieve - you ought to use ODBC / RDO correlation tools, such as MS Admittance and its queries or use MS SQL Ma?tre d' Allied Head waiter practice with OPENROWSET statements. So, lets affect that you are on MS SQL Server. You have all in all two options eConnect (you must pay for the reg key/license and this is SDK) and custom stored procedures. We'll only be concerned about custom stored procedures way here:

1. Stored Procs. The first difficulty is - are we permitted to build stored proc in Great Plains DYNAMICS and companies databases. The fulfil is Yes - conflicting to such goods as Microsoft CRM (where you are banned to build any custom balk in MS CRM database, and as a substitute you conceive your own custom folder and place all your procedures and views there) - you are confident to coin your stored procedures and place them in both DYNAMICS and Business databases. You need to know the anatomy of Great Plains tables structure.

2. Tables Structure. If you launch Great Plains workstation and adhere to this way: Tools->Resource Descriptions->Tables - then you are in tables descriptor, arrangement by tables Physical, Consistent or Tables Group Mechanical names. This is all Great Plains Agility architecture realm and it is more or less byzantine and not "developer-friendly" - but if you build check out transactions in Great Plains - you can assume out where data must be populated.

3. Sales Order Processing. Or SOP module. This is commonly the core of eCommerce education - transactions ought to go into SOP tables (with SOP prefix): SOP10100, SOP10200 and others. If you are promotion to your accessible customers, then customers are in Receivables Management module (AR) with AR prefixes: RM00101 - is Client Master, RM00102 - buyer deal with master, etc.

4. Sales Order/Invoice Allocation dilemma. Great Plains SOP module is running in concert with List control, construction allocation of inventoried items in IV. So, this is very challenging to duplicate allocation logic. We commend do not allocate in Commands and Invoices and do allocation by operator, who processes the internet commands batch.

5. Sales Order assigning dilemma. If you are using eConnect - this is kind of issue, so you have to attract to GP home architecture and do it with the stored procs approach.

Good luck with implementation, customization and integration and if you have issues or concerns - we are here to help! If you want us to do the job - give us a call 1-630-961-5918 or 1-866-528-0577! help@albaspectrum. com

Andrew is Great Plains specialist in Alba Spectrum Technologies (http://www. albaspectrum. com) - USA countrywide Great Plains, Microsoft CRM customization company, helping clients in Chicago, Houston, Atlanta, Phoenix, New York, Los Angeles, San Francisco, San Diego, Miami, New Orleans, Toronto, Montreal and having locations in numerous states and internationally

Developed by:
home | site map © 2018