Product Information
Extended Integration Analysis in SAP Readiness Check – Prerequisites and Data Collection
Dear All,
This is the second blog in the series. Links to the other blogs in the series are provided at the end.
In this blog we will review the prerequisites, what you need to install and why, what data is collected and transmitted for the analysis, and what option you have if you prefer to limit the data submitted for analysis.
Prerequisites
As interface discovery is not a new topic, we collaborated with our experienced colleagues to adopt and extend existing data collectors to enhance the capabilities of SAP Readiness Check. For instance, this is how the ST-A/PI component was brought into scope.
The data collection process now consists of the following steps:
- ST-A/PI provides three APIs for the discovery of IDoc, Web service, and RFC/BAPI interfaces.
- The SAP Readiness Check data collection report RC_COLLECT_ANALYSIS_DATA invokes these APIs and performs the discovery of SAP Business Warehouse (SAP BW) extractors itself.
- ABAP test cockpit analyzes your custom code and provides impact information on custom RFC-enabled function modules and IDoc custom extensions.
To enable this data collection process, you will need to perform the following:
- Upgrade the ST-A/PI component in your SAP ERP production system to a minimum of 01U* SP02.
- Implement SAP Note 3072059 with the latest code corrections.
- Install SAP Note 3035012 in your SAP ERP development system and central ABAP test cockpit system – this will bring a new ABAP test cockpit check for IDoc segments.
- Implement SAP Note 3057501 in your central ABAP test cockpit system to add the new S/4HANA: IDoc Check to the S4HANA_READINESS check variant.
- Implement SAP Note 2781766 in your central ABAP test cockpit system to extend the content of the extracted XML file.
- Ensure you execute the RC_COLLECT_ANALYSIS_DATA report with a user with the necessary authorizations – see SAP Note 3061414.
You can find all the technical details in SAP Note 3061414 – Enabling extended integration analysis for SAP Readiness Check.
Once these steps are complete, you will need to perform the following:
- Execute the data collection with the report RC_COLLECT_ANALYSIS_DATA
- Schedule the custom code analysis with ABAP test cockpit (optional)
- Upload both generated zip files into the same analysis in SAP Readiness Check
See SAP Note 2913617 – SAP Readiness Check for SAP S/4HANA for details.
Data Collection
The selection screen of the RC_COLLECT_ANALYSIS_DATA report underwent some changes. It offers you a simple option of enabling data collection for the Integration check in the Standard mode and allows certain fine-tuning in the Expert mode.
Standard mode:
Expert mode:
Here is how the data collection works technically:
IDocs
The data collector retrieves active and inactive IDoc interfaces configured in the system. The enumeration is based on the outbound (table EDP13) and inbound (table EDP21) partner profiles. The usage information is pulled from the EDIDC table.
In case the size of the EDIDC table leads to unacceptable runtime and/or you do not consider the usage of IDoc interfaces a valuable parameter, you have an option to skip the collection of IDoc runtime statistics in the Expert mode.
Web Services
All consumer and provider ABAP proxies that are both registered and not registered in SOA Manager are discovered. The usage is based on the Web service message monitoring.
RFCs/BAPIs
The interfaces are collected based on the runtime statistics (transaction ST03N). The same statistics provide the usage information. The list is extended with all Remote-Function-Call-enabled (RFC-enabled) custom function modules, which represent explicitly defined potential RFC interfaces.
BW Extractors
The SAP BW extractors are enumerated based on the ROOSOURCE table. The usage information is extracted from the ROOSPRMSC table.
The Collect minimum data set option available in the Expert mode allows you to reduce the amount of the data collected and uploaded as part of the analysis.
The tables below contain the integration-related data collected by the RC_COLLECT_ANALYSIS_DATA report and indicate fields omitted or anonymized with the Collect minimum data set option.
Anonymization is applied to fields with possibly sensitive information that are used as keys in supplied tables or required for the analysis, such as to calculate the number of distinct partners. To avoid transmitting real field values, the values are replaced consistently with alphanumeric codes within every interface type.
IDocs
| Data Description | Behavior with Collect minimum data set Option |
| IDoc configuration (client, direction, message type, IDoc type, extension type, process code) | Included |
| Package, application component | Included |
| Runtime statistic (oldest, newest IDoc date, number of IDocs) * | Included |
| RFC destination | Anonymized |
| RFC destination type, middleware type, partner SID | Included |
| Partner server (hostname or IP) | Not included |
| Partner port, number | Anonymized |
| Partner type, role | Included |
| Package size, transport and trigger mode | Not included |
| Function module, function group, package, component | Included |
| Function module/group, package titles | Not included |
| Code category (SAP, customer, partner), ALE and BAPI flags | Included |
| IDoc segment fields with extended length | Not included |
| Exception messages | In case of exceptions |
*) Collection of IDoc runtime statistic can be disabled in the Expert mode.
Web Services
| Data Description | Behavior with Collect minimum data set Option |
| Web service configuration (ABAP proxy name, service definition name, direction, external name) | Included |
| Package, application component | Included |
| Runtime statistic (oldest, newest service call, number of calls) | Included |
| Middleware type | Included |
| External namespace, access URL | Not included |
| Logical port, port, protocol | Not included |
| Hostname | Anonymized |
| Implementation class, endpoint type/name | Included |
| ABAP proxy, function module/group, package, component | Included |
| Function module/group, package titles | Not included |
| Code category (SAP, customer, partner), ALE and BAPI flags | Included |
| Exception messages | In case of exceptions |
RFCs/BAPIs
| Data Description | Behavior with Collect minimum data set Option |
| RFC call statistic (client, direction, task type, function module name, calling program name) | Included |
| Call entry point (transaction or report) | Included |
| Not called custom RFC-enabled function module names | Included |
| Package, application component | Included |
| Number of calls | Included |
| Call time, execution time, sent/received data size | Not included |
| RFC destination | Anonymized |
| RFC destination type, middleware type | Included |
| Remote server (hostname or IP) | Anonymized |
| Development package, application component | Included |
| Function module/group, package titles | Not included |
| Code category (SAP, customer, partner), ALE and BAPI flags | Included |
| Exception messages | In case of exceptions |
BW Extractors
| Data Description | Behavior with Collect minimum data set Option |
| BW extractor configuration (OLPT source, extractor type, extractor name) | Included |
| BW extractor description | Not included |
| Runtime statistic (oldest, newest extraction, number of data extractions) | Included |
| Source function module/group or table name | Included |
| Package, application component | Included |
| Exception messages | In case of exceptions |
Previous blog in this blog series:
- Extended Integration Analysis in SAP Readiness Check Is Now Live – Provides a short summary of the extended functionality; areas of improvement, supported interfaces, and an overview of the results.
Next blogs in this blog series:
- 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.
Hi Astrid
Thank you for this blog.
The Integration section is empty in my readiness check report.
I have SAP_BASIS 702 SP 0010 and ST-A/PI 01U_700 SP 0003.
what is missing please ? your help is very appreciated.
Best Regards
Hi Hanane Barka,
please re-check the SAP Note 3061414 – Enabling extended integration analysis for SAP Readiness Check for prerequisites. For example, your SAP_BASIS component should be on SAP_BASIS 7.02 SP15+.
Hope this helps.
Best Regards,
Astrid
Hi Astrid
Many Thanks for your prompt reply.
Best Regards,
Hanane
Hi Astid Tschense,
In our current ECC version basis component is in 7.40 . When I am trying to implement Note 3061414 it's asking to pre-requisite note 3035012,3057501 and 2781766 but those notes will be implemented when SAP_BASIS component is in at list 7.54 but in ECC it's not possible to update SAP_BASIS component up to 7.54. SO, could you please confirmed can we run updated (integration features) S4HANA_READINESS ATC variant in ECC if yes then please confirm the SAP_BASIS component version also confirm in which sap version we can run report RC_COLLECT_ANALYSIS_DATA.
Thanks,
Soumen
Hi Soumen,
This is Tony from SAP Readiness Check support team.
The report RC_COLLECT_ANALYSIS_DATA comes from the SAP Note 2758146. And it can be implemented in SAP_BASIS 740.
For the RC integration sub check, the SAP Note 3072059 is fine. After you implement this note, you can do the interface check.
The custom code analysis, you can execute the SYCM ro ATC.
To enable the analysis for binary incompatible changes in custom function modules and custom IDoc extensions via the ABAP test cockpit, please install the following notes. If you have yet to configure a central ABAP test cockpit system, you may leave this part of the analysis for later and adapt impacted interfaces of this type along with your custom code adaptation activities.
Implement SAP Note 3035012 in your SAP ERP development system and central ABAP test cockpit system before the ATC S4HANA_READINESS check is executed. This will bring a new ABAP test cockpit check for IDoc segments: S/4HANA: IDoc Check (check class CL_CI_TEST_IDOC_CONS). The central ABAP text cockpit system has to be on SAP_BASIS 7.54 or above.
Implement SAP Note 3057501 in your central ABAP test cockpit system to have this new S/4HANA: IDoc Check added to the S4HANA_READINESS check variant.
I would like to suggest you to create a customer incident under the component SV-SCS-S4R if you need further help.
Best,
Tony
Hi Tony,
Could please confirm ,can we run ATC variant S4HANA_READINESS in our ECC NW 7.4, SAP_BASIS 7.4 ? which note need to be apply to get this variant? In our system S4HANA_READINESS_REMOTE variant is available in our system, is this both variant functionality is same to check this integration data.
Thanks,
Soumen
Hi Soumen,
It is not possible to run it in the ECC with SAP BASIS 7.40. The customer needs to setup the remote analysis.
“SAP S/4HANA readiness are only available with the SAP NetWeaver AS for ABAP 7.51 innovation package”
See the following blog, SAP Notes 2436688 and 2364916.
Best,
Tony
Thanks Tony,
For your information.
In case we are migrating ECC to S4HANA system, could you please help me how could we know which SAP Standard object is available or which is not available in SAP S4 HANA target system? We want one source table from where we can identify that which object is available and which object will not be available or is there any specific SAP Notes from, we can identify objects are available or not in target system.
Thanks,
Soumen