Looply Academy
  • Getting Started
    • What is Looply?
    • Deployment Models
  • System Requirements
  • SAP Integration: ABAP Add-on & Access
  • Security & Identity - What IT Teams Need to Know
  • Authenticating Teams User Actions to Enterprise Systems
  • Signing Up & Onboarding Your Team
  • Looply Implementation Plan
  • Looply Integration Demos
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
      • SSO Authentication
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Maintain SAP Gateway Settings
  • Manage SAP System Alias
  • Activate SAP Gateway
  • Assign Alias to oData Service
  • oData Service Authorization
  • Transport Changes
  • Activate sicf Node
  1. Integrations
  2. SAP Integration
  3. Installing the ABAP Looply Add-On

Gateway Service Setup - Single System

PreviousInstalling the ABAP Looply Add-OnNextGateway Service Setup - Hub scenario

Last updated 4 months ago

Maintain SAP Gateway Settings

Setup GW_HUB destinations for each system in your landscape. Enter GW_HUB as the “Destination system”, the client Looply will run in as the client, the system id as the “System Alias” and leave the RFC destination blank.

  • In NW 7.0-731 go the IMG in transaction SPRO, and open SAP NetWeaver->Gateway Service Enablement->Backend OData Channel->Connection Settings to SAP Netweaver Gateway->SAP Netweaver Gateway Settings

  • In NW 740+ go to the IMG in transaction SPRO and open SAP NetWeaver->SAP Gateway Service Enablement->Backend OData Channel->Connection Settings to SAP Gateway->SAP Gateway Settings

  • Alternatively you could also directly edit table /IWBEP/C_SYSTEM in sm30

Manage SAP System Alias

Manage SAP System Alias and make sure the SAP System Alias is assigned to LOCAL.

  • In NW 7.0-731 go the IMG in transaction SPRO, and open SAP NetWeaver->Gateway->OData Channel->Configuration->Connection Settings->SAP Gateway to SAP System->Manage SAP System Aliases

  • In NW 740+ go to the IMG in transaction SPRO and open SAP Netweaver->SAP Gateway->OData Channel->Configuration->Connection Settings->SAP Gateway to SAP System->Manage SAP System Aliases

  • Alternatively you could also directly edit table /IWFND/V_DFSYAL in sm30.

Activate SAP Gateway

Activate SAP Gateway in every system in the landscape (if it is not already activated).

  • In NW 7.0-731 go the IMG in transaction SPRO ->SAP Netweaver->Gateway->OData Channel->Configuration->Activate or Deactivate SAP Gateway

  • In NW 740+ go to the IMG in transaction SPRO->SAP Netweaver->SAP Gateway->OData Channel->Configuration->Activate or Deactivate SAP Gateway if you are on a NW 740 system) and make sure SAP Gateway is active.

Assign Alias to oData Service

For the alias defined in the above step, create an entry in table /IWFND/V_MGDEAM (via transaction sm30) for service /LOOPLY/SERVICE_SRV_0001.

oData Service Authorization

In order for users to be able to post data to SAP (to approve a card for example), they must have authorization for the underlying oData service. To add this to a (new or existing) role, do the following:

  • Add authorization object s_service to the role

  • Click on the “change” button next to “Program, transaction or functi”:

  • Select “TADIR Service” in the “Type” drop-down and add the following two entries: R3TR IWSG /LOOPLY/SERVICE_SRV_0001 R3TR IWSV /LOOPLY/SERVICE_SRV 0001

Transport Changes

Transport all the changes made and new objects created in the above steps (including table entries) throughout your landscape.

Activate sicf Node

In every system in your landscape, go to transaction SICF and activate the following node:

/sap/opu/odata/looply/service_srv

This step must be repeated in every system in your landscape. See:

http://scn.sap.com/docs/DOC-42241