SAP Business One users now get more flexibility with the new Service Layer architecture because it exposes more objects, fields and operations & can also respond quicker to SAP Business One developments. It became simpler to release a new object.
Previously SAP Business One was dependent on Microsoft SQL for data management. But now SAP introduced HANA. Which is its own database & allowed SAP to offer customers a REST-based API called Service Layer. It enables them to connect applications and software directly to SAP Business One’s data and services.
Advantages of SAP Service Layer:
It is very easy to run the Service Layer in both cloud and on-premises environments whether the server is based upon Windows or Linux. The SAP Business One (SL) Integration tool is useful for those organizations who want to communicate with SAP Business One through REST APIs. Previously, the SAP Business One Integration tool communicated with SAP Business One either using the Data Interface (DI) API or using the DI server object.
The execution of operations such as data Retrieve, Data Add & Data Update processes in any module can easily be performed with Get, Post & Patch service.
Also, if any SAP Business One user wants to create any user-defined table they can easily create & access it through service layer API. Only they have to put a prefix before the table name as “U_”. They don’t need to create any separate object base for the UDT’s. The same process goes for the user-defined fields as well.
The entire documentation support is also available in the service layer URL as well.
Disadvantages of SAP Service Layer:
As the entire process is dependent on REST API so Internet connectivity is the biggest point. In any segment, data loss can happen if Internet Bandwidth gets down.
For each process in the service layer as the API calling is dependent, hence the default proxy time out cannot be sufficient all the time. Always session timeout setting for SLD needs to be increased and restart the SLD service is necessary during configuration.
That needs to be 500 minimum if the user wants to communicate with SAP Business One using GET, PATCH, POST mechanisms.
In SAP DI server architecture using SQL, multiple tables can be joined, and user can write their own query to pull data from SAP Business One as per their requirement. By using the single database call the user can get multiple data from multiple modules in a runtime.
But in SAP Service Layer as there are separate APIs that exist for each and every module so the user can not join them in a single API pull request. The user needs to do multiple API calls to get multi-data from multi-source.
If the user wants to get data using custom queries, then the query needs to be written first & store in the Queries segment. Then via API call, it can be executed.
In a single API call, SAP SL provides by default 20 data packets. Though it can be modified, the processing time gets increases once the packet size gets modified.
Now, you can easily connect all your business applications under one single platform to automate the business process!