Skip to main content
This page records how composerID publishes into SAP Fieldglass: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. SAP Fieldglass is a structured, enterprise VMS used to manage large external workforces and SOW services at global scale. composerID turns Triage intent into deterministic Fieldglass records (requisitions, SOW and time objects) handling tenant-specific requirements via preflight and enrichment.
Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Vendor documentation

SAP Fieldglass REST API Integration: General Reference (PDF)

SAP Business Accelerator Hub: Fieldglass APIs

SAP Fieldglass product documentation

API posture

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
Some Fieldglass requirements are program/tenant-defined (custom fields, approval chains, code lists). Even with public PDFs, a tenant connection is needed to confirm required fields and generate a tenant-specific MappingProfile. Legacy SAP landscapes may route via BAPIs/RFCs/IDocs rather than modern REST: confirm the integration path per tenant.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.