Analyzing the MCM Architecture

Last but not least let's have a quick look at the architecture of MCM.

We see that the application is split into two parts.

At the top in the center we see the cloud application built on the BTP platform, and at the bottom we see the SAP S/4HANA backend that does all the master data changes. This way, we have the best of both worlds. On one hand, SAP BTP gives us a flexible solution and the connectivity with the SAP event mesh, which is crucial in order to integrate third party systems.

At every major step of our standard process, an event gets sent out and that event can be used for example by one of the backend systems on the right side to react to it, get the data and start their downstream processes. On the backend side on the application process engine side, the event creates a transfer document, which is an intermediate document that gets stored and triggers a process document.

This architecture will change based on the customer landscape, and process like Device Management or Energy Data Management could be handled in SAP S/4HANA for Utilities, SAP Cloud for Energy or third party applications.

The image depicts the architecture of SAP Business Technology Platform (SAP BTP) and its integration with the SAP S/4HANA system. It shows the key components, including applications, services, core logic, and persistence in the SAP BTP, as well as the back-end systems like device management and energy data management. The image also highlights the measurement concept management add-on in the SAP S/4HANA system, which includes a webhook handler and application program interfaces (APIs) for processing documents.

Note

*Device management and EDM process could be managed in SAP S/4HANA Utilities, SAP Cloud for Energy solution, or third-party solutions.

Full integration between measurement concept management and the measurement concept management add-on for SAP S/4HANA Utilities.

The MCM Cloud Application integrates natively with the SAP S/4HANA MCM Add-on using SAP Event Mesh to orchestrate the master data updates.

The SAP S/4HANA MCM Add-on requires configuration to properly update the data in SAP S/4HANA based on the instructions coming from the MCM Cloud Application.

Process Steps:

Applications request new process against cloud application
Cloud app validates initial data and raises events via SAP Event Mesh
SAP S/4HANA and backend systems listen to new events and read / update data in cloud application

The image consists of three main sections: 1. Cloud app for measurement concept management: This section showcases the user interface of a cloud application for managing measurement concepts. 2. Process choreography (SAP Event Mesh): This section depicts the different process statuses and changes, such as Active, Installed, In Creation, and Initial. 3. Measurement concept management add-on for SAP S/4HANA Utilities: This section shows a technical master data and process implementation for the measurement concept management add-on in the SAP S/4HANA Utilities system. The overall image illustrates the integration and functionalities of the cloud application, process choreography, and measurement concept management add-on within the SAP ecosystem.