Introduction
Integrating SAP S/4HANA Public Edition (CE) with SAP Field Service Management (FSM) is a multi-layered technical setup. It spans communication configuration, event-driven architecture, and data replication across various business entities. This blog series provides a comprehensive, step-by-step walkthrough of the complete integration setup.
This guide is structured across three parts:
|
Part |
Coverage |
|
Part 1 (this post) |
Architecture overview, Communication Users, Communication Systems, Event Mesh setup |
|
Part 2 |
Communication Arrangements for all integration scenarios |
|
Part 3 |
SAP Cloud Integration (CPI) iFlow configuration (coming soon) |
The integration between SAP S/4HANA Public Edition and SAP Field Service Management involves three primary systems:
- SAP S/4HANA Public Cloud (CE) — source system for business objects (Service Orders, Business Partners, Products, Equipment, etc.)
- SAP Cloud Integration (CPI) — middleware orchestrating data flow bidirectionally
- SAP Field Service Management (FSM) — target system for field service execution
SAP Event Mesh plays a critical role specifically for the Service Order flow — it listens for Service Order change events in S/4HANA and triggers the CPI iFlow to process and forward data to FSM.
Figure 1 — Architecture Overview: SAP S/4HANA Public Edition integration with SAP Field Service Management
As part of the initial setup, the following three activities need to be completed:
- Create Communication Users
- Create 3 Communication Systems
- Create Communication Arrangements
Additionally, Event Mesh (Queue and Webhook) must be configured so that it reacts to Service Order event changes and triggers the CPI iFlow to send data to FSM.
1. iFlow Deployment
All required CPI iFlows must be deployed and active. The iFlow endpoint URLs are required during Communication Arrangement configuration.
2. Required Business Roles in S/4HANA CE
Assign the following roles to your S/4HANA user. These are required to execute the setup steps and to support master and transactional data replication:
|
Role |
Description |
|
SAP_BR_ADMINISTRATOR |
General administration |
|
SAP_BR_EMPLOYEE |
Employee access |
|
SAP_BR_PRICING_SPECIALIST |
Price replication |
|
SAP_BR_INVENTORY_MANAGER |
Stock data |
|
SAP_BR_PRODMASTER_SPECIALIST |
Product/Material master |
|
SAP_BR_BUPA_MASTER_SPECIALIST |
Business Partner data |
|
SAP_BR_CONF_EXPERT_BUS_NET_INT |
Communication & integration |
|
SAP_BR_CUSTOMER_SRVC_MGR |
Service management |
|
SAP_BR_CUSTOMER_SRVC_TEC |
Service technician access |
|
SAP_BR_BPC_EXPERT |
BPC configuration |
|
SAP_BR_MAINTENANCE_PLANNER |
Plant Maintenance planning |
|
SAP_BR_MAINT_SUPERVISOR |
Maintenance supervision |
|
SAP_BR_MD_SPECIALIST_EAM |
Enterprise Asset Management |
|
SAP_BR_PRODN_OPTR_DISC |
Production operations |
|
SAP_BR_PURCHASER |
Purchasing |
Note: Some roles are not strictly required for the initial setup but are needed during master and transactional data replication. Listed here as a consolidated reference.
A Communication User is a technical user that allows an external system to authenticate and access S/4HANA Public Cloud. Two users need to be created for this integration.
Navigate to: Communication Management → Communication Users
1.1 Inbound Communication User (CPI to S/4HANA)
Create a new user — for example, FSMIMPORT — with a description such as “CPI to S/4 Inbound User”. Set a strong password and save. This user is configured in the SAP Integration Suite as a security material credential, and is referenced within iFlows to make OData/HTTP calls to the S/4HANA CE backend.
Figure 2 — Communication User creation (FSMIMPORT). The “Used By” fields populate automatically after full configuration.
1.2 Outbound Communication User (S/4HANA to Event Mesh)
Create a second communication user — for example, EVENT_MESH_FSM_USR — for the outbound S/4HANA to Event Mesh flow.
Figure 3 — Event Mesh outbound communication user
This user requires the following role depending on the SAP BTP environment:
|
BTP Environment |
Required Role |
|
Cloud Foundry |
MessagingSend |
|
Neo |
ESBMessaging.send |
Three communication systems need to be configured to represent the external systems interacting with S/4HANA CE.
Navigate to: Communication Management → Communication Systems
|
# |
Communication System |
Direction |
Purpose |
|
1 |
Event Mesh |
Outbound |
Service Order change events → Event Mesh → CPI → FSM |
|
2 |
CPI System |
Bidirectional |
S/4 to CPI to FSM and FSM to CPI to S/4 |
|
3 |
FSM System |
Direct P2P |
S/4HANA CE directly to FSM (Service Contract, Equipment, PM Orders) |
2.1 Event Mesh Communication System
Important: The Event Mesh Communication System is auto-created when Communication Arrangement SAP_COM_0092 is saved. Manual creation is not required. Refer to Section 3.
2.2 CPI Communication System
Navigate to Communication Management → Communication Systems and create a new entry.
Enter the CPI tenant host name. Provide a meaningful alias for the Logical System / Business System Name (e.g., CPI-CF0002-FSM).
Configure Users for Inbound and Outbound Communication:
- Inbound User: FSMIMPORT — the inbound communication user from Section 1.1. Credentials are stored in the Integration Suite and used by iFlows for OData/HTTP calls.
- Outbound User: fsmimport@global.corp.sap — a technical user with access to the SAP Cloud Integration tenant.
2.3 FSM Communication System
System Name: e.g., FSM_AU_SYS
Configure the outbound user using the Client ID and Client Secret generated from the OAuth 2.0 Settings in the FSM administration console.
Figure 9 — Outbound communication setup using FSM OAuth 2.0 Client ID and Secret
Save the Communication System.
Prerequisite: Event Mesh Service Key from SAP BTP
Before creating this arrangement, obtain the Service Key from your Event Mesh instance in SAP BTP. Navigate to your BTP subaccount → Event Mesh instance → click the instance → Copy the Service Key.
Creating the Arrangement
Navigate to: Communication Management → Communication Arrangements → New
|
Field |
Value |
|
Scenario |
SAP_COM_0092 |
|
Arrangement Name |
e.g., FSM_EVENT_MESH |
|
Communication User |
EVENT_MESH_FSM_USR (from Section 1.2 — Figure 3) |
|
Service Key |
Paste the BTP Event Mesh service key |
Click on the Event Mesh instance and copy the Service Key to be entered in the Communication Arrangement screen.
After the Communication Arrangement is saved, it will look as shown below:
Important: Copy the Topic Space value displayed after saving (e.g., CCF/CF0002/CECCF). This is required for configuring the Event Mesh topic queue.
4.1 Configure Outbound Event Topics
In S/4HANA CE, navigate to the outbound event configuration and set up the event bindings for Service Orders.
Figure 15 — Outbound events list for Service Order integration
Configure Outbound Topic Bindings
Once configured, the final outbound topic bindings will appear as shown below:
Figure 17 — Completed outbound topic bindings. Whenever these Service Order events are triggered in S/4HANA, Event Mesh is notified.
After configuring outbound events in S/4HANA, set up the receiving infrastructure in the Event Mesh application in SAP BTP.
Figure 18 — SAP Event Mesh application in BTP
5.1 Create a Queue in Event Mesh
Navigate to: Event Mesh Application → Message Client → Create Queue
Figure 19 — Queue creation in the Event Mesh Message Client
Figure 20 — Queue name using the Topic Space as prefix
Use the Topic Space value copied from the Communication Arrangement as the prefix, followed by the topic name from the SAP Help documentation. Example format: CCF/CF0002/CECCF/
Figure 21 — Queue configured with the correct Topic Space prefix and topic name
5.2 Create a Webhook
Navigate to: Event Mesh Application → Message Client → Webhooks → Create
Take the CPI iFlow endpoint URL to be used as the webhook target.
Figure 22 — Retrieving the CPI iFlow URL for use in the webhook
Figure 23 — Webhook creation screen. Enter the CPI iFlow endpoint URL and link it to the queue from Step 5.1.
Once saved, the webhook will automatically trigger the CPI iFlow endpoint whenever a configured Service Order event fires.
- ☑ Two Communication Users created — inbound (FSMIMPORT) and outbound (EVENT_MESH_FSM_USR)
- ☑ Three Communication Systems configured — Event Mesh (auto-created), CPI, and FSM
- ☑ Communication Arrangement SAP_COM_0092 created for Event Mesh
- ☑ Outbound event topic bindings configured in S/4HANA CE
- ☑ Event Mesh Queue and Webhook configured in SAP BTP
What's Next — Part 2
Part 2 covers the configuration of all remaining Communication Arrangements required for the full integration — including Business Partner, Product, Service Order, Service Contract, Plant Maintenance, and more. Link
References
SAP Help Documentation:
https://help.sap.com/docs/SAP_S4HANA_CLOUD/6ef7f849fed34f95adfc449f29835255/a6e1ee3b1bf2481b9bfa1776…
Note: The information presented in this document has been sourced from the official SAP Help documentation. For additional details and the latest information, please refer to the link above
