SAP Fieldglass (platform)

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.

Reference
API at a glance

The public API facts composerID's adapter relies on. Tenant-specific details (custom fields, picklists, approval chains) are confirmed during connection and folded into the MappingProfile.

AuthenticationOAuth 2.0 (client credentials; SAML and X.509 assertion flows also supported). Credentials and application keys provisioned per tenant/environment.
API styleREST (JSON) + OData; upload/download connectors also accept CSV. 227+ individual REST resources across requisitions, work orders, time sheets and SOW.
Base URLTenant + environment specific (provisioned per Fieldglass instance). No single public base URL.
ObjectsJob Posting / Requisition, Work Order + revisions, Worker, Time Sheet, Expense, SOW, Invoice, Supplier
Events / webhooksPoll-first. Outbound integration connectors and audit-trail downloads are configured per tenant; no general public webhook bus.
Rate limits100 requests/second per API by default; burst to 200 req/s for short durations.
Readiness
Docs confidence: Public

“Docs confidence” describes how deterministic our mapping templates can be before we connect to a tenant. Even with public docs, implementations vary — especially around custom fields, approval flows and object extensions.

Deterministic mapping

Common Workforce Model fields map to known API fields. Best for standard objects (requisitions, assignments, timesheets, POs).

Tenant discovery

composerID can scan tenant configuration (custom fields, picklists, required fields) where the platform permits it, then generate a tenant‑specific MappingProfile.

Enrichment loop

If the target platform requires a field the Intent record doesn't yet have, composerID emits an enrichment_request back to the intake layer.

Mapping
Minimum viable mapping for SAP Fieldglass

An opinionated baseline. The platform adapter enforces additional requirements via preflight. “Tenant required” fields are discovered during connection and added to the MappingProfile.

Object Canonical fields Platform target Required status Notes
Requisition (Contingent)
Create external worker request
role_title, location, start_date, cost_center, worker_type REST resource (tenant-specific) Required + tenant required Preflight enforces required fields
Statement of Work
Create services request / SOW
service_category, sow.summary, deliverables[], budget, dates REST resource (tenant-specific) Often tenant required Attach defence file where supported
Timesheet
Capture time entries
worker_id, period, hours, cost_center REST resource (tenant-specific) Required Back-sync recommended
Idempotency & drift — publish + reconcileExpand

Publish operations are idempotent using a deterministic key {intent_id}-{intent_version}-{target_system}. Because humans can change records inside the platform, composerID supports reconciliation: it compares the platform record snapshot to the canonical intent and flags drift.

Tenant specifics
Custom fields & unique mapping

Real deployments rely on program-specific custom fields (for compliance, approvals, GL coding, rate rules or supplier constraints). composerID is designed to generate tenant‑specific mappings rather than forcing you to redesign your intake.

How scanning works

High-level flow

connect_destination() → read required fields + picklists (where permitted) → detect custom fields / extensions → build MappingProfile + validation rules → preflight intent against tenant requirements

What gets produced

Portable artefacts

MappingProfile (tenant-scoped) Capabilities matrix Required-field rules Picklist dictionaries Enrichment prompts Audit spine links (defence_file_ref)
Important — where this platform is tenant-definedExpand

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
Implement the adapter

Use this page alongside the API + Schemas docs to implement: destination connection, preflight validation, publish, webhook back-sync and reconciliation.