Blockchain is usually perceived to be the transfer system for cryptocurrencies. However, at its core, it’s a data transfer system. Hence, its exploitation as a data transfer system for any type of data is endless. SAP’s integration with Blockchain can help a lot of enterprises link their disparate departments and overcome inefficiency.

The major focus on Blockchain has always been its accessibility, transparency, and speed. As a data transfer system, it is unparalleled in its security and transparency. However, it also has no boundaries, in that it can send information across borders without any problems. While that may not be a problem with much of data today, it is an issue when it comes to finances.

Blockchain can transfer crypto-currency since it’s just bits and bytes of data, same as any other file. It’s not bound by tariffs or taxes or trade regulations. While the legality of that can be debated, the importance and ease of it cannot. Hence, its integration with businesses, particularly those that deal in Finance is invaluable.

Hence, here are the initial tests and outcomes that SAP has carried out as far as Blockchain is concerned.

Closed-Loop Control Architecture

SAP implemented its initial Blockchain use case implemented via the Hyperledger Fabric Architecture. Through this, they also tested the data privacy implementation for various enterprise scenarios. This led to the extension of Blockchain to the entire SAP S/4HANA core.

This use case’s objective was the implementation of transparency and trust regarding products that Blockchain affords. From manufacturing to the assembly of these products, every aspect had to be brought under tight controls.

This involved the creation of custom APIs and smart contracts which could be leveraged by different parties. All of them would be part of the same network, namely the Blockchain.

Software and Components

SAP Cloud

This is the basis of Blockchain in SAP. This would be the platform upon with SAP Blockchain is built and accessed through. This provides an easy to visualize node and channel dashboards. Other services that follow will be instantiated as parts of the EU/10 Canary Landscape with which SAP S/4HANA integrates seamlessly.

SAP Blockchain Hyperledger Fabric Service

These nodes, channels and private collections implemented were all part of the SAP Blockchain services of the EU10 Canary Landscape. These included Hyperledger Fabric Nodes as well. The procedures for entitlement and allocation are all similar to those in any other service from the SAP Cloud Platform.

Custom chain codes were written to handle data privacy. These were all written using private collections and optimized for search operations.

S/4 HANA System

SAP’s research allowed them to realize which system would work for major scenarios. This would be SAP S/4HANA 1905 SP00 and above. This research included multiple attempts of procurement and configuration of SAP S/4HANA backends, eventing configurations, and cloud connectors. This solution would integrate seamlessly with the SAP Cloud Platform’s Canary Dev Landscape for any major scenarios.

The problem with earlier systems turned out to be Product Object Eventing. Integration with ‘Task Object Type: Product’ proved to be extremely difficult as SAP faced blocking at several ends. This problem was fully solved from the 1905 SP00 system onwards.

All other Object Types include BusinessPartner, PurchaseOrder, SalesOrder, etc worked fine. Hence, implementation of Blockchain Integration with SAP is best initiated on builds 1905 or higher.

Enterprise Messaging Service

This Sub/Pub messaging service that is available on the SAP cloud platform is very straightforward. Any integration with Blockchain requires these three basic steps:

1. Make sure that Enterprise Eventing is activated for the Object in question. This has to be activated in the Business Event Subscription Application.
2. Configure the Communication System. The Communication and Arrangement User needs to configure connectivity with EMS on Canary (Dev). This will, in turn, activate the Communication Channel.
3. Manage the solution App to configure Eventing Channel subscription. This needs to be done for every single event and channel that you’re interested in (PO.changed.Product.Created, etc)

Node JS Client App

This simple application subscribed and bound to the EMS consumed messages selected from an SAP S/4HANA queue. The original intent was to try an SAP CP service. However, it was riddled with issues since the application hadn’t got past the beta stage. The NodeJS Client obliged, however.

Message consumption proved more challenging, however. The team needed to revert to details about Master Product Data. Hence, the team integrated the OData APIs in the SAP Hub.

Any teams willing to integrate similarly need to configure the corresponding API Integration Communication Scenario just like the Eventing scenario. Hence, the OData may be called successfully.

Critical info was required for any transactions that had to take place. For this, earlier mentioned BC chaincode APIs were called upon.

This completed the entire process of the end-to-end working scenario for Blockchain integration.

This would entail a product being created or updated in the product master. The decentralized ledger would hold a transaction that would reflect creation or updates. Thus, the Blockchain would maintain a transparent ledger and trace the action to its source. This would only be visible, however, to verified members of the network.

This process, though rough in patches, can be improved manifold to reflect the future needs of enterprises.