Tools to identify modified ABAP Objects in S/4HANA Cloud, extended edition
On SAP S/4HANA Cloud, extended edition, customers are not permitted to make modifications to the delivered source code or metadata of the Cloud Service. This includes standard ABAP objects.
How can I find which are the objects modified by the development team in my SAP S/4HANA Cloud, extended edition?
Let’s see the available options starting from a more functional view to a more technical view. We have the following available options for analyzing modifications in S/4HANA Cloud, extended edition:
- Access CCA 2.0 (Custom Code Analytics 2.0) Application via SAP ONE Support Launchpad.
Data is collected via Early Watch Alert without the need of Solution Manager.
The Custom Code Analytics application is available for all customers with Enterprise Support and higher. To use the application, the S-user authorization profile “Display System Data” is required. Contact your company’s user administrator to request it. Access is managed by the Customer.
It is expected in the future to focus more on Business Modifications.
- New ATC (ABAP Test Cockpit) variant
SAP Note: https://launchpad.support.sap.com/#/notes/2928076. This check counts modified objects and not # of modifications.
Supported object types are classes (CLAS), function groups (FUGR), reports and includes (PROG) and logical databases (LDBA).
No results showed for objects of other types, even if they are modified.
This is not yet available on SAP_BASIS Release 754 but it will be made available with the next SAP_BASIS release.
Blog on ABAP Test Cockpit – an Introduction to SAP’s new ABAP Quality Assurance Tool:
- SAP Solution Manager Launchpad
- SAP Solution Manager 7.2 (ST SP10, ST-OST 200 SP05)
- SAP S/4HANA 1909 FP00 as managed system
City Model tile
Displayed values are aggregated values for all the monitored systems.
Customer can also choose just 1 system for their analysis.
- Classical SAP transaction code /SDF/CD_CCA (or CCAPPS) – Custom Code Analysis.
Both transactions call the same ABAP program.
We need for this software component ST-PI (we used for this demo: ST-PI Release 740, SP 12).
We can choose the /0SAP/, namespace.
This transaction can be called from both S/4HANA 1909 and SAP Solution Manager (RFC Destination to S/4HANA system needs to be filled).
- More technical view, classic SAP transaction CODE: SE03. Not recommended as this is not filtering out false-positives results. We are more interested in “Business modifications”.
If the customer doesn’t have SAP Solution Manager installed, recommended options are: transaction /SDF/CD_CCA or tool CCA 2.0.
Each tool displays different results as it counts different types of objects.
There are many tools to check your S/4HANA Cloud, extended edition modifications. Keep the “real” modifications number close to zero!