/
Architecture and Data Flow

Architecture and Data Flow

Owned by Maria Hald
Jun 12, 2025

This page describes the architecture and functionality of the bidirectional integration between ServiceNow and the SAP system, using the SAP Business Technology Platform (BTP), the SAP Integration Suite, the Cloud Connector, and the SmartChange solution by REALTECH. The goal is to explain the technical communication flow clearly and to proactively address potential questions related to security and user handling.

image-20250612-092322.png

 

SAP System → ServiceNow (Display of Transport Data in the Panel)

  1. Data Source:
    The data originates from REALTECH SmartChange. Once a transport request is linked to a ServiceNow Change or Incident, updates to that transport request are automatically displayed in ServiceNow. This includes the current status of the transport, its current stage in the process, approvals at each stage, and all SAP systems involved in the transport lifecycle, including their respective status information.

  2. RFC Connection (HTTPS to external server):
    The SAP system sends the data directly via RFC (HTTPS to external server) to the ServiceNow instance. This connection is defined in SAP as a destination of type "HTTPS to external server".

  3. ServiceNow:
    The ServiceNow instance receives the data via a predefined endpoint provided by our "SAP Transport Integration" plugin.

  4. SmartChange Panel:
    The SmartChange Transport Integration Panel in ServiceNow consumes the data and displays it in a user-friendly manner.

  5. Configuration:
    Connection and activation are handled through the SmartChange Integration Framework within the SAP system. RFC connection details, endpoint information, and technical parameters are configured here. The technical configuration is delivered via preconfigured templates.

 

For SAP → ServiceNow, data is delivered directly via an RFC connection from the SAP system to the ServiceNow instance, and displayed in the SmartChange panel.

ServiceNow → SAP System (e.g. Creating Transport Requests, Approvals)

  1. User Input:
    In ServiceNow, the user triggers an action (e.g. create transport, approve request).

  2. API Call:
    ServiceNow sends a request to an API endpoint provided in the SAP Integration Suite (Cloud Integration) using HTTPS and token-based authentication.

  3. SAP Cloud Connector:
    The request is securely forwarded (trusted) to the on-premise SAP system via the Cloud Connector.

  4. Technical User:
    Authentication in SAP is currently handled via a technical user.

  5. Authorization Mapping:

    • A BAdI (Business Add-In) in SmartChange enables mapping between the ServiceNow user and a corresponding SAP user.

    • After activation, individual mappings can be maintained.

    • All SAP authorization checks are performed against the mapped SAP user.

    • The mapped user is also recorded in all relevant logs.

 

 

 

For ServiceNow → SAP, the SAP Integration Suite and Cloud Connector are used.