If you are going to convert your SAP Business Suite system to SAP S/4HANA and want to check your custom code, you use one of the ABAP Test Cockpit check variants like S4HANA_READINESS_REMOTE or S4HANA_READINESS_1909 for example (see also the blog SAP S/4HANA System Conversion – Custom code adaptation process).
So far the check for SAP Query was not a part of the SAP S/4HANA readiness ATC check variants. But now you can check your custom SAP Queries for SAP S/4HANA readiness after implementing the corresponding SAP Note 2942419 - Include ATC check 'S/4HANA: Readiness Check for SAP Queries' to the SAP S/4HANA c..., which is available for all SAP_BASIS >=7.52 releases.
After this you will get the new SAP Query check into all your SAP S/4HANA readiness check variants:
Consequently after checking your custom code containing SAP Queries with the updated SAP S/4HANA readiness check variant you will get the ATC findings also for your custom SAP Queries in case they use the SAP standard objects, which were simplified in SAP S/4HANA.
In the following example the SAP Fiori App Custom Code Migration executes an ATC run over the custom code in an ERP system and the SAP Query check reports the ATC findings in the result list:
In the details of the corresponding ATC finding you can track the reason: in the custom Infoset S4H_DEMO_INFOSET the table BSEG is used, which is simplified in SAP S/4HANA according to the SAP Note 2431747:
So far the check for SAP Query was not a part of the SAP S/4HANA readiness ATC check variants. But now you can check your custom SAP Queries for SAP S/4HANA readiness after implementing the corresponding SAP Note 2942419 - Include ATC check 'S/4HANA: Readiness Check for SAP Queries' to the SAP S/4HANA c..., which is available for all SAP_BASIS >=7.52 releases.
After this you will get the new SAP Query check into all your SAP S/4HANA readiness check variants:
Consequently after checking your custom code containing SAP Queries with the updated SAP S/4HANA readiness check variant you will get the ATC findings also for your custom SAP Queries in case they use the SAP standard objects, which were simplified in SAP S/4HANA.
In the following example the SAP Fiori App Custom Code Migration executes an ATC run over the custom code in an ERP system and the SAP Query check reports the ATC findings in the result list:
In the details of the corresponding ATC finding you can track the reason: in the custom Infoset S4H_DEMO_INFOSET the table BSEG is used, which is simplified in SAP S/4HANA according to the SAP Note 2431747:
- SAP Managed Tags:
24 Comments
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
