More information about how the transition is supported by the respective application can be found in the business impact notes or will be added to the business impact notes in the future. This support could consist of, e. g. guides describing the transition to the alternative solution, functional, technical, and data model mapping between the Compatibility Pack and alternative solution, and dedicated reports and tools for automating individual steps of the transition.
3. What happens to artifacts (e.g. tables, transactions etc.) in Compatibility Scope after 2025?
SAP plans to make compatibility scope functionalities technically unavailable after expiry of the respective compatibility pack license, beginning with the initial shipment of SAP S/4HANA 2025.All support and maintenance (e.g., patches, legal changes) for Compatibility Scope will end with the expiration of the usage rights.
4. What happens to interfaces e.g.IDOCs, BAPIs?
Interfaces to external systems e.g., IDOCs used for a functionality which is in Compatibility Scope will no longer be supported by the application after the expiration of the usage rights.
Please check the BAPIs you are usingwith the following monitoring tool:Unified Connectivity Tools (UCON)
Please check the IDOCs following the instructions in this blog chapter 2:Link
5. How can customers check if Compatibility Scope is in use in their system?
Customers may run the relevance check via the report /SDF/RC_START_CHECK (for further details see blog:LinkThe report checks the main transactions, tables, and business functions, etc. to detect if there is a trace that Compatibility Scope is in use.
Thereafter the customers need to verify if they are still productively using the Compatibility Scope discovered by the relevance check or if they have already switched to the alternative solution inSAPS/4HANA.
This report can be run by customers at any time.
6. What happens when Compatibility Scope objects (e.g., tables, functions) are used in custom code?
SAP is no longer responsible in any way for correctness of these development objects, after the expiration of usage rights and if custom code refers to Compatibility Scope functionality, including their semantical and syntactical correctness. The customers must adjust their programs accordingly before expiration of usage rights.
7. How can customers check if their custom code uses Compatibility Scope artifacts?
Custom code can be checked using the ABAP Test co*ckpit (ATC) in combination with piece lists, if already available, containing artifacts which are in compatibility scope.
8. Can documents and transactional data in Compatibility Scope still be displayed and can open business processes be finished?
Started objects and open business processes using Compatibility Scope need to be finished by the expiration of the usage rights at the latest.
The data itself belongs to the customer. For compliance reasons, it is planned that customers will be able to only read data from Compatibility Scope applications after the expiration of usage. This will be possible as long as architectural and data model changes are notinvalidating this.
Nevertheless, the display transactions which belong to Compatibility Scope must not be used after the expiration of usage rights.
Please check the corresponding business impact note belonging to the Compatibility Scope item regarding recommendations to display the data.
9. Can customers still apply Data Privacy and Protection (DPP) related blocking and destruction activities on Compatibility Scope data?
All archiving and destruction objects from Compatibility Scope applications will be serviced in future in accordance with the applicable retention periods.
10. Can Compatibility Scope artifacts cause security issues after 2025?
SAP generally takes care of security issues in its products. If security issues in Compatibility Scope arise after the termination of usage rights, SAP may block or delete the affected code or use other means to rectify issues.
The security maintenance of functionality outside of the Compatibility Scope is key to continuously protect also against all types of attacks or newly identified potential weaknesses:SAP Security Patch Day.
11. Can customers still run reporting on transactional data based on Compatibility Scope?
Customers can still use historic data in previous structures which belong to Compatibility Scope for reporting purposes . Nevertheless they need to use reports which are not in Compatibility Scope. The data resides for reporting, machine learning and so forth in Compatibility Scope tables. This will be possible as long architectural and data model changes are not invalidating this.
12. What happens to the report painter and report writer?
Certain reports in the report writer and painter are in Compatibility Scope. In this case, the reports in Compatibility Scope may not be used after 2025. An alternative solution for the reports already exists. For details checkSAP note #2997574.
13. What happens to Logistic Information System (LIS)?
TheLISframework, as such, is not in Compatibility Scope. This means, that theLISframework is planned to be available and supported even beyond 2025. Only particularLISanalytical standard reports inSD,MM-PUR, Vendor Evaluation, andPPhave restricted usage rights as part of the Compatibility Scope which will expire end of 2025. Other applications, e. g. Inventory Controlling, still support theirLISapplications beyond 2025. Currently, SAP is not planning specific developments / improvements in theLIS area.
14. What is the impact of Compatibility Scope usage on system conversions after 2025?
The expiration of the Compatibility Scope license will not affect customers on SAPERP. They can continue to use this functionality beyond 2025 until the end of SAPERPmaintenance.
In addition, system conversions from SAPERPto SAPS/4HANAwhich are done after 2025 are still possible, even if a customer is using Compatibility Scope functionality on SAPERP. All system conversions done after 2025 are required to include the migration to the designated alternative functionalities of Compatibility Scope directly in the conversion project. The option to do the system conversion first and then the migration to Compatibility Scope alternatives at a later point in time, will not be available after 2025 (exceptions apply for selected Compatibility Scope functionality that has been extended to 2030).
Please check as well the blog by Jan Gilg: The Future of Compatibility Packs in SAP S/4HANA
