Scheduling SAP Business One Customizations and Integrations with SDK Libraries

SAP B1 is friendly to Microsoft Visual Studio programmers through its so-called Software Development Kit. In the next version 9.0 scheduled for the fourth quarter of 2012, it is renamed ‘Business One Studio’. Let’s do a short technical introduction and then try to talk about case studies and get answers to popular questions. Let’s start with the categorization of the SDK:

1. User interface API. The User Interface API provides programmatic access to windows, menus, and events in SAP Business One. The User Interface API allows you to create new windows, modify existing ones, add new business logic, add or modify menu menus. apps and more ‘. After the presentation of the ‘Help Center’, we would like to mention that the modification of the user interface could be vulnerable to future projects such as updates. We prefer to recommend that you focus on the type of integration projects and see the next paragraph

2. DI API. The DI API provides a programmatic interface to SAP Business One through a set of fully functional business objects. The DI API provides access to the business logic and data access layers of SAP Business One ‘. It is much easier to review the integration code and recompile it with the new version DLL set.

3. DI server. ‘The DI server is an extension of the DI API and supports all of its objects. It is designed for high-volume data integration, where numerous client connections must be managed simultaneously and optimized for speed. Also suitable where web services architecture is preferred. ‘Here you should think about maximum performance.

4. Code samples are available in C # and VB. This is one of the reasons why you should consider encoding in these languages. However, if you are comfortable translating into your favorite .Net compatible language, feel free to implement it

5. Table structure. Here you have to combine the client interface and the SDK. Log in to B1 and in the menu View-> System Information check it. Open the form where you need to know the table and hover over and read the field and table name in the lower left corner. Type the name of the table and search for it in the Help Center. Try the following exercise. Open the Sales order form and hover over the Customer field. And you should see the Name CardCode field and the ORDR table. Then check out this table in Help Center Search. If you are comfortable finding the table on your own directly in the Kit, go to Customization Tools -> Database Table Reference

6. Integrations. It is recommended to first create user-defined tables in the client application and then use them as test objects. You can import records into that table directly through the SQL insert statement, as it does not participate in the core business logic. The next step is DI API programming in Visual Studio, where you can read records from the staging table and create AR invoices, purchase orders, etc.

7. Integration with Linux and PHP. This is a frequent request due to the fact that custom eCommerce portals are often hosted on MySQL on the Linux platform. A good recommendation is to consider SOAP XML Web Service with SDK libraries. The web service is independent of the computing platform and can be called from Linux