By Robert Schilling & Bertrand Henkel.
As an Enterprise Architect for SAP RISE customers, we guide organizations through business transformation and cloud adoption. The core integration principle enables hybrid architecture scenarios developed by SAP for customers with large and complex SAP landscapes integrating essential elements and enabling a phased transition to the cloud.
For an initial introduction to clean core principles, we recommend the following learning resource: Managing Clean Core for SAP S/4HANA Cloud. Here, we demonstrate how to evaluate and apply clean core principles to ERP systems to maximize business process agility, reduce adaptation efforts, and accelerate innovation. The course is designed for beginners, takes two hours, and is free of charge.
In general clean core integration focusses on four pillars – please follow up with the official documentation or other blog entries like Future-Proofing Enterprise Agility with SAP Integration Suite and Clean Core Principles
Technically speaking the clean core integration principle focusses on these main components:
- Establishing an API-led strategy and event driven architecture
- SAP Integration Suite on SAP BTP,
- Enabling operational excellence for end-to-end monitoring using
Based on SAP progress, many integration scenarios are already available within this solution architecture: In our daily business as Enterprise Architects we are often asked: “How do I activate these SAP standard scenarios?” and “What should I consider for my custom-built interfaces?”
Therefore, this blog focuses on the reference architecture for the monitoring capabilities for OData Services of SAP Application Interface Framework following the clean core integration principle.
How do I activate SAP AIF Monitoring & Error Handling for SAP standard interfaces for SAP CALM integration?
To do this, the corresponding SAP AIF scenario must be activated. In the SAP documentation (see example: Purchase Requisition – OData V2) for each interface, the available AIF scenario is listed, which can then be activated using the transaction "AIF Content Transport – Deploy /AIF/CONTENT_EXTRACT".
If SAP standard interfaces are not listed as a scenario, SAP asks you to submit a corresponding SAP Customer Influence Request for the relevant interface, like other clean core topics. In general, you can also check the table /AIF/ICD_DATA, which underlies the transaction /AIF/CONTENT_EXTRACT.
In the meantime - How to handle SAP Standard Interfaces, where no SAP AIF Scenario is available?
At present, not all SAP Standard OData Interfaces—such as those from the Maintenance Management area—come with available SAP AIF Scenarios. So, what’s the approach for enabling SAP Cloud ALM Integration and Exception Monitoring in these cases?
These specific SAP Standard Interfaces are handled through SAP Gateway functionalities. You can monitor them directly in SAP S/4HANA using the SAP Gateway Performance Monitor (/IWFND/MONITOR) and review issues in the SAP Gateway Error Logs (/IWFND/ERROR_LOG). Currently, with SAP Cloud ALM, only data from the Error Log can be transferred to SAP Cloud ALM Integration & Exception Monitoring. For more details, please refer to the following section: Enable SAP ABAP Gateway Errors for SAP Cloud ALM.
License requirement for using SAP AIF with custom-developed interfaces:
As described in SAP Note 2293938 – License Check for SAP Application Interface Framework and in the SAP blog "SAP Application Interface Framework – Licensing", a separate SAP AIF license is required to manage custom-developed interfaces via SAP AIF. After purchasing the SAP AIF license, the AIF component AIF_GEN can be installed in the system and used for developing custom interfaces under SAP AIF. The necessary configuration steps for custom interfaces can be found in the relevant SAP help for SAP AIF interface development.
Further information:
Bluesky
