SAP B1 has several tools to enable integration with your legacy system, e-commerce, etc. In this small article, we would like to give you highlights about SAP Business One SDK integrations. These integrations require Microsoft Visual Studio.net C# or VB programming skills. A typical SAP BO integration would move sales orders into SAP B1 sales orders
o Provisioning table. You need to move your e-commerce transactions to the staging table, preferably in MS SQL Server where SAP BO is hosted. Use stored procedures when required, you can perform heterogeneous queries to retrieve transactions from Oracle, IBM Lotus Notes Domino or any other database platform
o SAP BO SDK loop. You should open the connection to SAP BO company via SDK. We won’t give you a code example here, we expect medium SDK coding experience. When connected, read your staging spreadsheet and create one sales order at a time – or alternatively create one sales order and add items at a time
o Flag imported transactions. In the staging table, you should either delete imported transactions or mark them as imported, depending on your choice
o AR invoice. We do not recommend adding an invoice to the integration. The reason is simple – the invoice is not saved in the batch – it should be posted – and we don’t recommend you to check posted invoices – to cancel them you have to enter credit notes, which would mess up your entry
o Other integrations. With the SAP Business One SDK you can create, change and manipulate practically all SAP B1 objects. In this article we showed you customer orders. You can also update or add customers, suppliers, etc.
Please do not hesitate to call us for SAP Business One integration scenarios: 1-866-528-0577, 1-630-961-5918, firstname.lastname@example.org or Skype: albaspectrum