A practical decision guide for choosing the right SAP FSM integration path for your landscape.
Connecting SAP Field Service Management (FSM) to your back-office SAP system is not a one-size-fits-all decision. Two distinct SAP FSM integration paths exist, and the right choice depends entirely on your SAP landscape.
Choosing the wrong approach can lead to unnecessary complexity and costly rework. This guide will help you make the right decision from day one.
The Two SAP FSM Integration Paths
SAP FSM connects to your SAP back-end via two primary connectors, each designed for a specific type of landscape:
How the Proaxia Cloud Connector Works
PCC sits between your SAP back-end and FSM Cloud as a three-component middleware layer. The ABAP Add-on (installed in SAP ECC or S/4HANA) holds all business logic.
The Message Broker handles data conversion and message queuing. The Transporter manages secure outbound delivery to FSM Cloud.
A key design characteristic is that communication is outbound-only from the Message Broker to FSM Cloud. FSM cannot initiate connections inward.
The Message Broker can be hosted on Windows, Linux, or SAP BTP – and guarantees message ordering, meaning no data is ever lost or delivered out of sequence.
How the SAP Integration Suite (CPI) Works
SAP Integration Suite (CPI), running on SAP BTP, acts as the central integration hub between SAP S/4HANA and SAP FSM Cloud. Rather than custom-built point-to-point connections, it uses pre-delivered integration flows (iFlows) – regularly maintained and updated by SAP – meaning your integration stays current without additional development effort.
Data flows in two directions. From S/4HANA, service orders, service items, and service parts are pushed outbound to FSM, so technicians have everything they need before they arrive on site. From FSM, confirmations, time and effort records, expenses, mileage, and attachments flow back into S/4HANA – closing the loop on the service lifecycle automatically.
Side-by-Side Comparison
Use this table to quickly assess which SAP FSM integration connector best fits your environment.
| Criteria | Proaxia Cloud Connector (PCC) | SAP Integration Suite (CPI) |
| Best For | SAP ECC and S/4HANA on-premises | S/4HANA Public Cloud, CX Service Cloud |
| Deployment | On-premises, Windows/Linux, or BTP | Cloud-native, fully managed by SAP |
| SAP Modules | CS, PM, PS, PP, S/4HANA Service, Advanced Execution | S/4HANA Service Cloud, CRM 7.0, CX Cloud |
| Versions Supported | ECC 6.0+ (PACG200); S/4HANA (S4PACG200 / S4PACG300+ / S4PACG400) | No version add-on required – cloud-managed |
| Licensing | Proaxia licence + SAP FSM Cloud subscription | SAP Integration Suite subscription |
| Setup Complexity | Moderate – ABAP add-on + middleware layer | Lower – pre-built iFlows, cloud-managed |
| Customisation | High – BAdIs, config tables, event handlers | Moderate – iFlow configuration |
| Data Sync | Near real-time via Message Broker queuing | Real-time cloud-to-cloud |
| Confirmation Writeback | Full writeback: time, expenses, mileage, checkout PDF | Standard confirmation writeback via iFlows |
| Ideal Landscape | Staying on ECC or on-prem S/4HANA | Moving to or already on S/4HANA Cloud |
The Full-Service Lifecycle with PCC
PCC doesn’t just send data one way – it supports the complete end-to-end service lifecycle, including confirmation writeback from the field to SAP.
This is the flow for S/4HANA Service orders, which is the most common starting point:
| # | Stage | What Happens |
| 1 | Order Created | Service order raised in SAP (ECC or S/4HANA) |
| 2 | Sent to FSM | PCC transmits order data via Message Broker to FSM Cloud |
| 3 | Planning & Dispatch | The dispatcher assigns technicians in FSM Planning and Dispatching |
| 4 | Field Execution | Technicians execute jobs via FSM Mobile – logging time, parts, expenses, and mileage |
| 5 | Checkout | Technicians complete checkout in FSM Mobile; a checkout PDF is auto-attached to the SAP order |
| 6 | Confirmation Writeback | Time, expenses, mileage written back to SAP Service Order/CATS |
| 7 | Invoice | SAP generates service confirmation, debit memo, and invoice |
Writeback details: technicians log time, materials, expenses, and mileage in FSM Mobile.
These are confirmed back to the SAP Service Order, either via standard Fiori confirmation or CATS (Cross-Application Time Sheet).
A Checkout PDF is automatically attached to the SAP order item as a permanent, auditable record of field completion.
The Full-Service Lifecycle with SAP Integration Suite (CPI)
SAP Integration Suite (CPI) powers the native, cloud-to-cloud integration between S/4HANA Public / Service Cloud and SAP FSM – with no on-premises middleware required.
All data flows in real time via pre-built iFlows deployed on SAP BTP.
This is the complete 8-stage flow:
| # | Stage | What Happens |
| 1 | Master Data Replicated | Business partners, equipment, functional locations and employees are replicated from S/4HANA Cloud to FSM via CPI iFlows (or MDI) before any order is raised, ensuring FSM always has current reference data. |
| 2 | Order Created and Released | Service Order created and released in S/4HANA Service Cloud. The Data Replication Framework (DRF) automatically triggers replication to push it downstream. |
| 3 | Sent to FSM via iFlow | CPI’s outbound iFlow transforms and transmits the Service Order (ServiceCall, Activities, Reserved Materials) in real time to FSM Cloud via the FSM Connector API – no queue, no broker. |
| 4 | Planning & Dispatch | Order appears on the FSM Planning Board. A dispatcher assigns a technician manually or via AI-assisted scheduling. The technician instantly receives a push notification on FSM Mobile. |
| 5 | Field Execution | The technician executes the job on FSM Mobile, logging time, materials, expenses, and mileage. The customer countersigns the service summary on the device before close-out. |
| 6 | Confirmation Writeback | On checkout or T&M approval, FSM fires an event to the CPI Routing iFlow, which transforms and writes the confirmation back to S/4HANA – creating the Service Confirmation, CATS timesheet entries and goods movements. |
| 7 | Error Monitoring | Failed inbound/outbound messages surface in the FSM Connector Error Monitoring console for one-click retry. Administrators can also trace the full flow via SAP BTP’s Message Processing Logs. |
| 8 | Invoice | S/4HANA generates the debit memo request and final customer invoice based on confirmed service data written back from FSM – closing the financial loop without manual intervention. |
Key Difference Between the SAP FSM Integration Approaches
Unlike PCC, CPI is bidirectional and real-time, with S/4HANA pushing data to FSM and FSM writing data back to S/4HANA through separate iFlows and without an intermediate message broker.
SAP Integration Suite also handles master data replication as an explicit stage (Stage 1), whereas PCC manages this transparently via its ABAP Add-on.
If your landscape spans multiple systems, PCC and CPI can coexist in the same FSM tenant – PCC for on-premises workloads and CPI for cloud environments.
Which Connector Fits Your Scenario? Find out below.
| Your Landscape | Use This Connector | Why |
| SAP ECC 6.0+ (any version) | Proaxia PCC | PCC is purpose-built for ECC with PACG200 add-on supporting CS, PM, PS, and PP. |
| S/4HANA on-premises or compatibility mode | Proaxia PCC | S4PACG200/300/400 add-on installs directly in on-prem S/4HANA – no cloud dependency. |
| S/4HANA 2021+ on-premises | Proaxia PCC | Use S4PACG300 or S4PACG400, depending on the version – both are fully supported. |
| SAP S/4HANA Public Cloud | SAP CPI | PCC requires an ABAP add-on which cannot be installed in the public cloud. |
| SAP CX / C4C Service Cloud | SAP CPI | SAP provides pre-built CPI iFlows for the full CX portfolio. |
| SAP CRM 7.0 | SAP CPI | PCC doesn’t support CRM 7.0 – CPI is the correct and only route. |
| SAP Business One | B1 Cloud Connector | Neither PCC nor CPI – SAP Business One uses its own dedicated connector. |
| Mixed: ECC + S/4HANA Public Cloud | Both | PCC for on-prem ECC workloads, CPI for cloud-side – they coexist in the same FSM tenant. |
| Asset-intensive PM / EAM operations | Proaxia PCC | Full component-to-inventory linking in the PM module prevents wrong-part dispatching. |
| Project-driven field work (PS/WBS) | Proaxia PCC | PS integration with WBS elements and real-time milestone writeback is unique to PCC. |
When SAP Integration Suite (CPI) Is the Right Choice
CPI is SAP’s strategic cloud-native integration approach for modern SAP landscapes.
Here’s when to choose it over PCC:
| Running SAP S/4HANA Public Cloud | PCC requires an on-prem ABAP add-on, which cannot be installed in the public cloud. CPI is the only viable path. |
| SAP CX / C4C Service Cloud landscape | SAP maintains purpose-built CPI iFlows for the CX portfolio, updated with every release. |
| SAP CRM 7.0 | PCC doesn’t support CRM 7.0. CPI is the only connector available for this system. |
| Minimal on-premises footprint desired | CPI is fully managed by SAP in the cloud. No middleware servers, no on-premise maintenance overhead. |
Still unsure which SAP FSM integration approach is right for your landscape?
On Device Solutions has hands-on experience implementing both the Proaxia Cloud Connector and SAP Integration Suite across a wide range of SAP landscapes – ECC, on-premises S/4HANA, hybrid, and cloud environments.
Whether you’re starting fresh, migrating, or troubleshooting an existing integration, we can help you assess your landscape, pick the right connector, and implement it correctly the first time.
|
Quick Rule of Thumb Still on ECC or on-premises S/4HANA? → Proaxia PCC Already in S/4HANA Cloud or CX? → SAP Integration Suite (CPI) Running both? → Both connectors can coexist in the same FSM tenant. Not sure? → That’s what we’re here for. |
Contact us to ensure your SAP FSM integration is built on the right foundation.
