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
  • Overview
  • Looply ABAP Add-on
  • SAP OAuth 2.0 Client & Role Setup
  • Making SAP Endpoints Accessible
  • Optional: SAP BTP Proxy Integration

SAP Integration: ABAP Add-on & Access

Looply connects seamlessly with SAP ECC and S/4HANA systems, enabling real-time notifications and workflow interactions inside Microsoft Teams.

This page explains the core components required to integrate Looply with your SAP landscape.

Overview

To enable SAP integration, Looply requires:

  • The installation of the Looply ABAP Add-on on your SAP Gateway system

  • Configuration of OAuth 2.0 authentication in SAP Gateway

  • Exposure of specific SAP endpoints externally (secure HTTPS access)

Looply ABAP Add-on

The Looply ABAP Add-on is installed on your SAP system.

Purpose

  • Exposes standardized OData services for workflow interactions

  • Handles user delegation securely via OAuth 2.0 and SAML assertions

  • Simplifies access management via predefined PFCG roles

Deployment

  • Lightweight footprint; no core SAP modifications

SAP OAuth 2.0 Client & Role Setup

To enable secure, delegated access between Looply and SAP:

  • Create a new OAuth 2.0 Client in SAP Gateway

  • Configure SAML 2.0 Federation between Azure AD and SAP

  • Assign SAP users the necessary PFCG roles to authorize access to Looply services

Typical PFCG roles will grant controlled access to:

  • OData services exposed by Looply

  • Authorization token endpoints

Note: OAuth 2.0 setup must be completed separately for each SAP environment (DEV, QA, PROD).

Making SAP Endpoints Accessible

Looply requires your SAP system to expose two key HTTPS endpoints externally:

Endpoint
Purpose

/sap/opu/odata/looply/service_srv/*

OData services for workflow

/sap/bc/sec/oauth2/token

OAuth 2.0 token exchange

Options for Exposure

  • Proxy via Azure Application Gateway (recommended)

  • Expose directly through firewall/NAT rules

These endpoints must be accessible from Looply's hosted environment (AWS). AWS IP address for whitelisting Looply: 52.208.220.68

If your SAP system is not externally exposed, we recommend setting up a secure proxy in Azure/applicable public facing infrastructure to enable it.

Optional: SAP BTP Proxy Integration

If your organization uses SAP BTP Integration Suite and Cloud Connector, Looply can also connect to your SAP systems via BTP.

This model adds an extra layer of abstraction between Looply and your on-premise SAP Gateway.

  • Useful for customers standardizing integration patterns via BTP

PreviousSystem RequirementsNextSecurity & Identity - What IT Teams Need to Know

Last updated 1 month ago

Installation instructions are detailed in the .

SAP Integration Installation Guide