Sap Business One Sdk Programming and Customizations

By: Andrew Karasev

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.

Enterprise Information Systems
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 

» More on Enterprise Information Systems