Part 2 — Communication Arrangements for All Integration Scenarios

This is Part 2 of the blog series on integrating SAP S/4HANA Public Edition with SAP Field Service Management (FSM). In Part 1, we covered the architecture overview, created the Communication Users, Communication Systems, and set up the Event Mesh (SAP_COM_0092). In this part, we configure the remaining Communication Arrangements that cover all the major business object replication and direct integration scenarios between S/4HANA CE and FSM.

The following table lists all Communication Arrangements required for the complete S/4HANA CE to FSM integration:

 SAP_COM_0092 was already configured in Part 1. The sections below cover all remaining arrangements.

Navigate to: Communication Management → Communication Arrangements → New

Scenario: SAP_COM_0A50    |    Arrangement Name: e.g., FSM_CPI_COM_0A50

                    Figure 1 — Creating a new Communication Arrangement for SAP_COM_0A50

On the next screen, enter the CPI Communication System created in Part 1 — e.g., CPI-CF0002-FSM. Additional fields will be auto-populated. Save the arrangement.

Figure 2 — SAP_COM_0A50 with the CPI Communication System configured and additional fields auto-filled

Navigate to: Communication Management → Communication Arrangements → New
Scenario: SAP_COM_0008    |    Arrangement Name: e.g., FSM_BP_COM_0008

This arrangement ensures that when a Business Partner is created or changed in S/4HANA CE, it is sent to CPI for processing and then forwarded to FSM.

Enter the Communication System: CPI-CF0002-FSM

Figure 3 — Entering the CPI Communication System for SAP_COM_0008. API URL, inbound user, and outbound services are auto-populated.

Outbound Service Configuration

After the communication system is entered, all outbound services appear. Deactivate all outbound services by unchecking the Active checkbox — except for the following two:

• Business Partner – Replicate from SAP S/4HANA Cloud to Client
• Business Partner Relationship – Replicate from SAP S/4HANA Cloud to Client

Note: This ensures only BP and BP Relationship channels remain active. All IDOC channels and confirmation-related services are intentionally deactivated.

Figure 4 — Only Business Partner and Business Partner Relationship outbound services remain active

For the service “Business Partner – Replicate from SAP S/4HANA Cloud to Client”, expand the Additional Properties section and enter the DRF details:

               Figure 5 — Accessing the Additional Properties/DRF section for the BP outbound service

                                                                       Figure 6 —iFlow endpoint path

Save the arrangement.

Repeat the same for “Business Partner Relationship – Replicate from SAP S/4HANA Cloud to Client”. Use the endpoint path from the corresponding Business Partner Relationship iFlow.

                                 Figure 7 —Business Partner Relationship outbound service

Follow the same approach as SAP_COM_0008:

• Create a new Communication Arrangement with scenario SAP_COM_0009
• Enter the CPI Communication System (CPI-CF0002-FSM)
• Deactivate all outbound services except: Product Master – Replicate from SAP S/4HANA Cloud to Client
• Enter DRF details and the iFlow endpoint path for the Product Master iFlow

                        Figure 8 — SAP_COM_0009 with only Product Master replication service active

              Figure 9 — DRF configuration for Product Master replication with iFlow endpoint path

Create the Communication Arrangement following the same pattern:

• Scenario: SAP_COM_0447
• Enter the CPI Communication System
• Configure DRF details for stock replication

               Figure 10 — SAP_COM_0447 Communication Arrangement for Material Stock replication

Create the Communication Arrangement with scenario SAP_COM_0295, following the same steps used for Product and Stock above. Enter the CPI Communication System and configure the DRF details and iFlow endpoint path for the pricing iFlow.

             Figure 11 — SAP_COM_0295 Communication Arrangement for Product Price replication

Important: This is a special arrangement — it covers the direct point-to-point (P2P) integration between S/4HANA CE and FSM, without use of CPI entirely for certain object types.

Current use case covered: Service Contract Replication

Planned for future release (2608): Equipment, Functional Locations (FL), Characteristics & Classification

Unlike the previous arrangements that use the CPI system, this one uses the FSM Communication System (FSM_AU_SYS) created in Part 1. When the FSM system is selected, fields are auto-populated.

Additionally enter:

Figure 12 — SAP_COM_0687 configured with the FSM Communication System and Service Contract DRF model S4_SC

Note: For detailed configuration steps, refer to the SAP Help documentation for SAP_COM_0687.

The following arrangements are configured using the same methodology described above. For each, refer to SAP Help documentation to find the specific DRF replication model and iFlow endpoint path.

With Parts 1 and 2 finished, the complete Communication Layer for the S/4HANA CE and FSM integration is in place.

What's Next — Part 3

Part 3 will cover the SAP Cloud Integration (CPI) iFlow configuration — including how to configure, deploy each iFlow for the business scenarios covered in this blog series.

Stay tuned — Part 3 coming soon!

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