# SAP Field Service Management with SAP Business One > Source: https://netray.co/stack/sap-field-service-management-sap-business-one > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer SAP Field Service Management (the former Coresystems product, delivered with Coresuite) dispatches technicians, tracks service activities and syncs with Business One service calls and billing through a native integration. It suits manufacturers who install and maintain equipment and want technician scheduling beyond what Business One's service module offers. ## Erp SAP Business One ## Erp Key sap-b1 ## On Prem true ## Product SAP Field Service Management (with Coresuite) ## Vendor SAP (formerly Coresystems) ## Category Field service ## Integration **Method:** Native SAP FSM to Business One integration **Detail:** SAP describes a native connection in which Business One remains the system of record for customers, items and billing, while FSM handles dispatch, mobile work and time and material capture. A published case study describes this setup in practice. **Method:** Business One service documents **Detail:** Service calls, activities and equipment cards in Business One correspond to service calls and activities in FSM. Exact object mapping depends on the integration version, so check it with SAP. ## Data Flows **From:** SAP Business One **To:** SAP FSM **Data:** Customers, business partner addresses, items and equipment **Trigger:** Master data change, scheduled sync **From:** SAP Business One **To:** SAP FSM **Data:** Service calls to be dispatched **Trigger:** Service call created **From:** SAP FSM **To:** SAP Business One **Data:** Technician time, materials and expenses booked on the job **Trigger:** Activity completed on mobile **From:** SAP FSM **To:** SAP Business One **Data:** Service call status and completion notes **Trigger:** Status change **From:** SAP Business One **To:** Billing **Data:** Invoice from confirmed time and material **Trigger:** Service call closed and released ## Setup ### Define the service process **Detail:** Agree how a service call is created, dispatched, completed and billed, and which system holds each step. ### Provision FSM and the connector **Detail:** Set up the FSM tenant and the Business One integration with SAP or your implementation partner. ### Clean master data **Detail:** Fix customer addresses, equipment cards and service item definitions before synchronising them. ### Configure technicians and skills **Detail:** Create technician records, skills, working hours and warehouses for van stock. ### Map time, material and expense items **Detail:** Choose Business One items used for labour, travel and parts so billing posts correctly. ### Pilot with one team **Detail:** Run real jobs for a few weeks and compare FSM data to Business One billing. ### Roll out mobile usage **Detail:** Train technicians and set rules for offline use and photo capture. ## Pitfalls - Equipment cards with incomplete serial numbers or addresses cause dispatching errors. - Technicians booking parts that do not exist in van stock create negative inventory in Business One. - Time booked to the wrong labour item produces wrong invoice amounts. - Two way sync of master data can overwrite changes if ownership is not defined. - Contract and warranty rules held in Business One are not visible to technicians unless they are mapped. - Sync delays mean the office sees job status late, so set expectations about timing. ## Ai Layer ### Billing exception review **Description:** A private assistant compares FSM activities with Business One invoices and flags jobs closed without billing or billed with unusual time or parts. ### Repeat failure analysis **Description:** Reads service history across equipment cards and job notes to surface machines with recurring faults for a service manager. ### Plain language service questions **Description:** Managers ask which jobs are overdue, which technician has which parts, and which contracts are expiring, read only. ### Job note drafting **Description:** Drafts customer facing summaries from technician notes for review before sending. ## Alternatives - Business One's own service module, if you have few technicians and simple scheduling. - A third party field service app for Business One from the SAP partner ecosystem, if cost matters more than depth. - Spreadsheet and calendar dispatch for very small teams. ## Faq ### Is SAP FSM the same as Coresystems? **Answer:** SAP acquired Coresystems in 2018 and its product became SAP Field Service Management. Coresuite is the related partner integration offering. Naming differs by source, so confirm current product names with SAP. ### Does Business One remain the system of record? **Answer:** In the described setup, yes for customers, items and billing, while FSM manages dispatch and mobile work. Where each field lives should be decided explicitly in design. ### Does it work with on-prem Business One? **Answer:** The integration needs a secure connection between the cloud FSM service and your Business One server. Check connectivity options and supported versions with SAP. ### What would AI add? **Answer:** A private assistant can reconcile FSM jobs with Business One billing and answer service questions across both. It stays read only and sends proposed fixes to a person to approve. ## Source https://www.coresystems.ch/hubfs/Case%20Studies%202023/Fleming-Case%20Study-EN.pdf ## Search terms sap field service management business one, coresuite business one, sap fsm business one integration, coresystems sap business one, field service sap b1, technician dispatch business one --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json