Crypt Trials Technology » Customizations

Dynamics GP Technology Partner: Great Plains Customizations and Integrations Support

admin — Tue, 15 Jun 2010 22:20:23 +0000

Modern ERP, MRP, Sales, Purchasing and Accounting systems, being implemented, have to coexist with company computer network and legacy applications infrastructure: EDI, eCommerce, Groupware, various industry applications, reporting. We assume that the decision to implement Microsoft Dynamics GP was made in several comparison cycles, where you have seen competitors: SAP Business One, Accpac, MAS 90, and you are now ready to begin Dynamics GP custom add-ons implementation, and if these are too expensive or do not exist for your Corporate ERP business requirements, this small publication should give your GP custom development perspectives:

1. Dynamics GP customization specification writing, programming, testing and version upgrade. Specification is first step and it often is decisive in the success of failure. We encourage you to involve your Dynamics GP ISV partner in this process. If you are in partner selection process, please, check with your prospects if they have your industry GP implementation and modification expertise and if they carry in staff Dexterity, eConnect programmers with multiple years of coding experience. For programming and testing phase, based on our experience, we recommend you either to dedicate separate Testing Server or do QA and Testing on the copy of you GP production company. Custom logic is often your settings and data driven and it is too generic to test in GP Lesson Company. GP Custom Add-on has its own life cycle, most important is to plan its code review for each Dynamics GP version update. This paragraph was for IT directors, we tried to be not too technical

2. Great Plains Customization tools. Being mid-market ERP, GP has various tools and modification options. We will list them here and you will need to come through others FAQ style articles to get more info on each one to make your homework done. eConnect is perfect new set of libraries and SDK sample code snippets – if you are experienced or even probing your after college steps Microsoft Visual Studio C#, VB or other .Net language programmer, you may quickly familiarize yourself to eConnect and make introduction programming exercises. eConnect allows you to manipulate master objects (Customer, Vendor, Employee, GL Account, Address, etc.) and Work Transactions (SOP Invoice, Order, POP Purchase Receipt, etc.). Microsoft Dexterity, formerly known as Great Plains Dexterity, it is the shell of Dynamics GP user workstation and it is part of current architecture on the data structure level. Dexterity is more proprietary, comparing to eConnect, for example, and we do not recommend you to consider programming Dex in-house. Dexterity programmer has complete control over GP objects and such GP Add-ons as Alba Spectrum Posting Server is coded in Dexterity Sanscript, where our Software Development Factory Programmers had access to Dex native procedures and functions and that would not be possible in C#, SQL or other non Dexterity programming

3. Integration Tools. Here you should consider eConnect and Dexterity, especially eConnect as integration typically feeds something like Sales Orders and Customers from your ecommerce website, or EDI compliant Purchase Orders. However, if your objective is not customization, but rather pure integration, please review Dynamics GP Integration Manager module. It was recently redesigned with eConnect connectors, meaning that you can deploy eConnect logic and performance even if you are not a software developer, but rather business logic savvy end user. Plus in IM you can tweak integration logic in event driven scripts: before integration (where you set up global parameters, such as date, exchange rate), before document commit (where you check and modify document parameters before saving them in GP). With IM you typically expect integration on demand, meaning that GP user should launch integration manager manually. It is definitely the most popular way, however you can also schedule IM with Windows macro based third party small programs, and we even saw the scenario, when ecommerce computer parts and service reseller implemented real time IM integration by calling it every 2 minutes

4. Dexterity Custom Add-On upgrade. If your custom module coded in Dexterity triggers exclusively – you might be lucky in just reapplying Dex chunk file to new version Great Plains workstation. For the rest of us, especially when you had to alter existing GP windows, consider some budget for Dex customization upgrade

5. Barcode integration in retail, wholesale, shipping and receiving, logistics. Please, refer to our recent articles on these subjects. You should decide on Barcode scanning integration point, plus if you are OK with Batch mode or need real time Barcoding data upload

