Setup Steps in the ABAP System


  • Technical Prerequisites for the ABAP system
    • SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04)
    • Install ST-PI 7.40 SP14 or higher
    • Implement the latest version of the collective correction note:
    • Check that profile parameter icm/HTTPS/client_sni_enabled is set to TRUE (see also note 510007 - Additional considerations for setting up SSL on Application Server ABAP)

  • Required Authorizations
    • To run  transaction /SDF/ALM_SETUP you need the PFCG role SAP_SDF_ALM_SETUP
    • The user you specify as Background User, requires the PFCG role SAP_SDF_ALM_COLLECTORS_JOBS

  • You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
    • Endpoints: e.g.
    • OAuth URL: Service Key parameter "url" + /oauth/token, e.g.
    • Client ID: Service key parameter "clientid"
    • Client secret: Service key parameter "clientsecret"

Configuration of the PUSH Data Provider

  1. Log on to ABAP system
  2. Start transaction /n/SDF/ALM_SETUP
If you start the transaction the first time it will look like this:


In transaction /SDF/ALM_SETUP please perform the following steps:

  1. Target ALM Destination
    • To create a new ALM Destination, enter a name (e.g. CALM) and press the 'Enter' key
    • To change an existing ALM destination, select one from the F4 input help and press the 'Enter' key
    • After pressing the 'Enter' key the subsequent fields will be filled.
  2. Maintain HTTP Destination
    • Click 'Update destination'
    • You can copy&paste the content from the JSON file created during the enablement of the SAP Cloud ALM APIs by clicking 'Paste Service Keys'
    • Or you can enter the required fields for connecting Cloud ALM manually:
      1. Token Endpoint: Enter the CALM OAuth URL 
      2. Client ID: Enter Cloud ALM client ID
      3. Client Secret: Enter Cloud ALM client secret
      4. Proxy User (if required)
      5. Proxy Password (if required)
      6. Proxy Host (if required)
      7. Proxy Port (if required)
    • Click 'Ok' to close the pop-up.
    • To delete a destination click on 'Delete destination'
  3. Enter registration target
    • Enter the target ALM root url depending on your region e.g.
    • Enter the background user you created to perform the data collection
    • Click on 'Register' to call Cloud ALM and register the system. If it is successful, a LMS ID is retrieved and is displayed.
    • To unregister a system, click the 'Unregister' button. Caution: This stops all data collection and heartbeat measurements
  4. Select the use cases you want to collect and push data for. The PUSH mechanism supports the following use-cases:
    • Integration Monitoring
    • Exception Management 
    • Performance Monitoring
    • Business Process Monitoring
If everything is done correctly, it should look like this: