> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# SAP Fieldglass

> SAP Fieldglass (Vendor Management & Sourcing): the API posture, publish target and field mapping composerID publishes a decision reference through.

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.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                         |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| Authentication       | OAuth 2.0 (client credentials; SAML and X.509 assertion flows also supported).                                 |
| composerID publishes | Requisition (Contingent): REST resource (tenant-specific)                                                      |
| Intent ID lands on   | `job_posting` `customFields.intentId`, written into the destination record                                     |
| Back-sync            | Polling: the destination publishes no events composerID can subscribe to, so state is read back on a schedule. |

## Vendor documentation

<Columns cols={2}>
  <Card title="SAP Fieldglass REST API Integration: General Reference (PDF)" icon="external-link" href="https://help.sap.com/doc/a5fdbd31ebe94832aef0eb79066a8087/cloud/en-US/SAPFieldglassRESTAPIIntegrationGeneralReferenceGuide.pdf" horizontal />

  <Card title="SAP Business Accelerator Hub: Fieldglass APIs" icon="external-link" href="https://api.sap.com/" horizontal />

  <Card title="SAP Fieldglass product documentation" icon="external-link" href="https://help.sap.com/docs/SAP_FIELDGLASS" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                 |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication | OAuth 2.0 (client credentials; SAML and X.509 assertion flows also supported). Credentials and application keys provisioned per tenant/environment.    |
| Style          | REST (JSON) + OData; upload/download connectors also accept CSV. 227+ individual REST resources across requisitions, work orders, time sheets and SOW. |
| Base URL       | Tenant + environment specific (provisioned per Fieldglass instance). No single public base URL.                                                        |
| Webhooks       | Poll-first. Outbound integration connectors and audit-trail downloads are configured per tenant; no general public webhook bus.                        |
| Events posture | Polling                                                                                                                                                |
| Rate limits    | 100 requests/second per API by default; burst to 200 req/s for short durations.                                                                        |
| Objects        | Job Posting / Requisition, Work Order + revisions, Worker, Time Sheet, Expense, SOW, Invoice, Supplier                                                 |

## 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.

<AccordionGroup>
  <Accordion title="Requisition (Contingent)" icon="arrow-right-left" description="Create external worker request">
    | Mapping                  | Detail                                                         |
    | ------------------------ | -------------------------------------------------------------- |
    | Canonical to destination | role\_title, location, start\_date, cost\_center, worker\_type |
    | Target                   | REST resource (tenant-specific)                                |
    | Requirement              | Required + tenant required                                     |
    | Notes                    | Preflight enforces required fields                             |
  </Accordion>

  <Accordion title="Statement of Work" icon="arrow-right-left" description="Create services request / SOW">
    | Mapping                  | Detail                                                          |
    | ------------------------ | --------------------------------------------------------------- |
    | Canonical to destination | service\_category, sow\.summary, deliverables\[], budget, dates |
    | Target                   | REST resource (tenant-specific)                                 |
    | Requirement              | Often tenant required                                           |
    | Notes                    | Attach Compliance File where supported                          |
  </Accordion>

  <Accordion title="Timesheet" icon="arrow-right-left" description="Capture time entries">
    | Mapping                  | Detail                                  |
    | ------------------------ | --------------------------------------- |
    | Canonical to destination | worker\_id, period, hours, cost\_center |
    | Target                   | REST resource (tenant-specific)         |
    | Requirement              | Required                                |
    | Notes                    | Back-sync recommended                   |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                                                                                                      |
    | ------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
    | Canonical to destination | intent\_id, intent\_version                                                                                                 |
    | Target                   | CustomField.IntentID on the Job Posting / Work Order                                                                        |
    | Requirement              | Required                                                                                                                    |
    | Notes                    | Matches the fieldglass.contingent\_requisition.v1 mapping profile; concrete custom-field key confirmed at tenant onboarding |
  </Accordion>
</AccordionGroup>

<Note>
  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.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>