Contents
- The Problem
- Key Benefits
- Accessing Configuration in Public Cloud (SSCUI)
- Step-by-Step Configuration Guide
- Monitoring & Error Recovery
- Troubleshooting Quick Reference
This blog focuses on multi-company configuration for PM for SAP S/4HANA Public Cloud – SAP FSA integration. We recommend reading Integrating SAP S/4HANA Public Cloud PM Order with SAP Field Service & Asset Management first, which covers the core integration concepts, architecture, and single-company setup.
1. The Problem
Imagine a multinational company running three FSA companies:
- FSA Company Europe — for plants in Germany, France, and the UK
- FSA Company Americas — for plants in the US and Brazil
- FSA Company Asia-Pacific — for plants in Japan and Australia
A PM order is created in Hamburg for Plant 1000, and another in Texas for Plant 1010.
Without multi-company configuration, both orders land in the same FSA company. The wrong dispatch team sees orders that don't belong to them, technicians are dispatched incorrectly, and SLA clocks keep ticking while the confusion is sorted out.
With multi-company integration:
- The Hamburg order is automatically routed to FSA Company Europe.
- The Texas order is automatically routed to FSA Company Americas.
- Each dispatch team sees only their work — in real time.
2. Key Benefits
Capability | What it means in practice |
Automatic plant-based routing | A single S/4HANA tenant serves multiple FSA companies based on plant and order type — no manual steps or middleware transformation needed. |
Independent filter rules | One subsidiary may push orders to FSA when Released; another may wait until Ready for Scheduling. Each company configures this independently. |
Independent code-list mappings | Status codes, service call types, problem types, priorities, and regions can all differ between FSA companies to match local configurations. |
Full error monitoring | Complete restart capability through the Error Monitoring App — no silent failures. |
No SPRO required | Accessible entirely through SSCUI — no classic transaction access needed in Public Cloud. |
3. Accessing Configuration in Public Cloud (SSCUI)
In Public Cloud S/4HANA, customers do not have access to the classic SPRO transaction. Instead, IMG activities are exposed as Self-Service Configuration UIs (SSCUIs) via the Manage Your Solution Fiori app. Configuration for the PM-FSA integration is split across two paths:
Access to these SSCUIs requires the business role SAP_BR_BPC_EXPERT (Configuration Expert – Business Process Configuration) to be assigned to your user in the SAP S/4HANA Cloud system.
Step | Application Area | Sub Application Area | Item Name |
1 | Field Service & Asset Management | Integration | Integration with SAP Field Service & Asset Management |
2–8 | Asset Management | Maintenance Management | Integration with Field Service Management |
4. Step-by-Step Configuration Guide
1. Configure Multi-Company Routing
This is the heart of the multi-company setup. Every plant that should replicate must be mapped to its target FSA Company ID. Plants not listed will not replicate.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Field Service & Asset Management | Integration | Integration with SAP Field Service & Asset Management | Configure Multiple Company Replication |
Step | Config Item | Purpose |
1 | Assign Rule Type to Replication Object | Controls routing logic per object type |
2 | Define S/4 FSA Company | Maps an S/4 Company ID to a name |
3 | Assign Replication Object Details | Enables replication per company |
4 | Assign Relevant Plants | Maps each plant + order type to the target FSA Company |
5 | Assign FSA Company Details | Links S/4 Company ID to FSA Account ID + Company ID |
Sub-step 1a: Assign Rule Type to Replication Object
Set Replication Object = PM Maintenance Order and select Rule Type 01 (Plant) for standard plant-based routing, or 07 (Custom Logic) for BAdI-driven routing.
Sub-step 1b: Define S/4HANA FSA Company
Create a logical identifier for each FSA company (e.g. 00001 = Company 1, 00002 = Company 2). This short key becomes the master reference that all subsequent configuration links back to.
Sub-step 1c: Assign FSA Company Details
For each S/4 FSA Company ID, enter the Account ID and Company ID from your FSA tenant. Find these in FSA Admin → Account Information and FSA Admin → Companies.
Sub-step 1d: Assign Replication Object Details
For each S/4 FSA Company ID, activate PM order replication by adding replication object PM Maintenance Order. This acts as a per-company master switch — if not enabled, no PM orders will ever route to that company.
Sub-step 1e: Assign Relevant Plants
Define which combination of S/4 FSA Company + Planning Plant + Order Type routes PM orders to which FSA company. This is the core routing table — every plant that should replicate must be listed here. Plants not listed will not replicate.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Field Service & Asset Management | Integration | Integration with SAP Field Service & Asset Management | Configure Multiple Company Replication |
Important: This is maintained inside the multi-company replication IMG node — it is a separate entry from the single-company plant filter and must not be confused with it.
Steps 2–8: Codelist Mappings & Filters
The following steps are configured under a separate SSCUI path — not under the multi-company replication node above.
2. Configure Mapping for Service Call Type Codelist
Every FSA Service Call needs a serviceCallType. This step maps your PM order types to the FSA code list entries.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Configure Mapping for Service Call Type Codelist |
3. Configure Mapping for Phase Codelist
Status is bidirectional. This mapping table works both ways:
- Outbound: PM system status → FSA Service Call status
- Inbound: FSA status change → PM order user status update
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Configure Mapping for Phase Codelist |
A missing status mapping doesn't cause an error — it causes a silent mismatch. Get this right.
4. Configure Mapping for Priority Codelist
PM order priorities are numeric or text codes configured in PM Customizing. FSA has its own priority codelist. Without this mapping, FSA receives the raw PM value — which almost certainly won't match any FSA entry.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Configure Mapping for Priority Codelist |
5. Configure Mapping for Problem Type Codelist
Maps PM damage or object-part codes to FSA problemType entries. This helps FSA categorize the nature of the work correctly for reporting and dispatch.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Configure Mapping for Problem Type Codelist |
6. Define System Status to Filter Maintenance Order Replication
FSA tracks a phase alongside status — representing the current execution stage of the service event. Map PM lifecycle milestones to the corresponding FSA phase and sub-phase codes, and control whether to replicate or prevent replication.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Define System Status to Filter Maintenance Order Replication |
Best Practice content is delivered — but verify and change the Replication Type as per your requirement.
7. Set Default Business Partner (Customer)
FSA Service Calls require a customer reference. PM orders don't always have one. This configuration sets a fallback default Business Partner to satisfy the FSA requirement.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Set Default Business Partner (Customer) |
8. Configure Region
Defines where the FSA region field is sourced from — the functional location, the equipment master, or a fixed value.
Application Area | Sub Application Area | Item Name | Configuration Step Name |
Asset Management | Maintenance Management | Integration with Field Service Management | Configure Region |
Best Practice content is delivered — but verify and change the Region Source Code as per your requirement.
Region drives FSA's dispatch routing logic, so this directly affects which dispatcher queue the Service Call lands in. An incorrect region means the order sits in the wrong queue.
5. Monitoring & Error Recovery
Every replication attempt — successful or failed — is recorded in SAP's Application Interface Framework (AIF). This gives operations teams complete visibility into what was sent to FSA, what FSA responded, and the ability to restart any failed message after the root cause is resolved — all without developer involvement.
Use the Fiori app Message Monitoring and Error Handling to monitor replication messages, inspect payloads, and restart failed messages.
Access to the Message Monitoring and Error Handling Fiori App requires the business role SAP_BR_CONF_EXPERT_BUS_NET_INT to be assigned to your user in the SAP S/4HANA Cloud system.
From the Message Monitoring and Error Handling app, teams can:
- See exactly which PM orders were replicated and when
- Inspect the full message payload sent to FSA and the FSA response received
- Restart failed messages with a single action — for example after a missing region in FSA has been created, or a connectivity issue has been resolved
- Receive automatic alerts when errors occur, via configurable recipient groups — ensuring nothing fails silently
Namespace | Interface | Description |
/FSMPM | ORDER_OUT | bgRFC Interface for PM Order replication to FSA |
/FSMPM | ORDER_IN | Maintenance Order Inbound |
/FSMPM | ORDEROP_IN | Maintenance Order Operation Inbound |
/FSMPM | CONFIRM_IN | Maintenance Order Confirmation Inbound |
6. Troubleshooting Quick Reference
Symptom | First Check |
Order goes to wrong FSA company | Configure Multiple Company Replication — verify plant-to-company mapping |
Order not replicated at all | Message Monitoring and Error Handling Fiori App → Namespace /FSMPM → Interface ORDER_OUT — check for errors |
Priority blank in FSA | Configure Mapping for Priority Codelist |
Service Call type wrong | Configure Mapping for Service Call Type Codelist |
References
- SAP Help: Maintenance Order Processing with SAP Field Service Management
- Integrating SAP S/4HANA Public Cloud PM Order with SAP Field Service & Asset Management
Source link
