Selection Guide

How to connect eCommerce to SAP and Dynamics

How your eCommerce can be connected to enterprise ERP's like SAP ECC, S/4HANA and Dynamics 365 Finance and Supply?
An iPaaS makes all your connections visible and understandable on its user-friendly graphical interface, makes it easy for system integrators or agencies to quite literally be on the same page with project managers and C-level, when planning tweaks, improvements or budget allocations on their system integrations.

How to connect eCommerce to SAP and Dynamics

SAP S/4HANA and Microsoft Dynamics 365 Finance and Operations are one of the most renown enterprise ERP systems on the market. As our environment continues to strive for complete digitization and a 360° customer satisfaction, merchants are looking towards creating an omnichannel experience and digitalization through integrations between these ERPs and the eCommerce platform.  

More often than enough, when starting an integration project with these giant ERP’s, you end up with these consultants entering your project, and here’s where your nightmare starts …

Inevitably, you will be told that the SAP of Dynamics ERP is not able to provide the data as webservices or that the existing onces are not performing for realtime use.

Of course, these ERP’s have the capabilities to provide webservices, however with this option, there are unfortunately none. Simply put, a normal SME ERP or accountancy software application has a large amount of data entities provided as webservices which in most cases are also well documented. Examples of data entities are "Customers, Products, Stock, Prices, Orders", which are also needed data for B2B eCommerce like "Customer specific prices, invoices’" etc.  Therefore, by concluding that they are “empty”, what is meant here is that the webservices of these giant’s ERP’s are not able to deliver such data as of yet.

Do you really need these ERP consultants to be onboard?

Thus, all the eCommerce desired data needs to be created as webservices by these ERP Consultants, so the digital environment is able to get the data from the ERP, and to send the data back to the ERP, to obtain a seamless omnichannel experience. Dynamics 365 FO is slightly different, however, also lacks the data needed to automate your eCommerce platform for B2B eCommerce, they seem to have data for B2C eCommerce… but webservices are lacking in performance asking for catalog data, which therefore the Microsoft consultants will advise to configure a push file so the webservices are not producing performance issues. A second problem which the Microsoft Consultants are trying to solve is the fact the dynamic custom fields of the catalog are not mapped in the default available webservice.

As mentioned, no data will be available for B2B eCommerce, which additionally means no data is available for B2B customer specific price information, real time order simulation for presenting the right discounts, prices, VAT, and basket surcharges which, furthermore, contributes to not being able to send the orders, deliveries, and invoices of all your customers in a push file which is only able to call the data – resulting in any performance issues.

By going down this route, with no webservices or data available, you will be left with a complex SAP or Dynamics project, a 3–6-month timeframe wasted before the integration project even starts, your customer spending three days for an individual webservice configuration through an ERP consultant and a trial-and-error project that pays no dividends. Of course three days seems not to be so problematic, however, please imagine that for a fully-blown eCommerce project, you will need 20 webservices, so it is essential to realize that 20 webservices multiplied by 3 days contributes to a needed budget for the ERP consultants of  +/- 60 days or in terms of an hourly rate, accumulates to approximately 200, which subsequently results in a budget of 120.000, notwithstanding all the problems ERP Consultants are creating by trying to be ‘digital experts’, which is not the case. We believe that digital processes should be guided and supervised by the right figures.

Connecting the enterprise variants of SAP and Microsoft Dynamics to eCommerce can result in:

1) Let the API Datapoints be created via SAP Consultants

Risk of low quality & performance errors
If your team will create the data points in the API’s for a fully blown SAP B2B portal, for the first time, the risk of forgetting data fields, the wrong type / logic of creating webservices in a way they will not perform is enormous.    

Let's give you 1 example and insight:   In order to create a customer or so-called self-service portal in your B2B eCommerce, where customers can have a look to their current stats of orders and deliveries, or the history of orders, you need to create 2 separate webservice to make sure you are not over requesting the SAP API. You need to create a separate web service which only requests the header information (invoice number,  for only the latest 10 items, etc and 1 separate which request the detailed information of an invoice. rserd customer will look for a list of first and only will have a look to 1 order/ delivery. The API call of the headers is exceptionally light, and the request of detailed information is a bit heavier. By using 2 APIs call for this feature, you are preventing to request all the detailed information for every user, which will visit the self-service portal. This way if building the API’s is 98% lighter than requesting all detailed information for all orders by all users!

The risk of configuring your webservice in a way which will get a big load to your SAP is enormous. When requesting all products, B2B Prices, Orders or Invoices to your SAP using real-time calls via a wrong logic, it may cause serious  performance problems. It is  therefore extremely important to configure the webservice with the right logic, using a smart caching  mechanism, to not request data in real-time by using “call” requests to your  API webservices, however  use a push mechanism to prevent big load and performance issues

2) Use an off the shelf certified and proven SAP API Plugin

A SAP or Dynamics project where no webservice/data will be available

A complex SAP or Dynamics with ERP consultants involved

A customer paying a huge amount for having their webservices configured

A wasted 3 to 6 months before the project even can start

