Extended Integration Analysis in SAP Readiness Check Is Now Live
Today we are extremely happy to announce the go-live of the extended integration analysis solution available as part of SAP Readiness Check for SAP S/4HANA and SAP Readiness Check for SAP S/4HANA upgrades.
The existing integration analysis check was completely redesigned and enhanced to provide you with more insight into the existing interfaces and thus better support you as you scope and plan your project. This new version of the integration analysis supports additional interface types and offers in-depth details on both impacted and non-impacted interfaces. To enable the use of this new version of the integration analysis, simply update and execute the interface data collectors that are installed within the system you plan to analyze.
In short, the new integration check now offers the following benefits:
- Provides a list of discovered interfaces
- Automates otherwise tedious analysis and cross-checks with different data sources
- Identifies interfaces that may no longer work (or function as expected) following the conversion to SAP S/4HANA or upgrade between SAP S/4HANA product versions
It supports these interface types:
- SAP Business Warehouse extractors
- IDoc interfaces
- Web service interfaces
- RFC/BAPI interfaces
Additionally, analysis of the following is on the development roadmap:
- OData services
- SLT replication
- Flat file interfaces
The result of the analysis reveals interfaces that have the following characteristics:
- Belong to (or depend on) functionality that is either unavailable or used differently in the target SAP S/4HANA release (Functionality Unavailable)
- Consume ABAP artifacts that are blocked in the target SAP S/4HANA release (Blocked)
- Contain structures (such as RFC signatures or IDoc segments) that become binary incompatible upon conversion or upgrade (Serialization Issue)
Note: The analysis to identify binary incompatibility requires the upload of ABAP test cockpit analysis results, extended with a new check. If you have yet to configure a central ABAP test cockpit system, it is recommended to focus on the findings related to Functionality Unavailable and Blocked impact types. The reasoning for this recommendation is that the first two impact types are expected to take longer to remediate, as they could require functional analysis and interface redesign. In contrast, the binary incompatibility findings can typically be addressed with lower effort.
Impacted interfaces that appear to be unused are grouped separately. Among these you will find pre-shipped ABAP proxies from the IS-H industry solution that were deprecated with SAP S/4HANA – although it might well be that you never used these. There could be also custom RFC-enabled function modules that become binary incompatible upon conversion – these should be either adapted or changed to non-RFC-enabled. This group might, however, also contain rarely but still used interfaces – treat these as used interfaces.
Experience has shown that middleware solutions often help make an interface adaptation easier or even unnecessary. The number of mediated interfaces is present on the Integration tile and indicated by the middleware type column in the detailed interface list.
In summary, this additional insight should provide an overview of impact on existing integration, well before the start of your SAP S/4HANA system conversion or SAP S/4HANA upgrade project.
To offer further insight into this enhanced solution, we have compiled a blog series covering the following topics:
- Extended Integration Analysis in SAP Readiness Check – Prerequisites and Data Collection – What you need to install and why; what data is collected and transmitted to perform the analysis; and what option you have if you prefer to limit the data submitted for analysis.
- Extended Integration Analysis in SAP Readiness Check – Impact Analysis in Detail – How the new Integration check analyzes your system; which data sources are considered; how impact types are defined, and what they mean from a practical perspective.
- Extended Integration Analysis in SAP Readiness Check – Findings, Next Steps, and Examples – How to interpret and address the findings; we will walk through the next steps proposed by SAP Readiness Check using real examples.
As always, we look forward to receiving your feedback!
SAP Readiness Check Team
Very nice blog and really good tool for identify and analyse SAP S/4HANA interfaces impacts.
Regarding "middleware type" column, I found a customer that his system is not using a middleware, but some interfaces are tagged with a PI/PO middleware:
If it is possible, I would like to understand how the middleware tag is set in a interface
Thanks a lot.
Thank you for your question and interest in the Integration Analysis!
We are currently working on including this information about the Middleware identification into this Blog. We will update you once this is the case.
We really like the latest enhancements on the integration part, this really helps to get an quick insight about the impact in this area.
Is there any information available on when the ODATA and FLAT-Files will become available and what the check is actually checking?
Hi Johannes Dellert and Astrid Tschense , I see the OData and SLT integration check is included in the Readiness Check report, but not Flat File yet. Is this correct? Could you give an update when this is expected?
we did several Readiness Checks with the Integration Analysis Option. For most of the interface types the result is clear, but we have issues with webservices and OData services. The frequency of use shows always "Unknown".
Do we miss something, but we are sure we implemented all relevant OSS notes in the ECC systems.
thank you for reaching out. For OData services, there is no usage information associated (see description in the learn more section of the SAP Readiness Check Integration analysis).
For WebServices there should be, the information is taken from the PI/PO monitoring logs of the analysed system. You may check the logs directly if they contain the corresponding data (in case of a dev system or if there was a cleanup they could be empty).
If you find data in the logs which are not considered for the analysis, please open a ticket for SAP Readiness Check, then we will analyse the issue.