Do’s and Don’ts – SAP Business One SDK or Software Development Kit

How ERP Stock Calculation Impacts ECommerce Sales

SAP Business One Software Development Kit or SDK, all of the SAP Business One Customers and Partners are aware of this toolkit. Many partners provide solutions using this tool which serves several additional features and extends the SAP Business One Feature List, for example,

  • Connector Solutions – Connecting SAP Business One with third party systems like eCommerce, CRM, SCM, POS. For example, APPSeCONNECTiVEND
  • Country Packages – Country specific customizations are predefined in SAP Business One. For example, Coresuite Country Packages
  • Tax Solutions – Complex tax calculating solutions, for example – Avalara
  • Shipping Solution- Pick & pack and shipping solution, for example – Processweaver
  • Usability and Productivity Packages to efficiently use the software from Boyum IT
  • Credit Card Processing in SAP Business One, for example, iCharge and many more.

What is SAP Business One SDK?

SAP Business One SDK is a toolkit which contains programming interfaces, utilities and documentation which allow programmers to add custom features in the ERP or interface with external applications. SAP Business One has a business object layer and user interface layer, SDK has access to both these layers and using its capabilities SAP Business One admin users can extend its features to suit the business needs.

Let’s have a quick idea what advantages SDK Provides:

  • Access to SAP Business One Business Logic through an Object Oriented Programming Layer
  • Supports a wide variety of Programming Languages and Tools provides the developers to use their familiar technology. Usually .Net Platform C# are widely used as the Programming Language.
  • Supports SAP Business One Version or PL Upgrades, usually no re-work or very additional work is required.

Components:

  • Application Programming Interface for Data Interface (Widely known as DI API) to connect external applications.
  • API for User Interface (UIAPI)
  • Screen Designer with Drag and Drop Features – For designing custom screens.
  • Java Connector – Connecting External applications through Java as the Programming Language.
  • Cool idea’s about the best practices to use this useful toolkit:

Do’s

  • SBO_SP_TransactionNotification can be used for both propagating information about the change in a Business Object (UDO or standard SAP Business One) as well as interrupting (i.e. rolling back) the propagated transactions.
  • For pure transaction propagating purposes, SAP recommends using the newly introduced stored procedure: SBO_SP_PostTransaction Notice.
  • Use data interface object using DI API or DI Server to add new data in SAP B1.
  • Use data interface object using DI API or DI Server to update data in SAP B1.
  • Use data interface object using DI API or DI Server to update data in SAP B1.
  • Use UDT to create the custom table in SAP B1.
  • Use UDO to access the custom table using DI API or DI server in SAP B1.
  • Use proper namespace conventions to avoid conflicts in between add-ons.
  • Use application events to perform add-on cleanup operations.
  • Use language change event to give multilingual support of add-on.
  • Use message window to display a critical message which is required for user inputs.
  • Use status bar messaging system to display Error/info in the case of no direct inputs required from use.
  • Use title case to define label text.

Don’ts:

  • Do not add trigger and store procedure by Add-on Solution.
  • Do not use trigger and store procedure by Add-on Solution.
  • Do not update SAP B1 Store procedure SBO_SP_TransactionNotification and SBO_SP_PostTransactionNotice using Add-On Solution, automatically it may conflict with SAP B1 other processes.
  • Do not use SQL statement using DI API & DI Server to add new data in SAP B1.
  • Do not use SQL statement using DI API & DI Server to update data in SAP B1.
  • Do not Use SQL statement using DI API & DI Server to update data in SAP B1.
  • Do not create a custom table directly in SAP B1 Database.
  • Do not show critical messages in status bar.
  • Do not use window size more than 800×460 when you define a form.
  • Do not use punctuation at the end of the label text.
  • Do not formulate Label Text as questions.

Connect Ecommerce with SAP B1

You may also like:
Our Partner, CEO Consultoria Wins ‘Channel with Best Performance in SAP B1′
Webinar- Connect Third Party Systems with SAP B1 – DI API, DI Server, B1WS
Webinar: Connect SAP B1 with apps using Service Layer (HANA)

 

Subhajit Goswami

Subhajit is a Business Development Professional with ability in managing Customer Accounts and Channel Business. His specific interest is in the areas of Retail Industry and eCommerce, Multichannel eRetail and ERP Systems.