A test an error project that inevitably gets you no further from where you started

So, now that you know you want to “work smarter not harder, you more than likely want to start with a project that is not as complex and expensive, whilst providing you with documented webservices that provide you with all the data. As it goes without saying – “Where there’s a will, there’s a way!"

Happily... You DO NOT need these ERP consultants!

The smooth solution: How to connect SAP and Dynamics to eCommerce!

Alumio has been connecting to SAP and Microsoft for over 20 years and have created unique and native software which can be installed in these ERP’s. The software delivers configuration features so that the data objects of the ERP’s can be configured within a matter of days. Between day one and day three day you will have 21 well-documented webservices and push data points which can in essence, be connected to the eCommerce platform.

But how do we connect to eCommerce?

You now are able to connect the data with your development team, using custom code to eCommerce. A faster and more future-proof way is to use Alumio’s integration platform. The integrations routes are already available as integration templates, so your integration project is kickstarted. You can now change the routes according to the needs of your customer, let junior developers do the integrations and you will have automatic logging and monitoring features!

The costs of the API Plugins

Most importantly, API Plugins are cost effective solutions for kickstarting your integration project with all the needed and desired webservices. For the fully blown version that entails 21 webservices, you will pay a bit more than using the 8 data routes needed for B2C eCommerce.

Additionally, there is also a variant option designated for E-Invoicing, EDI, and Message broker. In essence the installation and configuration of the SAP API Plugin will cost a limited amount of money as a fixed price integration project, bringing the total cost of ownership of a 3-year project to a fraction of the custom-built version by ERP Consultants. Perhaps more importantly, you will have a working version within a three-day time frame.

Don’t reinvent the wheel, flip it on its axis and watch it spin with this Alumio – eCommerce combination and see your eCommerce dreams come to life!

Selection Guide

How to connect eCommerce to SAP and Dynamics

How your eCommerce can be connected to enterprise ERP's like SAP ECC, S/4HANA and Dynamics 365 Finance and Supply?
How to connect eCommerce to SAP and Dynamics

SAP S/4HANA and Microsoft Dynamics 365 Finance and Operations are one of the most renown enterprise ERP systems on the market. As our environment continues to strive for complete digitization and a 360° customer satisfaction, merchants are looking towards creating an omnichannel experience and digitalization through integrations between these ERPs and the eCommerce platform.  

More often than enough, when starting an integration project with these giant ERP’s, you end up with these consultants entering your project, and here’s where your nightmare starts …

Inevitably, you will be told that the SAP of Dynamics ERP is not able to provide the data as webservices or that the existing onces are not performing for realtime use.

Of course, these ERP’s have the capabilities to provide webservices, however with this option, there are unfortunately none. Simply put, a normal SME ERP or accountancy software application has a large amount of data entities provided as webservices which in most cases are also well documented. Examples of data entities are "Customers, Products, Stock, Prices, Orders", which are also needed data for B2B eCommerce like "Customer specific prices, invoices’" etc.  Therefore, by concluding that they are “empty”, what is meant here is that the webservices of these giant’s ERP’s are not able to deliver such data as of yet.

Do you really need these ERP consultants to be onboard?

Thus, all the eCommerce desired data needs to be created as webservices by these ERP Consultants, so the digital environment is able to get the data from the ERP, and to send the data back to the ERP, to obtain a seamless omnichannel experience. Dynamics 365 FO is slightly different, however, also lacks the data needed to automate your eCommerce platform for B2B eCommerce, they seem to have data for B2C eCommerce… but webservices are lacking in performance asking for catalog data, which therefore the Microsoft consultants will advise to configure a push file so the webservices are not producing performance issues. A second problem which the Microsoft Consultants are trying to solve is the fact the dynamic custom fields of the catalog are not mapped in the default available webservice.

As mentioned, no data will be available for B2B eCommerce, which additionally means no data is available for B2B customer specific price information, real time order simulation for presenting the right discounts, prices, VAT, and basket surcharges which, furthermore, contributes to not being able to send the orders, deliveries, and invoices of all your customers in a push file which is only able to call the data – resulting in any performance issues.

By going down this route, with no webservices or data available, you will be left with a complex SAP or Dynamics project, a 3–6-month timeframe wasted before the integration project even starts, your customer spending three days for an individual webservice configuration through an ERP consultant and a trial-and-error project that pays no dividends. Of course three days seems not to be so problematic, however, please imagine that for a fully-blown eCommerce project, you will need 20 webservices, so it is essential to realize that 20 webservices multiplied by 3 days contributes to a needed budget for the ERP consultants of  +/- 60 days or in terms of an hourly rate, accumulates to approximately 200, which subsequently results in a budget of 120.000, notwithstanding all the problems ERP Consultants are creating by trying to be ‘digital experts’, which is not the case. We believe that digital processes should be guided and supervised by the right figures.

Connecting the enterprise variants of SAP and Microsoft Dynamics to eCommerce can result in:

Connect your eCommerce platform to your ERP

Ready to dive in?

Get your demo today.

Let's build an IT-landscape for tomorrow, together!