Reference · built on requestConnectorField service & CMMS

SAP Field Service and Asset Management

Service calls, activities, equipment, and business partners from SAP Field Service and Asset Management via Data API v4 and Service API.

Request accessPricing ↗

About

SAP Field Service and Asset Management is SAP's cloud application for planning and executing field work; it took this name from SAP Field Service Management with the 2605 release. Its Data API v4 exposes more than 100 domain objects as DTOs, including ServiceCall, Activity, Equipment, BusinessPartner, and Address, with create, read, update, and delete plus filtered, expanded, and paged queries. The Service API v2 adds business actions on activities and service calls.

An operator on Fibric reads service calls and their activities, watches for changes, and proposes planning, rescheduling, or releasing an activity for your approval, leaving a receipt of what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from SAP Field Service and Asset Management and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • ServiceCall and Activity DTOs, read individually, as lists, or by external ID from /api/data/v4/{resourceName}
  • Equipment, BusinessPartner, Address, and other DTOs, with linked objects expanded in one query
  • Deleted IDs of a resource, so removals are noticed as well as edits
  • CoreSQL queries through the Query API, for example SELECT sc.id, sc.subject FROM ServiceCall sc
  • Create, update, and delete notifications for ServiceCall and Activity through the Streaming API
  • Attachments referenced from the data model through the Attachment API

Proposed actions

  • Target capability: propose a service call with its activities through /api/v2/composite-tree/service-calls
  • Target capability: propose planning or replanning an activity to a technician or team through /v2/activities/{activity-uid}/actions/plan
  • Target capability: propose rescheduling, releasing, or unassigning an activity through its business action endpoints
  • Target capability: propose cancelling a service call or marking it technically complete

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Fill a technician's day without a dispatcher

    Read unplanned activities and technician availability, then propose a plan action per activity, or an autofill for the technician's timeframe.

    With Field Dispatch

  • Warn before a promised window slips

    Compare each activity's planned start against its service call's due date and propose a reschedule or customer notice when they diverge.

    With Service Window, ETA Notice

  • Hold release until parts are on the van

    Read activities awaiting release and the equipment involved; propose release only when the operator's parts check passes.

    With Parts Readiness

Requirements

  • An SAP Field Service and Asset Management account with its cluster host, for example {cluster}.fsm.cloud.sap
  • A registered API client with a client ID and client version
  • ADMINISTRATOR or SUPERUSER privileges on the account to obtain a Service API access token
  • The company ID whose data the operator reads
Authentication
OAuth 2.0 bearer tokens; every Data API request also carries X-Account-ID, X-Company-ID, X-Client-ID, and X-Client-Version headers.

Limits

  • Data API pages hold at most 1000 objects, and standard pagination stops at 100,000 objects
  • Rate limits per identity: 3000 requests a minute on the Data v4 and Bulk APIs, 500 on the Query API, never raised per customer
  • Writes are eventually consistent: a change is stored at once but may reach user interfaces and downstream services later
  • The Streaming API is in maintenance mode; SAP points new outbound integrations to the FSM Connector

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SAP Field Service and Asset Management ↗

Questions and answers

Which headers does the Data API require?
Five on every request, including Batch and Attachment API calls: Authorization, X-Account-ID, X-Company-ID, X-Client-ID, and X-Client-Version. Tokens come from the OAuth 2.0 access API.
How are resource names written in Data API URLs?
Resource and field names in the URL are case sensitive and follow camelCase. The list endpoint has the form /api/data/v4/{resourceName}?dtos={resourceName.dtoVersion}, so each request names the DTO version it expects.
How does an external system learn about changes?
The Streaming API sends notifications when a ServiceCall or Activity is created, updated, or deleted. SAP has placed it in maintenance mode and recommends the FSM Connector for outbound communication. The Data API also lists deleted IDs of a resource for polling.
Ask about SAP Field Service and Asset Management

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SAP Field Service and Asset Management through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy