SAP B1 has multiple tools to enable integration with your legacy system, eCommerce, etc. In this small article we would like to give you highlights on SAP Business One SDK integrations. These integrations require Microsoft Visual Studio.net C# or VB programming skills. Typical SAP BO integration would move customer orders to SAP B1 Sale Orders
o Staging Table. You need to move your eCommerce transactions to staging table, preferably in MS SQL Server, where SAP BO is hosted. Use stored procedure, if required you can do heterogeneous queries to pull transactions from Oracle, IBM Lotus Notes Domino or another db platform
o SAP BO SDK Loop. You should open connection to SAP BO company via SDK. We will not give you code sample here, we expect intermediate SDK coding experience. When connection is established – you read your staging table and create Sales Orders one by one – or alternatively you create one Sales Order and add items one-by-one
o Flagging Imported Transactions. In staging table you should either delete imported transaction or flag them as being imported, your choice
o AR Invoice. We do not recommend you to add invoice in integration. The reason is simple – invoice is not stored in the batch – it should be posted – and we do not recommend you to review posted invoices – in order to reverse them you will need to enter credit memos, which will create a mess in your data entry
o Other Integrations. SAP Business One SDK allows you to create, modify and manipulate virtually all SAP B1 objects, in this article we showed you Sales Orders, you can also update or add customers, vendors, etc.
Please feel free to call us on SAP Business One integration scenarios: 1-866-528-0577, 1-630-961-5918, help@albaspectrum.com or skype: albaspectrum
AUTOPOST by BEDEWY VISIT GAHZLY
