/
SAP System Prerequisites BI-DIRECTIONAL - ServiceNow Integration

SAP System Prerequisites BI-DIRECTIONAL - ServiceNow Integration

Owned by Maria Hald
Last updated: Jan 15, 2025
2 min read

If you use SmartChange Panel bi-directionally the following steps must be configured in SAP.

Example for Bi-directional activities

  • create transport requests

  • approve transport request

  • display TM attributes in SmartChange Panel

Step

Transaction

Description

Step

Transaction

Description

1

Import transport requests

 

Import the transport request SmartChange (OData Hub_Registration v5.x.0.0).
The transport request is included in the latest Service Pack!

2

Activate web services

SICF

The following services are consumed and must be activated

  • /sap/bc/gui/sap/its/webgui
    SAP Login for WebGUI

  • /sap/public/bc/icf/logoff
    SAP Logoff for user logout

  • /sap/opu/*
    OData for SAP Products

  • /sap/opu/odata/RTC/TM_GW_SRV/*
    All Realtech OData Services are located under this path

  • /sap/opu/odata/RTC/TM_GW_NOTIFY_SRV/*
    SmartChange notification OData Services

Service WEBGUI

In the Handler List, add /RTC/CL_HTTP_HANDLE to the last position

image-20241218-165345.png

 

3

Configure SAP Gateway Routing

SPRO

  1. Activate SAP NetWeaver Gateway
    IMG Path: SAP NetWeaver > SAP Gateway > OData Channel > Configuration

  2. Create SAP System Alias
    IMG Path: SAP NetWeaver > SAP Gateway > OData Channel > Connect Settings > SAP NetWeaver Gateway to SAP System > Manage SAP System Aliases

  • Not using a central hub please check if system alias LOCAL is created

  • Using SAP Gateway Server as central hub, create a system alias with (trusted!) RFC Destination to your backend system (e.g. NT3_SC_INT)

image-20241218-170329.png

 

4

Activate and Maintain Services

/IWFND/MAINT_SERVICE

Technical Service Name:

  • /RTC/TM_GW_SRV

  • /RTC/TM_GW_NOTIFY_SRV

  1. Click on the service name in the Service Catalog. 

  2. In the Systems Aliases window - add the system alias created before. 

  3. In the ICF nodes window - Activate the ODATA ICF node.  

5

Create Trusted RFC connection

 

Create trusted RFC connections between all development systems and TM Server

Note:
The trusted RFC connection is needed for distributed landscapes (TM Controller is not on the Development system)
Development system should trust TM Controller. 

6

Authorization for using trusted RFC connections

 

Assign the role /RTC/SC_INTEGRATION (object S_RFCACL) to all user using Odata Services (e.g. with SmartChange Approval, SAP Transport Integration).

7

Managing HTTP Whitelist

UCONCOCKPIT

If you use an HTTP whitelist, only HTTP calls from URLs in this list are accepted by the system. You can call this function from the UCON Cockpit).

Before SAP NW Release 7.51 SP00, it was only possible to edit the HTTP whitelist using the database table HTTP_WHITELIST.

Firewall

Following services will be called from SAP Transport Integration App

  • <default_host>/sap/bc/gui/sap/its/webgui

  • <default_host>/sap/public/bc/icf/logoff

  • <default_host>/sap/opu/odata/RTC/TM_GW_SRV

  • <default_host>/sap/opu/odata/RTC/TM_GW_NOTIFY_SRV

If you require the IP address for SAP Transport Integration outgoing calls, kindly raise a support ticket.