6. EDI Integrations. Here you likely have to read these lines if existing Dynamics GP ISV EDI add-on is too expensive or you believe that you can program EDI integration in SQL Stored Procedure or simple eConnect programming

7. Great Plains Customization in International Environment. Please, note that Dexterity is not compatible at least in its current version 10.0 with Unicode. If you plan to roll out Dynamics GP in the subsidiary in China, Korea, Japan, Thailand, Burma, Vietnam, Cambodia, please give us a call on your possible options. If you plan to implement simple GP interface in European language: Bulgarian, Russian, Lithuanian, Polish, Czech, Slovak, Serbian (when tax compliance localization requirement is not a concern), you may consider to translate Dexterity strings from English into your local country language

8. Consolidated GP Reporting. Here we recommend you to deploy FRx financial reporting with Reporting Trees, Multicurrency

9. If you need additional help, please call us: 1-866-528-0577, internationally 1-630-961-5918, help@albaspectrum.com or skype: albaspectrum. We would be happy to give you your industry case from Great Plains customization and integration perspective, as well as to give you second opinion, if you are not happy with your current Dynamics GP Partner support level

Microsoft Dynamics Gp ? Typical Customizations

admin — Wed, 23 Sep 2009 20:56:51 +0000

Microsoft Great Plains, currently new name in Microsoft Dynamics family is Microsoft Dynamics GP, originally this ERP package was created by Great Plains Software as Great Plains Dynamics in earlier 1990th as Great Plains Dexterity application. Microsoft Great Plains tailored business logic or professional modifications were initially made back in late 1990th in Great Plains Dex, this IDE has it own C-shell based scripting language – sanscript. MRP package at that time had similar customization capabilities: SAP had ABAP, Axapta – Morph X, X++, Navision – C/Side. When Microsoft purchased Great Plains Software and formed Microsoft Business Solutions, Dexterity core of GP was deemphasized (however it stays and not going anywhere), instead Microsoft BS opened GP objects for Microsoft Visual Studio C# and VB.Net developers via new tool – eConnect. eConnect obviously is not a miracle and it replicates Dex logic in SQL stored procedures – meaning that eConnect is definitely step forward to make Microsoft Great Plains more open MRP platform, but this step is rather evolutional, not a major revolution. Let’s review typical GP modification scenarios

1. eCommerce. GP is now open ERP or accounting backoffice, thanks to eConnect. Good approach in eConnect software development is calling XML web services scenarios. If you have already practiced eConnect e-commerce development, you should come to the dilemma of eCommerce invoices automatic posting. eConnect doesn’t do posting job and it is understandable, as eConnect is build upon Great Plains Dexterity architecture, where posting is left to GP operators

2. EDI or Electronic Document Interchange. Traditionally EDI is considered as fixed length fields standard, new approach is XML data interchange, including XML web services. In the case of Microsoft Great Plains both approaches could be relatively easy realized on MS SQL Server scripting level, where you deploy such statements and constructions as convert and cast to program fixed field length

3. Sales Order Processing module modifications. SOP is one of the most popular custom logic scenarios. If you think about deploying custom logic in GP user workstation, then more likely modification should be programmed in Dexterity. If Dex is too complex, especially if you plan to customize GP in-house, then consider GP Modifier with VBA

4. Modifier with VBA (Visual Basic for Applications). This tools is related to older Microsoft OLE technologies – customization of Microsoft Office Excel, Word, PowerPoint, etc

Great Plains Customizations: Dynamics Gp Add-ons

admin — Wed, 09 Sep 2009 10:13:54 +0000

Microsoft Dynamics GP has various customization options and tools, which should fit to your specific modification need. However as typical mid-market ERP it requires tools research prior to performing custom programming. Let’s quickly review the tools:

