Addendum No 2
Confidential
© 2023 SAP SE SAP Readiness Check for SAP S/4HANA Page 97 of 117
collector evaluates and aggregates the data during a specific time frame and compiles a list of
active flat file interfaces.
The data collection period defines the precision of the analysis results. Due to different project
requirements and objectives, no general recommendation about the duration of the data collection
period can be provided. Instead, the project team needs to evaluate and agree on the duration. If
required, the analysis data of flat file interfaces can be uploaded to the current SAP Readiness
Check analysis several times.
The data collection process for flat file interfaces runs independently from the rest of the SAP
Readiness Check framework. This decoupled approach enables the time-consuming analysis of flat
file interfaces to continue without impacting the completion of the other SAP Readiness Check data
collectors. The flat file analysis can start before or after performing the rest of the SAP Readiness
Check analyses.
The data collector aggregates and filters the analysis results of the flat file interfaces to focus on
interfaces relevant to SAP Readiness Check and exclude interfaces classified as SAP technical file
interfaces (for example, in the transport system or for interfaces related to ABAP design time
traces). The list of used filter criteria is available in SAP Note 3322944.Use the file interface
discovery tool to explore the complete flat file interface analysis.
The chart and table in the Integration check provide an overview of discovered interfaces and the results of
the impact analysis performed by SAP Readiness Check. The impact analysis focuses on the most critical
impact types that require immediate action during system conversion. It does not cover topics such as using
outdated technology, security risks, performance, and so on
The analysis covers the following impact types:
Functionality Unavailable:
One standard ABAP object directly associated with an interface or referenced by an associated custom
ABAP object is on the simplification list. The identified objects can be categorized as follows:
• Standard objects are checked against the simplification item database and the data dictionary of
the target SAP S/4HANA release. The findings include cases where an object is missing in the
target release, exists but is neither used nor supported, and where a table is partially used in SAP
S/4HANA compared to SAP ERP.
• Custom objects are checked against the ABAP test cockpit scan results. The results become
available once you upload the ABAP test cockpit results (S4HANA_READINESS) to your SAP
Readiness Check analysis.
Serialization Issue:
One of the objects associated with an interface becomes binarily incompatible upon system conversion due
to a field length extension. These interfaces should not be used without adjustments on the caller side to
avoid possible data inconsistencies.
There are three types of cases:
• An SAP S/4HANA version of a standard function module and its SAP ERP version are binarily
incompatible. These function modules are listed in the external blocklist.
• A custom function module becomes binarily incompatible upon system conversion. The ABAP test
cockpit identifies such custom function modules.
• A custom or extension IDoc segment becomes binarily incompatible upon system conversion. The
ABAP test cockpit identifies such IDoc segments.
Interfaces with this impact category will either dump with a syntax error on first use when calling a missing
object or become unstable, as the referenced standard object is neither supported nor maintained in SAP
S/4HANA.
Blocked:
One of the standard programs or function modules associated with an interface is on the internal blocklist
and cannot be used with SAP S/4HANA. Interfaces with this impact category will dump on first use when
accessing a blocked object.
In the Details column displayed in the table within the Integration check, impacted BW extractors are
assigned to one of the following subcategories (if available):