Skip to Content
Technical Articles

Aggregate usage data in your production system with SUSG transaction

You can use transaction SUSG to aggregate usage data recorded by ABAP Call Monitor (transaction SCMON or /SDF/SCMON) in your production system.

The ABAP Call Monitor records the execution (usage) of ABAP code (function modules, method calls etc.) in your production system. Find more about how to configure and use the ABAP Call Monitor in the blog ABAP Call Monitor (SCMON) – Analyze usage of your code.

The purpose of the transaction SUSG is to aggregate this usage information collected by ABAP Call Monitor for a period of time.

The aggregated usage data can be used (for example for Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration) to identify when an ABAP program or procedure was last used productively. In this way, the aggregated usage data also helps you to identify the custom code, which is not executed in production so that you can minimize your adaptation efforts while converting your SAP ERP system to SAP S/4HANA.

NOTE: You cannot display the aggregated usage data (neither in SUSG nor in SCMON or /SDF/SCMON). A remote enabled API is provided to read the aggregated usage data which you can use to implement your own display or extractor.

Prerequisites

Transaction SUSG and ABAP Call Monitor (transaction SCMON or /SDF/SCMON) must be available in your system.

See the SAP Note 2643357 for supported SAP_BASIS releases, the installation instructions of SUSG and the SAP Note 2701371 for using the SUSG.

Aggregate usage data

Start the transaction SUSG. If you haven’t collected usage data with the ABAP Call Monitor before and haven’t used SUSG yet, Aggregation and ABAP Call Monitor will not be active and number of Aggregated Days, Aggregated Records will be 0. Aggregation Log (click “Display Log” button) will be also empty:

Otherwise if the ABAP Call Monitor is running and/or you already aggregated usage data before with the SUSG, your entry screen will look like this:

Press “Activate” button. If not already running the ABAP Call Monitor starts. The aggregation of your usage data will be activated with the record limit 199.999.999. The aggregation batch job will be scheduled on a daily basis at 2.30 a.m. system time and aggregates your usage data of the day before.

If you start again the SUSG transaction after some period of time (at least from the next day after 2.30 a.m.) you will see the information about your aggregated usage data so far:

If you click the “Display Log” button, you will get all aggregation logs sorted by date. The log records all user interactions as well as information and error messages during the aggregation. The log also records the information when usage data could not be aggregated (for example during system downtime) or when aggregated data was deleted.

If you deactivate aggregation (button “Deactivate”) the aggregation will stop, the aggregation batch job will not be scheduled, but the ABAP Call Monitor is still active and records your usage data. You can deactivate the ABAP Call Monitor in the transaction SCMON (or /SDF/SCMON).

Create and manage usage data snapshots

You can create snapshots of the aggregated usage data and use them for analysis or archiving purposes. Snapshots can be created for a certain period of time: between the aggregation activation date until yesterday and record already aggregated usage data. The advantages of snapshots are that you can any time access data records that will no longer change during analysis and you can easily transfer aggregated usage data between systems by downloading/uploading snapshots to/from files or automatically using RFC.

Start the transaction SUSG. The data must be already aggregated, meaning that the numbers of Aggregated Days and Aggregated Records on the aggregation state screen shall be > 0. Click Create Snapshot button and enter Descripton:

Click “Manage Snapshots” button to display a list of the snapshots you have created.

Here you can click “Download to File” button to export your snapshot as a file and upload it later on to the target system, or if you are already on your target system, you can click “Upload from File” button to upload the snapshot to your target system.

Clicking “Export via RFC” or ”Import via RFC” buttons transfers your aggregated usage data snapshot automatically between your production and target systems.

You can also delete not needed snapshots by clicking the “Delete Snapshot” button.

Further information

Find more detailed information in the SUSG documentation on the SAP Help Portal.

8 Comments
You must be Logged on to comment or reply to a post.
  • Hi Olga,

    I followed the steps given above and SUSG seems to be ready. However when I try and create a snapshot, I am getting a message:

    Could not create snapshot ‘Usage data of system ECX from 09/16/2019 to 09/17/’: Usage Data locked for write access

    Message no. SUSG_UI121

    Any idea what could be causing this error?

     

    thanks,

    Deepak

    • Hi Deepak,

      it may be that the aggregation started at 2:30 is still running. As long as it’s running the aggregated data is locked and snapshot can’t be generated. With the (brand new) SAP Note 2830186 – SUSG: Runtime of SUSG_COLLECT_FROM_SCMON the duration of the aggregation should be reduced.

      Regards,

      Olga.

  • Hi Olga,

    Thanks a lot for the article – it was very interesting. I am wondering once we have the snapshot of data from SUSG what transaction or tool we use to interpret this data? We are not yet on S/4 HANA so cannot use the Custom Code Migration app. Can we import the data into the ATC (ABAP Test Cockpit) and see there what custom code we are actually running?

     

    Regards,

    Alan Roberts.

    • Hi Alan,

      no, you cannot import an SUSG snapshot into ATC. This is exactly the advantage of the Custom Code Migration App: consideration of the usage data (SUSG snapshots) for scoping of custom code for SAP S/4HANA.

      Regards,

      Olga.

      • Okay, thanks Olga. But the Custom Code Migration app is only available if you have S/4 HANA, no? If we are not on S/4 HANA is there another way of checking the SUSG snapshots?

        Regards,

        Alan.

        • Hi Alan,

          yes, the prerequisite for the Custom Code Migration App is the SAP S/4HANA >=1809 system (or SAP Cloud Platform ABAP Environment, since the App can be run there as well).  There is no other way for evaluation of SUSG snapshots. If you use the SAP GUI based ATC and want to define custom code scope for SAP S/4HANA based on the usage data, you will need to collect the usage data with SCMON (or UPL) and manually define the scope based on these data.

          Regards,

          Olga.

      • Olga Dolinskaja

        Hi Olga,

        does this basically mean that we’d need to set up a new S/4HANA 1909 system where the Custom Code Migration App can then be executed from, utilising SUSG-data captured in the existing NW 7.50 production systems? And should such a new S/4HANA system then also take over the tasks our current central ATC-system provides (i.e. ATC-checks during transport release) which is on NW 7.52?

        Cheers

        Bärbel

         

        • Hi Bärbel,

          yes, if you want to use the Custom Code Migration App, you need to setup an SAP S/4HANA >=1809 system. This system can also take over the tasks of the central ATC system in your landscape. It depends on your situation: whether you e.g. just want to use the SAP S/4HANA sandbox for checking for S/4HANA readiness and then “get rid of” this system or use it further on as the ATC central check system.

          Best Regards,

          Olga.