Installing the ABAP Looply Add-On
In order to integrate Looply with SAP, you must first install the delivered ABAP Looply Add-On in your ECC or S/4HANA system.
Last updated
In order to integrate Looply with SAP, you must first install the delivered ABAP Looply Add-On in your ECC or S/4HANA system.
Last updated
The Add-On can be installed using the standard SAP Add-On Installation Tool (SAINT). For detailed information on the SAINT tool, please see the section of the SAP help portal. A quick overview of the required steps is also provided bellow:
Logon to client 000 of your SAP system as a user that has SAP_ALL authorization. Do not use the SAP* or DDIC user.
Go to transaction SAINT.
Select Installation Package->Load Packages->From Front End and browse to the delivered .SAR file.
Go to transaction SGEN.
Select “Generate All Objects of Selected Software Components” and click Continue.
Select the “STELO” software component and click Continue.
Select for Parallel Generation: Leave default. Click Continue.
Start Job Directly.
Generation speed depends on your system but should take under 10 minutes.
Please note that all the above steps must first be performed in your development system and then repeated throughout your landscape.
After installing the Add-On, the following tasks must be performed:
In transaction sm59, create an RFC connection to Looply. This will be used by the SAP system to trigger (or Resume) Looply workflows. Create a connection with the following details: (This step should be performed in every system in your landscape)
Connection Type: G Target Host: api.looply.io Path Prefix: /v2/workflows
In the Logon & Security tab, set SSL to active and select the correct SSL Certificate:
At this point you may need to whitelist the Looply host so that i is not blocked by your firewall. When attempting a Connection Test you should get a 403 Forbidden response. You can ignore the 403 error
In the Looply web app, create an API key by going to the API keys tab and clicking on the Create API Key button.
On your SAP system, go to the following transaction in SPRO and maintain an entry for each of the systems in your landscape:
General Application Functions -> Looply -> System Settings
SAP System ID: The ID of your SAP system
RFC Destination: The name of the sm59 connection created in the previous step
API Key: The API key created in the previous step (you can use the same API key for each system in your landscape)
Gateway System ID: The ID of the corresponding Gateway System (if you are running Gateway on the same system Looply is installed in, you can leave this field blank)
Gateway System Client: The client of the corresponding Gateway System (if you are running Gateway on the same system Looply is installed in, you can leave this field blank)
These entries should then be transported throughout your landscape.
In transaction snro, maintain intervals for number range /LOOPLY/EI as follows: Number Range No. 01 From No. 0000000001 To Number 9999999999
This step must be repeated in every system of your landscape.
In this step we will configure the SAP Gateway service used by Looply to post data to SAP. The step depends on your setup. If you are running Gateway on the same system Looply is installed in, follow the steps in the page. If you are running Gateway on a Fiori Hub system, follow the steps in the page.
If you wish to integrate Looply with SAP workflow, also follow the steps in .
