GAHZLY

The World of Corporate MRP systems is full of surprises. If in the late 1990th major ERP market players: Oracle, SAP were trying to realize the strategy of releasing so-called ‘light’, ‘select’, ‘express’ versions of their high-end ERP – the idea is very simple and attractive – if your corporate ERP application could be written on one CD (or several CDs) – why not to try the game when you disable 70% of the functionality and release ‘lite’ version? The real world kind of accepted and a the same time rejected this movement from the up to the down – as would it funny to realize, but the issue was – this is still the same heavy-pace ERP application and its implementation cycle is of course reduced, but not substantially and not enough to fit to mid-size and small companies. Plus – these heavy-weight applications were targeting super and mini computers, when Intel-based Servers achieved and surpassed the ...

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 Transactio...