Integration Pattern with Usecase to push Data from On-premise ERP system to multiple consumers

[umang6287]

This refers to the continuation of Rahul Kothari's blog post, where he discussed important ideas and a method for linking a SAAS application with an Advanced Event Mesh (AEM) to facilitate streaming events and data.

Introduction

Regarding the process of publishing data from On-premises ERP Systems, there are several methods to accomplish this integration. It can be achieved through point-to-point integration, either with or without middleware. However, it is crucial to carefully choose the appropriate integration pattern, considering the available options and the desired objectives. Failure to select the correct design could result in accumulating technical debts.

In this account, here I am sharing an integration pattern for designing the Demand to Deliver processes in SAP ECC, leveraging SAP BTP for a smooth transition to SAP S/4HANA while preserving the clean core system.

In many SAP S/4HANA implementation projects, the Demand to Deliver workstream is frequently encountered. However, the implementation of this workstream presents significant challenges due to the necessity of integrating multiple systems. Keeping a clean core system while simultaneously focusing on development is crucial. Moreover, complications arise when non-SAP systems, such as third-party shipping providers or internally developed logistics modules, are utilized, as they limit the use of standard integration packages.

If SAP ECC has been used extensively, relying on SAP ABAP for development without employing middleware like SAP PI/PO, the challenge becomes even more complex. For instance, integration may have been achieved through API management by developing custom OData services at the core and exposing them as APIs at the API marketplace, and letting consumers consume the data periodically.

Given the tight deadline for migrating to S/4HANA, a simple "lift and shift" approach would lead to numerous custom developments overwhelming the core system. To avoid this and maintain a clean core, a possible solution is to redesign the entire process using SAP BTP (Business Technology Platform) as a forward path.

What am I talking about?

Existing High-Level Architecture

Challenges with this integration pattern:

• Polling the ECC system for real-time data results in increased network traffic, resource consumption, and system load. This inefficiency and scalability limitations lead to slower response times, performance issues, and constraints on scalability.


• The use of standard integration packages is limited when non-SAP systems such as third-party shipping providers or internally developed logistics modules are involved.


• A 'lift and shift' approach for migrating to S/4HANA within the tight deadline is not feasible to maintain a clean core.

Solution

Choosing an event-driven approach is crucial due to its advantages in scalability, flexibility, fault tolerance, and responsiveness. It meets the specific need for real-time data updates across systems, enabling selective data searches using standard SAP APIs instead of periodic polling and extensive searches from the core.

Proposed High-level Architecture 

Solution Highlights

• Chose SAP BTP (Business Technology Platform) as the path forward for redesigning the entire process.


• Use new extensibility options to extend standard OData services to hold custom data in S/4HANA and publish them as APIs


• Use of Integration Suite, Advanced Event Mesh in conjunction with event enablement add-on for event streaming


• Enable consumers to perform selective data searches and make ad-hoc requests by providing access to the APIs through the API business hub.

Solution Landscape

Embracing Event-Driven Approach

Adopting an event-driven approach offers a multitude of advantages, including enhanced scalability, unparalleled flexibility, robust fault tolerance, and exceptional responsiveness, among other compelling benefits. In such cases, a pivotal requirement often revolves around the imperative ability to achieve real-time data synchronization across systems, effectively communicating incremental changes within S/4HANA while upholding the pristine nature of the core system. This empowers consuming systems to engage in selective data exploration, leveraging standardized SAP APIs rather than relying on periodic timestamp-based polling or exhaustive searches. Hence, the strategic selection of an event-driven approach becomes paramount to meeting and exceeding these dynamic demands.

References

Event-Driven Architecture with Event Mesh: https://blogs.sap.com/2022/12/04/event-driven-architecture-with-event-mesh-part-1/

Introduction to SAP Integration Suite, advanced event mesh: https://blogs.sap.com/2022/10/03/sap-integration-suite-advanced-event-mesh-vis-a-vis-sap-event-mesh-...

This topic was presented at the SAP Inside Track event in Kolkata on 17th June 2023. This event was organized by moumitasaha.thedatatherapist(LN), Pradipto Kumar Saha, Sandeep Mukherjee, & SUBHASREE GHOSH with the support of many volunteers.

For more details of the event refer: https://blogs.sap.com/2023/06/30/3.-sap-btp-at-sap-inside-track-kolkata-2023/

 

What’s Next?

Please anticipate my upcoming blog, where you will discover further technical specifics concerning the connectivity, connectors, and Add-Ons linked to the integration pattern discussed in the blog.

[BarisBuyuktanir]

Hi Umang,

Thank you for the nice blog and provided high level / solution architecture.

A quick question:
You have mentioned Event Mesh in high level architecture and Advanced Event Mesh in the Solution Landscape. Are those for two different approaches? Which direction do the events go for the solution landscape? (S/4HANA is the consumer or publisher?) The reason I'm asking is AFAIK, only EventMesh is supported with the add-on unless you use a third party package (the solution architecture shows CI before AEM which means event enablement package consumes and publishes events from/to CI. Is that the case?

Thank you,
Baris

[umang6287]

Hi Baris,

Thank you for the question!

Regarding the PubSub model, both products appear similar for the shared use case. However, AEM overcomes the event mesh solution limitations outlined in the second blog's comparison chart. In my description of the futuristic landscape, I included AEM to highlight its relevance in event streaming from SAP SAAS products and On-premise ERP. Third-party add-ons support event streaming from ECC and S/4HANA to AEM, including inbound scenarios. SAP might release an add-on for AEM in the future. The cloud integration shown in the landscape is not necessary; the third-party add-on supports direct connectivity. Stay tuned for more details in my upcoming blog post.

[BarisBuyuktanir]

Hi Umang,

Because of the same reasons (AEM's multiple benefits over EM), we favor AEM and using it.

My point was, although they(EM and AEM) are totally different products, blogs are mentioning EM only(which is the only option) when it comes to connectivity to S/4HANA(not explicitly publishing events) from S/4HANA(or consuming).

I was chasing the connectivity to AEM directly since Q1 and it is promised to be available in Q32023 in the roadmap for the time being. (not talking about third party addon, which is already available in ECC & S/4HANA). Before that we are evaluating multiple options which doesn't feel very effective to me though and checking each time if there's something that is published.

Currently this "grey" area still remains when it comes to S/4HANA publishing to AEM directly, but I hope SAP will make AEM to S/4HANA available like in EM to S/4HANA as soon as possible, let's wait and see..

 

Baris