Connectors > Generic REST Endpoints

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors


ASAPIO Integration Add-on facilitates the direct integration of supported SAP NetWeaver® systems with REST endpoints.

Add-on/component name Type
ASAPIO Integration Add-on – Framework Base component (required)
ASAPIO Integration Add-on – REST Connector Additional package

Key features:

  • Supports a wide range of SAP NetWeaver based systems, including SAP ERP, S/4HANA, BW, HCM and many more
  • Out-of-the-box connectivity to many REST endpoints (generic connectivity)
  • Inbound connectivity is also possible, using a webhook to call the ASAPIO REST endpoint
  • Switch between event-driven (single events) or batch mode (job-driven) calls
  • Batch mode allows multi-threading with multiple SAP work processes

Block Architecture (Example)


Pre-requisites for REST endpoints

REST endpoint shall support one of the following authentication methods:

  • Basic authentication
  • Certificate based authentication
  • OAuth – coming soon

Endpoint URLs shall be reachable from SAP server which is running ASAPIO Add-on.

Steps required to establish connectivity

To establish connectivity with the REST service, please proceed with the following activities and refer to the specific documentation chapters:

  1. Create RFC destinations in the SAP system settings
  2. Set-up authentication
  3. Set-up basic configuration to lay the foundation of using REST connector
  4. Set-up connection instance to REST endpoint in ASAPIO Integration Add on
  5. See chapter Send example outbound message for a simple example to test connectivity

Create RFC destinations

Add Certificate to Trust Store

  • Download certificates necessary for your endpoint.
  • In transaction STRUST, double click the node “SSL Client (Anonymous)”.

  • In the very bottom press the “Import certificate” button and select the downloaded certificate file
  • Press the “Add to Certificate List” button. Confirm by pressing “Save” button at the very top.


Create RFC destination for REST endpoint

  • Transaction: SM59
  • Create new destination of type “G”
  • On “Technical Settings” tab, specify Target Host: <your REST endpoint host>
  • On “Logon & Security” tab, activate SSL and select ANONYM SSL Client
  • Save and press on “Connection Test”. Depending on your endpoint this can result in HTTP status code 404 or 405. This test is only meant to check the SSL configuration. So if you don’t get an SSL error this step is fine.


Set-up basic settings

The following settings are specific to the REST Connector

Configure cloud adapter

Add an entry for the connector to the list of cloud adapters:

  • Transaction: SPRO
  • Go to IMG > ASAPIO Integration Add-on Maintain Cloud Adapter. Add New Entry and specify:
  • Name: please specify a unique custom name, e.g. “REST_HANDLER”
  • Cloud Type

Set-up Codepages

Specify codepages used in the integration:

  • Transaction: SPRO
  • Go to IMG > ASAPIO Cloud IntegratorMaintain Cloud Codepages
  • Add New Entry and specify the code pages to be used, e.g.:

Set-up connection instance

Create the connection instance customizing together with the RFC destination created earlier and the cloud connector type:

  • Transaction: SPRO
  • Go to IMG > ASAPIO Integration Add-on Connection and Replication Object Customizing
  • Add New Entry and specify:
    • Field Instance: a name for this connection in
    • Field RFC Dest. (Upload): the RFC destination create for the messaging endpoint
    • Field ISO Code: the code page to use
    • Field Cloud Type: <the connector name you chose for the REST handler connector>

Set-up outbound messaging

Create Message Type


Example: in the example below, we use the Sales Order (BUS2032) event. Please choose any other suitable example if required.


For each object to be sent via ACI you have to create a message type:

  • Transaction: WE81
  • Add New Entry and specify:
    • Message Type: unique name for the integration
    • Description: description of the purpose

Ein Bild, das Tisch enthält. Automatisch generierte Beschreibung

Activate Message Type

The created message type has to be activated:

  • Transaction: BD50
  • Add New Entry and specify:
    • Message Type: the created message type
    • Active: tick the checkbox

Ein Bild, das Text enthält. Automatisch generierte Beschreibung

Set-up target endpoint in ‘Header Attributes’

Configure the URL path to send the events to:

  • Go to section Header Attributes
  • Add New Entry and specify:
Header Attribute Header Attribute Value
ACI_HTTP_URI sap_demo/sales_order


Set up ‘Business Object Event Linkage’

Link the configuration of the outbound object to a Business Object event:

  • Go to section Header Attributes
    • or use transaction SWE2
  • Add New Entry and specify:
    • Object Category: BO BOR Object Type
    • Object Type: the Business Object Type sending the event
    • Event: the event to react to
    • Receiver Type: the message type of the outbound object (this is the link to the Addon configuration)
    • Receiver Call: Function Module
    • Receiver Function Module: /ASADEV/ACI_EVENTS_TRIGGER
    • Linkage Activated: tick the checkbox


Ein Bild, das Text enthält. Automatisch generierte Beschreibung


For further configuration of the payload etc. please go to Outbound messaging – ASAPIO

Scroll to Top