This post is for the consultants and administrators who are actually setting up the Crowd Workforce Integration between SAP S/4HANA and SAP FSA. Part 1 of this series covered the business problem and how the integration works end to end. Here we get into the specifics: what to configure, in which system, in what order, and what to check when you're done.
Blog Series:
Part 2: Make It Work: Configuring Crowd Integration Across S/4HANA and FSA
We cover two deployment scenarios. Scenario A is the standard setup where technicians are replicated from S/4HANA service performers. Scenario B is the variant — used when the crowd partner wants to manage their own technicians directly in FSA without a corresponding employee record in S/4HANA.
Prerequisites at a Glance
System | Object / Setting | Action | Why It Matters |
SAP S/4HANA | Business Function /SHCM/EE_BP_1 | Activate in Switch Framework (transaction SFW5) | Enables the Service Performer partner function BBP005 and BUR025 relationship type for Business Partners while converting the Employee to Business Partner |
SAP S/4HANA | SAP Note 0002882172 | Review and apply as required | Documents known issues and corrections related to the /SHCM/EE_BP_1 Business Function activation |
SAP S/4HANA | Item Category for External Service Item | SRVW (or SREW for returns) configured in service order customising | Identifies service order items as external — triggers PR creation and FSA activity with subtype ‘External Service |
SAP S/4HANA | Lean Service Procurement | Standard lean service integration between SM and MM configured | Required for automatic PR creation on service order release |
SAP BTP / CPI | SAP S/4HANA–FSA integration package | Already deployed and active | Crowd integration extends the existing iFlows — it does not replace them |
SAP FSA | Crowd Workforce module | Licensed and enabled in the FSA tenant | Required for Crowd Partner and Technician objects to exist in FSA |
SAP FSA | Crowd Partner Portal | Enabled in FSA tenant configuration | External crowd partners need portal access for assignment acceptance and EMME approval |
Scenario A: Standard Setup — Technicians Replicated from S/4HANA
This is the default scenario. Everything flows from S/4HANA: the supplier, their workers, and all field activity assignments are traceable back to S/4HANA records. Use this when the customer wants S/4HANA as the single system of record for both the supplier relationship and the individual technicians.
Step 1 — Activate Business Function /SHCM/EE_BP_1
Go to transaction SFW5 in S/4HANA. Locate Business Function /SHCM/EE_BP_1 and activate it. This is a permanent, irreversible activation — confirm with the customer before proceeding. Once activated, it makes the following available:
- Partner function BBP005 (Service Performer) for use in Business Partner relationships
- Relationship type BUR025 (Employee — has Service Performer) between a person BP and a company BP
- The person type ‘Contingent Worker' on Employee BPs, which generates the Service Performer BP role on BP conversion
Important: Review SAP Note 0002882172 before activating. It covers known corrections for this Business Function that may apply to your release level.
If Customer uses Employee Group other than “9” for contingent worker than a BADi implementation is required. Reference blog: External Workforce in Employee Business Partner Data Model
Use the synchronization reports (/SHCM/RH_SYNC_BUPA_EMPL_SINGLE or /SHCM/RH_SYNC_BUPA_FROM_EMPL), to sync created employees as Business Partner with role BUP003 and BBP005.
Step 2 — Configure Partner Function BBP005 for Relationship Type BUR025
Create your supplier as a Business Partner (transaction FLVN01) with the relevant purchasing organisation and currency. Then link the service performers to this supplier using relationship type BUR025 — Has Service Performer.
That's the trigger. Once those relationships are saved, the new CPI iFlow — “Replicate Crowd Partner and Technician from SAP S/4HANA to SAP Field Service and Asset Management” — picks them up automatically and creates the Crowd Partner and Crowd Technicians in FSA. Adding or removing service performers later is handled the same way — the changes flow through to FSA Crowd Workforce without any manual intervention.
One thing that must be in place before replication runs: make sure a valid address dependent email is maintained on both the Supplier BP and each Employee BP. FSA requires an email address to create Crowd Partner and Technician records — it's how the platform sends onboarding notifications to the crowd partner. Missing emails will stop the replication.
If you don't want to maintain individual technicians in S/4HANA, there's a configuration option for that. Set the iFlow external parameter “CrowdPartner W/O Service Performer” to true. In this mode, the supplier replicates to FSA as a Crowd Partner with a placeholder technician carrying the supplier's details. The crowd partner admin then manages their own technicians directly in FSA. This is the right choice when the customer wants to keep their external workforce data out of S/4HANA entirely.
Role Mapping: Crowd Admin vs Crowd Technician: employees created with both Employee and Contingent Worker person types get both the Crowd Admins roles in FSA.
Step 3 — Configure Item Category for External Service Items
In Customizing path “SAP Customizing Implementation Guide -> Service -> Transactions -> Basic Settings -> Define Item Category Determination”, ensure the item category SRVW and SREW are configured and assigned to the relevant order type (SRVO) and item category group (SRVP or DIEN).
With this you can add External Service item categories to the Service Order.
In Customer path “SAP Customizing Implementation Guide -> Service -> Transactions Settings for Service Transactions -> Integration -> Logistics Integration -> Enterprise Organizational Management -> Define Logistics Scenario for Procurement of Materials and Services”, for the Purchase Requisition to auto create on the External Service Item, add PREQ as logistic.
If you are using legacy org, then patch will “SAP Customizing Implementation Guide -> Service -> Transactions Settings for Service Transactions -> Integration -> Logistics Integration -> Organizational Management(Legacy) -> Define Logistics Scenario for Procurement of Materials and Services”
Step 4 — Add Vendor and Service Performer Parties in Service
To update the Vendor and External technician to the External service item, maintain Vendor (0000019) and Service Performer (0000028) functions against Ext. Service Item (00000032) & Ext. Confirmation Service Item (00000033) categories in the Partner Function determination in Service.
Customizing path: “SAP Customizing Implementation Guide -> Service -> Basic Functions -> Partner Processing -> Define Partner Determination Procedure in Service”
Step 5: Authorization to access Purchase apps:
Make sure you have below roles to view purchase orders, requisition and service entry sheet
SAP_BR_EMPLOYEE_PROCUREMENT, SAP_BR_PURCHASER. SAP_BR_INTERNAL_SALES_REP
Step 6: Maintain Purchasing Info Record:
Maintain mapping of Purchase Org and Plant with the Service Material and Supplier in Purchasing Info Record (tcode ME11). This is required to create purchase order using purchase requisition.
Step 7 — Configure the CPI iFlows
In SAP BTP Integration Suite, open the standard package “SAP S/4HANA Integration with SAP Field Service and Assent Management”. The four iFlows relevant to crowd integration are:
- Replicate Service Order from SAP S4HANA to SAP Field Service and Asset Management SOAP — sends service order and external service item to FSA on release. Configure “External Service Item Categories” as SRVW,SREW.
- Notify External Service Order Item with Crowd Changes from SAP Field Service and Asset Management to SAP S4HANA – sends all crowd updates to external item.
- Crowd Service Entry Sheet Creation from SAP Field Service and Asset Management to SAP S4HANA – creates Service Entry Sheet on activity confirmations on external activity.
- Route Payload from SAP Field Service and Asset Management to SAP S/4HANA — handles all inbound FSA crowd events
Step 8 —FSA Connector Events for Crowd Business Events
The crowd business events mentioned below will be routed through the FSM Connector outbound event to initiate CPI endpoint. There is not configuration required, this will be taken care by standard in FSA.
Event | When It Fires | What It Triggers in S/4HANA |
crowd.activity.assigned and accepted | Crowd partner accepts assignment in Partner Portal | Updates Vendor and Service Performer on S/4HANA service order item |
crowd.activity.released | Crowd partner releases activity for field execution | Triggers automatic PO creation in S/4HANA via FSMIMPORT |
crowd.activity.cancelled | Assignment cancelled by crowd partner | Updates service order status in S/4HANA |
crowd.activity.unassigned | Activity unassigned from crowd resource | Clears assignment data from S/4HANA service order item |
EMME time effort approved activity.confirmed on external activity | Crowd admin approves time effort booking | Creates SES (for time effort) + auto-approves + triggers Service Confirmation in S/4HANA Create Service Confirmations for other non-time EMME’s like Expenses, Mileages, & Material |
Step 9 — Enable the Crowd Workforce Module in FSA
In FSA, go to Admin → Company Settings and verify that the Crowd module is enabled.
For details, refer to Configure Single Tenant Crowd.
Scenario B – Technicians Managed Only in FSA
Some customers want to onboard their external suppliers as crowd partners in FSA but don't want to maintain individual technician records in S/4HANA. The supplier manages their own workforce directly in FSA.
To achieve this, follow below handling in the configurations:
In the CPI iFlow parameters, configure “CrowdPartner W/O Service Performer” parameter as true in below iflows
- Replicate Business Partner
- Replicate Crowd Partner and Technician from SAP S4HANA to SAP Field Service and Asset Management
- Crowd Service Entry Sheet Creation from SAP Field Service and Asset Management to SAP S4HANA
- Notify External Service Order Item with Crowd Changes from SAP Field Service and Asset Management to SAP S4HANA
The effects of that single flag change:
- The Supplier BP still replicates to FSA as a Crowd Partner — the company-level entity is created
- No Crowd Technicians or Admins are created from S/4HANA service performer relationships
- The crowd partner admin creates and manages their own technicians directly in FSA
- When the crowd partner accepts and releases assignments, S/4HANA receives the status update (In Execution) but not the Executing Service Employee nor Service Performer.
Note that email is maintained on the Supplier in this scenario as well.
Scenario Comparison
Capability | Scenario A — Standard | Scenario B — Without Technician S4HANA |
Technician data in S/4HANA | Required (employee BPs with BUR025 relationship) | Not required |
Crowd Technician creation | Automatic from S/4HANA service performer replication | Manual, directly in FSA by crowd partner admin |
Technician identity in S/4HANA | Visible on service order Parties Involved | Not populated (status update only) |
Executing Employee on Confirmation | Actual technician from FSA assignment | Fallback to service order creator |
Best for | Customers who manage supplier workforce in S/4HANA and want full traceability | Customers who let suppliers self-manage their teams in FSA |
EMME Processing: Two Paths, One Clear Rule
When a technician books work through the FSA EMME journal, the integration handles different entry types differently. This is worth understanding explicitly because it affects what gets created in S/4HANA.
Path A: Time Efforts
Time effort entries — the hours a technician spent on the job — go through a specific path that uses the Purchase Order created earlier in the process:
- Technician logs time effort in FSA mobile app
- Crowd admin approves the time effort
- CPI iFlow creates a Service Entry Sheet in S/4HANA referencing the Purchase Order
- The SES is automatically approved by the integration
- S/4HANA creates a Service Confirmation on SES approval — actual cost is posted
The SES → Confirmation path is what makes this integration financially compliant. The Purchase Order acts as the financial commitment, the SES captures the actual delivery, and the Confirmation posts the cost. This is the standard three-way match for service procurement.
Path B: Materials, Mileage, and Expenses
Non-time EMME entries — materials used, mileage driven, expenses incurred — follow the existing standard FSA service confirmation flow. There is no change to this path. These entries do not go through the SES route and are not tied to the Purchase Order. They create service confirmations directly in S/4HANA through the same mechanism that was already in place before the crowd integration.
Worth Clarifying with Customers: If your customer uses material items heavily in their EMME journals, make sure they understand that only time efforts go through the SES path. Material-based costs are confirmed separately and are not linked to the crowd PO.
References:
Crowd External Service Integration
Crowd Partner and Crowd Technician Replication
Configure the External Service Item Categories and Set Purchase Requisition
Get Details on External Workforce in Employee Business Partner Data Model
Cookbook on Employee Business Partner Integration Cookbook of Employee BP Integration
Source link