Selection Guide

Everything you need to know about custom code integrations

Learn all about using custom code for integrations

Everything you need to know about custom code integrations

Selecting the proper software solution for data integration can be tricky, with so many different choices available. Besides, these options provide you with websites, catalogs, and pamphlets, only leaving you with half the story told. For that very reason, we've worked to compile several well-known and lesser-known data integration platforms into a single and easy to read document to aid in your decision making. In this blog, we'll discuss the pros and cons of custom code integration.

More than likely, the first integrated software solutions you created were probably bespoke or custom coded, end to end, integrations. If you’ve already got your own ERP application and want to support integration from other data entities with another application, then you’ve likely asked your software partner to add some custom code to support communication between your APIs.

The pros

This type of approach works best when you have no more than 2 applications to integrate. If you feel comfortable enough in the stability of your integration team, then this should work for you. However, we always recommend that you agree on the code and have robust discussions regarding how the integration will function.

The cons

  • Writing custom code can cost money and take up a substantial amount of time.
  • Custom code needs the professional who built the integration to provide support and maintenance.
  • Adding new functionality can be difcult because there isn’t much knowledge of the current code available.
  • For mission-critical integration, your team would be forced to create custom monitoring protocols, which can be expensive.
  • When the APIs are updating themselves, you could experience communication issues.
  • Changing the software in your IT landscape requires a big project and a big process.
  • You’ll need extra custom coding at some point to integrate new technologies like marketing automation software, AI, and machine learning tooling.

Using custom code for integrations is just one of the many ways to integrate your applications. Learn more by downloading our free white paper 'How to choose an integration solution.'

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

Selection Guide

Everything you need to know about custom code integrations

Learn all about using custom code for integrations
Everything you need to know about custom code integrations

Selecting the proper software solution for data integration can be tricky, with so many different choices available. Besides, these options provide you with websites, catalogs, and pamphlets, only leaving you with half the story told. For that very reason, we've worked to compile several well-known and lesser-known data integration platforms into a single and easy to read document to aid in your decision making. In this blog, we'll discuss the pros and cons of custom code integration.

More than likely, the first integrated software solutions you created were probably bespoke or custom coded, end to end, integrations. If you’ve already got your own ERP application and want to support integration from other data entities with another application, then you’ve likely asked your software partner to add some custom code to support communication between your APIs.

The pros

This type of approach works best when you have no more than 2 applications to integrate. If you feel comfortable enough in the stability of your integration team, then this should work for you. However, we always recommend that you agree on the code and have robust discussions regarding how the integration will function.

The cons

  • Writing custom code can cost money and take up a substantial amount of time.
  • Custom code needs the professional who built the integration to provide support and maintenance.
  • Adding new functionality can be difcult because there isn’t much knowledge of the current code available.
  • For mission-critical integration, your team would be forced to create custom monitoring protocols, which can be expensive.
  • When the APIs are updating themselves, you could experience communication issues.
  • Changing the software in your IT landscape requires a big project and a big process.
  • You’ll need extra custom coding at some point to integrate new technologies like marketing automation software, AI, and machine learning tooling.

Using custom code for integrations is just one of the many ways to integrate your applications. Learn more by downloading our free white paper 'How to choose an integration solution.'

Connect your eCommerce platform to your ERP

Ready to dive in?

Get your demo today.

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