1.       eConnect. This is the most modern and really cool SDK. If you are Microsoft Visual Studio C# or VB.Net programmer and you are reasonably good with SQL stored procedures, you should invest your time in eConnect research. However there are some drawbacks in eConnect programming: it is rather for integrations, and it is difficult to modify GP screens with eConnect – use rather Modifier with VBA or Dexterity for that. Also, eConnect doesn’t post batches in GP – consider deploying Alba Spectrum Autoposting Server to extend eConnect with batch posting logic

2.       Microsoft Dexterity. Former name was Great Plains Dexterity. This tool allows you to break through virtually any limits of other tools. Well, of course there is the learning curve – Dex is not rapid customization option, it requires long programming experience in order to produce professional and competitive Dexterity coding

3.       VBA and Modifier. This tool is rather legacy, however it is and was very popular, as simple and really quick modifications could be automated with simple VBA scripting. If you plan to do database update, select and insert statements – you can deploy ADO technology in your VBA code

4.       SQL direct scripting. If you are very advanced SQL programmer and DBA, then you probably like to disregard all the tools and try or rely on your experience in SQL stored procedures coding. Please, review GP SDK (install it from CD #2)

5.       Integration Manager. IM module also opens modification possibilities, related to data translation, VBA coding. In GP version 10.0 IM you will find eConnect connectors, which are breaking through former IM performance limits

6.       Third Party Add-Ons. At this time (June 2008), GP ISV products are written in Great Plains Dexterity and are distributed via Dex chunks technology. However there is the trend to adopt eConnect in the third party add-ons, related to eCommerce integration products

Great Plains Reseller: Econnect Integrations and Customizations Highlights

admin — Mon, 07 Sep 2009 15:39:51 +0000

Microsoft Dynamics GP could potentially go beyond its out-of-the-box standard functionality and you as software programmer and developer could deploy it as ERP platform for your company ecommerce, EDI, wholesale and other extensions and integrations. In this publication we would like to concentrate on eConnect programming and technology. Please, note that eConnect should be considered as solid SDK for C# and VB.Net developers, however for older versions of GP, such as 7.5, 8.0 and probably even 9.0 – we recommend you to upgrade to version 10.0, prior to investing into eConnect research and programming:

1.       GP 10.0 Integration Manager. Here you already have eConnect connectors in place. If you are familiar with old OLE based IM, then you need to know that eConnect Integration is per company, opposite to the old way when you login the company and run integration just for this company. Plus, cancelling old restrictions – Integration, based on eConnect connector doesn’t require you to run Great Plains client workstation. If you are OK with what Integration Manager gives you, then you probably should stop reading. For the rest of us, please know – if you need custom fields population via IM, then you have to deploy old way ADO in before document commit script

2.       Beyond IM. Deploying eConnect, you can combine GP data feeding with eConnect methods and custom tables updating via SQL custom stored procedures or update statements. In this scenario eConnect becomes one of the players

3.       eConnect technology. You probably already have read bunch of whitepapers and technical manuals, where you saw multiple eConnect technology layers. At the beginning of the way, eConnect has a set of encrypted SQL stored procedures, allowing you to create, update and delete GP objects

4.       eConnect restrictions. Here you need to know GP architecture and especially batch posting logic. Batches supposed to be posted by GP users exclusively, this is why eConnect doesn’t have posting features. In order to post batches from your eCommerce, EDI or another programmed application, you should deploy Alba Spectrum Batch Posting Server

5.       eConnect and GP Dexterity. Dex can call DLL libraries, and so eConnect could be exposed to Dexterity customizations. This is especially helpful for GP developers, who are trying to automate Great Plains intercompany transactions via dex custom add-ons

6.       Technology notes.   If you are not technical in GP integrating projects, this article could be potentially too challenging to read through. However we believe that IT technicians, who are facing the GP integration project would benefit from reading this publication

Great Plains Customizations: Dexterity, eConnect, SQL Scripting

admin — Tue, 18 Aug 2009 21:32:01 +0000

Microsoft Dynamics GP ERP or formerly known as Great Plains Dynamics and eEnterprise accounting, logistics, manufacturing, sales order processing, purchasing, MRP, warehouse management application fits to the majority of companies in USA, Canada, Mexico, Central and South America. In this small publication we would like to give you sort of Dynamics GP modification orientation session, assuming that you are technology oriented IT specialist, who is supporting Great Plains internally. Before we jump into GP programming world, please note that Great Plains doesn’t support Unicode characters: Chinese, Korean, Japanese. Plus, it depends on SQL Server collaterals and accents, so in order to translate Great Plains screens to such languages as Lithuanian, Russian, Latvian – you will need to install SQL Server with appropriate collation. Now to the topic:

1.       Microsoft Dexterity, formerly known as Great Plains Dexterity, it is the shell, written in C Programming language, which in turn has its own Sanscript scripting language and Software Development Environment. Dex allows you to integrate your add-on into Dynamics GP security realm as well as User graphical interface. Dynamics GP Dexterity is not open source programming language, so you should not expect to turn your own in-house programmers to begin coding in Dexterity overnight or even over couple of months. Dexterity also is dependent on Great Plains tables and screens structure, so our opinion is simple – subcontract Dexterity customization project to your Great Plains Technology Partner

2.       Dynamics GP eConnect. Initial remark on eConnect – prior to thinking on eConnect programming, consider upgrading Great Plains Dynamics GP to version 10.0 or at least 9.0 – eConnect was introduced for Dynamics GP 7.5, however you should allow some time for GP customization tools to mature. eConnect is C#, VB.Net and SQL programmer friendly, you have to be familiar with Great Plains objects: Customer, Vendor, GL account, SOP Invoice, POP Purchase Order, Payroll Employee, Customer Address, etc. eConnect to some extent replicates Great Plains Dexterity business logic, however it does it in more Object Oriented Programming manner

3.       SQL Scripting for Dynamics GP Great Plains. It is certainly a temptation for SQL coder to begin GP integration project in direct SQL insertion statements. We respect this and admire your brave aspiration. Please, take, however, into consideration the fact that eConnect is already written in SQL stored procedures, so you should not probably try to recode eConnect – instead consider deploying it

Microsoft Dynamics GP Partner Chicago: Great Plains Customizations

admin — Sat, 08 Aug 2009 19:40:07 +0000

If you are deploying Microsoft Dynamics GP, formerly known as Great Plains Dynamics, Microsoft Great Plains (and their predecessor Great Plains Accounting for DOS, Windows and Macintosh), we would like to review Great Plains customization support options in Chicago, Northern Illinois, North Western Indiana, Southern Wisconsin. Special emphasis on Dynamics GP software development, integration, custom programming and modifications. If you have legacy version of Great Plains Dynamics or Great Plains Accounting, your options may differ, but we still should be positioned to help you with legacy Great Plains system recovery, redeployment on new Windows 2003 or 2008 server, including Great Plains Dynamics (and GPA) on Pervasive SQL Server 2000. For new Dynamics GP customers in Chicagoland metro area we already described Microsoft Dynamics GP 11.0 and 10.0 licensing schemas and pricing policies, feel free to give us a call. If your Dynamics GP implementation was screwed up by local Dynamics GP VAR, feel free to ask for second opinion and likely to preserve investment into GP software licenses:

1. Dynamics GP Customization Tools. Historically, and still now in 2010, the customization tool of choice is Dynamics GP Dexterity. Dex was architectured in earlier 1990th as the Shell coded in C programming language. C was expected to outlive competing DB and Operating System platforms, such as Oracle, DBII, Microsoft Windows, Unix, Solaris. Now we know that those old good days concerns are no longer actual and we are living through different paradigms (Internet, Thin Clients, Web Clients). Whatever is the history, Great Plains Dexterity is very popular in GP customizations, as it allows you to incorporate custom modules directly into Dynamics GP security realm and user interface. Dexterity programming should be outsourced to Dex developers with at least several years of experience, or better to Dynamics GP Dexterity technology partner, who is in Dexterity Source Code program. If you are trying to recover and upgrade Dexterity customization, please be sure that you have Dynamics.dic or Extract.dic dictionaries with Dexterity Sanscript codes

2. Dynamics GP eConnect. This is new paradigm in Microsoft Dynamics GP technology, where Dexterity logic is rewritten in SQL Stored Procedures (encrypted, so you cannot alter them). Initially eConnect was dedicated to GP ecommerce programmers to open up Great Plains objects for ecommerce integration (Customer, Inventory Item, Sales Invoice, Price List, Address, etc.). Later on with eConnect success, its methods were expanded to cover most of the Dynamics GP modules: General Ledger, US Payroll, Purchase Order Processing, Bill Of Materials, Project Accounting, Accounts Receivable, Accounts Payable, Bank Reconciliation. Please, note that some of the Dynamics GP modules are not covered in eConnect, for example Invoicing module (which was historically budget option to Sales Order Processing). eConnect also is lacking Batch posting logic, and if you would like to post your GP batches directly from ecommerce web application (Microsoft Visual Studio C# or VB.Net project), you would need to review and deploy Alba Spectrum posting server

3. Dynamics GP Extender – it is Microsoft Dexterity shell, which allows you to modify GP logic without being Dexterity programmer. Enterprise version of Extender, available from eOne allows you to include Dexterity scripts (Sanscript codes). Extender innovative idea is really great, however some drawbacks are related to Extender performance, especially for new Dynamics GP versions 11.0 and 10.0

4. Dynamics GP Modifier with VBA. This technology is a bit outdated, but very efficient. You can modify Dynamics GP existing screens by placing new fields (editable field, push buttons, etc.) and activating them by associated VBA scripts

5. Give us a call: 1-866-528-0577, help@albaspectrum.com

Great Plains Consultant: Dynamics Gp Dexterity Customizations

admin — Sun, 05 Jul 2009 19:20:44 +0000

Microsoft Dynamics GP ERP application was initially designed and coded in Great Plains Software Dexterity. Dex is in turn EDI and shell, written in C++ programming language. Dexterity is tightly interrelated with Database structure, it has its own indexing, typically working with MS SQL Server primary keys and indexes. Plus Dex has its own scripting language (which is not interpreted, but compiled) – Sanscript. GP Dexterity might be not the first modification option, you like to try – you can first research such tools as Modifier with VBA, eConnect, Extender, but if you think your custom add-on should be seamlessly integrated with GP user interface and security realm, then Microsoft Dexterity programming is the way to go. Let’s come through Dex highlights:

1.       Dexterity developer selection. If you need Great Plains technical consultant with Dexterity programming expertise and certification, you typically find these specialists working for mid-size or large regional Great Plains VAR or Reseller. It might be tough project to lure in Dexterity developer on short term contract. If you think Dexterity coding could be learned in short period of time – this might be too optimistic opinion. Dexterity programmers need several years of experience to be comfortable to work on their own to spec out Add-Ons appropriately and then do the coding job, close by its quality to accepted Dex programming standards and guidelines

2.       Outsourcing Dexterity Custom Programming to subcontractor. This way is in our opinion the most optimal. Dexterity Software Development Factories are available through major Microsoft Dynamics GP partners and resellers

3.       Dexterity Technical World. Dex Add-Ons are distributed via so-called Dexterity chunks, which makes the process very flexible and open for remote support via web sessions, VPN and remote desktop connections. Sanscript is cursor driven programming language, however you can call SQL stored procedure from Dex code to get advantage of SQL selection aggregation. Dexterity debugging – Dex could be installed on your test server and Dexterity programmer could work with your system remotely, debugging flawing raw code, as part of QA procedures

4.       eConnect power and limitations. eConnect has SQL encrypted stored procedures as technology base. In various scenarios eConnect replicates Dexterity logic on SQL scripting level and exposes GP object to C# or VB.Net programmer. The strong point of eConnect is the fact, that you can get generic .Net programmer to code your GP objects directly in MS Visual Studio, the only recommendation is familiarity with MS SQL Server scripting. However eConnect doesn’t have all the power of Dexterity – especially this is seen when you need to post Great Plains transactions and batches. eConnect works with master records and work transactions only and it lacks posting logic, meaning, for example that e-commerce developers can’t post GP batches automatically without add-on, such as Alba Spectrum Posting Server

Dynamics GP Software Developer Notes: Great Plains Customizations

admin — Sat, 06 Jun 2009 16:17:31 +0000

Microsoft Dynamics GP is reasonably open for various custom integrations and user interface extension projects through several programming and software development tools: Great Plains Dexterity, eConnect, Extender, Integration Manager with VBA scripting, Modifier with VBA, plus you can always do program ecommerce web extensions and integrations via SQL Stored Procedures or eConnect with generic C# or VB.Net web programming project. This small publication is a review of these tools and options in the bullet style format:

1. Dexterity. This tools is original architecture foundation, it was designed in earlier 1990th as the shell for Great Plains Dynamics. Dexterity has its own scripting language, which is in fact compiled – Sanscript. Dexterity programming allows you to control and alter every existing GP object, plus you can do all sort of custom add-ons. If you do not have Dex programming experience, you might be discouraged by its complexity, however there are Dynamics GP customization project, where you have to code in Dexterity, especially when you have to call GP native logic, meaning calling such processes as Batch Posting from your custom module. Consider outsourcing Dex programming routines to Dynamics GP ISV Partners, who maintains Dexterity Software Development Factory

2. eConnect SDK. In your MS Visual Studio C#, VB or another programming language project you can include eConnect libraries and quickly learn on eConnect code snippets how to program various GP objects: Customer, Vendor, Item, Address, Sales Invoice, Customer Payment, etc. Initially eConnect was introduced for ecommerce developers, however for Dynamics GP 10.0 and to some extent 9.0 eConnect covers most of the business logic (except Posting and working with Posted and Historical data). We recommend you to try eConnect programming on your own if you are MS Visual Studio Programmer and work for the company where you plan Dynamics GP integrations, especially for eCommerce. We are kind of resisting to recommend you eConnect if you on Dynamics GP 8.0 or 7.5, in our opinion it is more efficient to upgrade to Dynamics GP 10.0 and then deploy eConnect programming for current GP version

3. Modifier with VBA scripts. GP Modifier allows you to change existing GP window layout (rename the field, change its position) plus add new fields and attach custom VBA scripts to them. We recommend this tool for simple modifications, and for heavy customizations consider Dexterity, Extender or eConnect

4. Dynamics GP Integration Manager Custom integrations. IM is user friendly integrations tool, however if you are VBA or Microsoft Office programmer, it should be easy for you to further advance integration logic by Before Integration, Before Document Commit and other event driven scripts

5. SQL Scripting in Dynamics GP. Theoretically, most of the scripting is already done in eConnect, as this SDK is duplicating Dexterity code in SQL encrypted stored procedures. However if you think that eConnect learning curve is too long and you would like just to glance and GP tables structure and begin SQL scripting – then please install Dynamics GP SDK from CD #2 or look at the tables and forms descriptions: Dynamics GP->Tools->Resource Descriptions->Tables

6. Extender. This Dynamics GP modification tool is friendly for non technical Great Plains Consultant. Extender itself is written as the Dexterity application or add-on. If you think that Dynamics GP native Extender is too restricted, consider calling to Extender Dynamics GP ISV in Australia to get Enterprise version

7. Dynamics GP Barcoding Custom Add-Ons. Barcode Scanning in Retail, Warehouse Management and Supply Chain Management should be first analyze on the subject where is integration point or in which Dynamics GP Window you would like to program this integration. Plus you should also consider Barcode inventory Items Labels printing and Barcode new item algorithm

8. Great Plains earlier versions customization support. If you are on Great Plains Dynamics or eEnteprise 7.5. 7.0, 6.0 or Great Plains 5.5, 5.0, 4.0, 3.2, 3.0 then you should consider GP Dexterity customizations, plus VBA with Modifier or Integration Manager. For old Great Plains versions you might have such old ISV as Intellisol Advanced Purchase Order Processing and Project Accounting, where you would have to consider migration to Dynamics GP Purchase Order Processing. For Great Plains Accounting for DOS, Windows or Mac customization options were more limited and now these archaic ERP and MRP applications are no longer supported

9. Dynamics GP Customizations Support Internationally. Here you should consider ERP localization in the senses of local tax code compliance and adoption of local country language. Dynamics GP is distributed in USA, Canada, including French Quebec version, UK, Australia, New Zealand, Oceania (Palau, Fiji, Tonga, and other island countries), South Africa, Southern and South East Asia, where English is official business language. It is also localize in Spanish Speaking Latin America and Caribbean countries. If you are located in different country, please consider possibility of Dexterity strings translation from English into your native language

10. Alba Spectrum Dynamics GP ISV products. At this time, August 2009, we are offering Dynamics GP Posting Server or Autopost, Order Connector, GP Integration with Microsoft RMS

11. For additional help, please call us 1-866-528-0577, help@albaspectrum.com skype albaspectrum. We specialize in Dynamics GP Customizations, Reporting, eConnect Programming, EDI, Integrations, International Support in Russian, Spanish, Portuguese, Chinese. Plus we are comfortable to help you with Great Plains Integrations with PHP, Java, Linux, Oracle, MySQL, MS Access, Excel. We also support SAP Business One SDK, Workbench customizations and integrations

Sap Business One Sdk Programming and Customizations

admin — Tue, 17 Mar 2009 00:22:41 +0000

SAP B1 is modern small business and lower mid-market ERP and even MRP, as it has discrete manufacturing and material resource planning modules, as you can expect has neat and nice modern interface and technical exposure to programmers, especially C# and VB.net coders through SAP BO SDK or Software Development Kit. In SAP Business One as with other accounting applications, we always recommend you first to research its native business logic, then if it doesn’t cover required functionality, review add-ons or SB1 ISV third party products or extensions, and if there is nothing out there yet, then you should consider your own custom logic design and development. Let’s review SDK and its typical integration, modification, data massage scenarios:

1. SDK project setup. Here you need Microsoft Visual Studio and connection to SB1 server. If you are C# software developer, you may think that you can easily do the custom programming on your own, however SDK requires some exposure to SAP B1 business logic and objects structure. This is why subcontracting the project to professional SB1 SDK ISV may be good option

2. Typical scenarios. Let’s first talk about integrating your legacy database or ecommerce website with SB1. Here you have to establish connection to SB1 as the system, then to the company, then you create your SB1 objects in SDK: business partner, Sales Quotation, Order or Invoice as the most typical scenario. If you are taking leads from the internet and want your sales people to process them, you may consider the algorithm to check if the lead is an existing customer (by matching company name, phone number, email, etc.) and then either attach newly created opportunity to the lead or the existing customer

3. GUI extensions. This is where you plan to change Graphical User Interface. These customizations are more vulnerable to version upgrades as you do not know what SB1 native developers plan to change in GUI in the coming version. If this warning doesn’t seem to be the showstopper to you, then you can go ahead with modifying or in essence altering or tailoring user interface

4. SQL scripting. We know from our experience that some SQL scripting is needed to fuel your SDK development with such nice nuances as the next document number, etc.