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.Requisition (Contingent)
Create external worker request
Requisition (Contingent)
Create external worker request
Statement of Work
Create services request / SOW
Statement of Work
Create services request / SOW
Timesheet
Capture time entries
Timesheet
Capture time entries
Intent ID correlation
Carry the Intent ID
Intent ID correlation
Carry the Intent ID
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.