.png)
SAP Fieldglass Integration Guide
Integrate SAP Fieldglass with enterprise applications through REST APIs, selected web services, secure file exchange, and tenant-dependent notifications.
SAP Fieldglass integration options at a glance
SAP Fieldglass supports REST-oriented APIs for applicable processes, with availability determined by the tenant, module, and API entitlement. Existing enterprise integrations may also use SOAP-style web services, secure file transfer, batch processing, or selected notification mechanisms. OAuth 2.0 can apply to supported API services, while SFTP, certificates, API keys, or tenant-specific credentials may be required for other interfaces. Martini can consume Fieldglass APIs, process files, expose endpoints for supported callbacks, schedule incremental synchronization, transform workforce and procurement data, and route validation or delivery failures for retry and reconciliation.
| Integration point | Supported by SAP Fieldglass? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Read and update supported Workers, Work Orders, Suppliers, and other Fieldglass objects, and submit transactions such as Timesheets or Invoices where the applicable API supports those operations. | Martini can consume Fieldglass REST APIs from workflows, manage authentication configuration, transform payloads, apply business rules, and persist synchronization state. |
| SOAP APIs | Limited | Existing enterprise integrations may use Fieldglass web services or SOAP-style operations for applicable business objects. | Martini can consume supported SOAP services, map XML requests and responses, and apply service-specific error handling. Availability should be confirmed for the required tenant and object. |
| Webhooks / outbound callbacks | Limited | Selected Fieldglass processes may provide notification or event-style integrations, but universal webhook coverage across objects is not confirmed. | Martini can expose an API endpoint for supported callbacks and route notifications into workflows. Scheduled polling or file extracts can cover processes without callbacks. |
| Bulk / async / batch processing | Limited | Initial loads and recurring workforce, supplier, assignment, and transaction synchronization may use batch-oriented APIs, integration services, or file processing. | Martini can orchestrate batch submissions, track processing states and acknowledgments, handle rejected records, and control concurrency. |
| File / attachment APIs | Limited | Secure file exchange can support bulk worker or supplier loads, work-order imports, timesheet and invoice exchanges, and outbound extracts. | Martini can retrieve or receive files through the supported transfer arrangement, parse and validate them, transform records, and deliver results to APIs or databases. |
| Authentication | Yes | Supported API services may use OAuth 2.0 client credentials and scopes, while file and legacy web-service interfaces may use SFTP credentials, certificates, API keys, or tenant-specific credentials. | Martini can keep credentials and secrets in secure environment configuration and apply interface-specific authentication to API and workflow calls. |
| Database / analytics access | Not confirmed | Direct customer access to the SAP Fieldglass SaaS application database was not confirmed. Supported APIs, web services, files, or reporting exports should be used instead. | Martini can load supported extracts into a database or warehouse, but it should not depend on direct Fieldglass database connectivity. |
How SAP Fieldglass exposes data and business events
SAP Fieldglass REST APIs
SAP Fieldglass provides REST-oriented API capabilities for applicable processes, including supported workforce, supplier, work-order, and transaction operations. Resources and operations depend on the tenant, module, and API catalog entitlement.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the applicable Fieldglass API, retrieves pages or incremental changes, maps the response into a canonical model, applies validation and lifecycle rules, and writes the result to a target system while storing checkpoint and correlation data.
Implementation sequence
SAP Fieldglass SOAP services
Fieldglass has historically supported enterprise web-service integrations, including SOAP-style services in applicable areas. Current availability must be confirmed for the required business object and tenant, with REST preferred when SAP documents it as the current interface.
Martini implementation pattern
Martini implementation pattern: a workflow sends an authenticated SOAP request, transforms the XML response, distinguishes transport faults from business errors, and routes valid data to the target application or an internal reconciliation store.
Implementation sequence
SAP Fieldglass file exchange
Secure file exchange is an established Fieldglass integration pattern for bulk worker or supplier loads, work-order imports, timesheet and invoice exchanges, and outbound extracts. File layouts, schedules, and acknowledgments are tenant- and interface-specific.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow retrieves or receives files, validates naming and structure, parses the content, transforms each record, loads the target system, and records duplicate-file, acknowledgment, and rejection outcomes.
Implementation sequence
SAP Fieldglass notifications
Selected Fieldglass processes may provide event-style notifications or outbound callbacks, but universal webhook coverage is not confirmed. Callback availability and event scope must be verified for the tenant and process.
Martini implementation pattern
Martini implementation pattern: Martini exposes a controlled API for supported callbacks, validates the notification, retrieves the current Fieldglass object when necessary, and uses scheduled polling as a fallback where no callback exists.
Implementation sequence
SAP Fieldglass batch processing
Bulk and asynchronous processing may be delivered through file interfaces, integration services, or object-specific APIs rather than one universal bulk REST endpoint. Batch limits, status handling, and rejection behavior require confirmation.
Martini implementation pattern
Martini implementation pattern: a workflow partitions source data into approved batches, submits them with controlled concurrency, tracks asynchronous status or acknowledgments, and reconciles accepted and rejected records.
Implementation sequence
Common SAP Fieldglass integration patterns
Pattern 1: Synchronize workers to an HR platform
When to use this pattern
Use this pattern when SAP Fieldglass is the source for contingent-worker assignments and an HR platform such as SAP SuccessFactors needs current worker, organization, and assignment information.
Integration direction
Example Mapping
| SAP Fieldglass Field | Canonical Field | Target Field |
|---|---|---|
| Worker ID | externalWorkerId | personExternalId |
| Work Order ID | assignmentId | employmentAssignmentId |
| Assignment status | assignmentStatus | employmentStatus |
| Start date | assignmentStartDate | startDate |
Martini implementation pattern
A scheduled Martini workflow retrieves changed Workers and Work Orders using the supported incremental mechanism, validates required organization and cost-center values, maps lifecycle statuses, and upserts the target records. It stores source and target identifiers, uses an overlap window when necessary, and routes missing master data or target failures to retry and reconciliation handling.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Process approved Fieldglass transactions in SAP S/4HANA
When to use this pattern
Use this pattern when approved Work Orders, Statements of Work, Timesheets, or Invoices must enter SAP procurement and finance processes without duplicate postings.
Integration direction
Example Mapping
| SAP Fieldglass Field | Canonical Field | Target Field |
|---|---|---|
| Supplier ID | supplierExternalId | supplier |
| Company code | companyCode | companyCode |
| Currency | currencyCode | transactionCurrency |
| Invoice ID | sourceInvoiceId | referenceDocument |
Martini implementation pattern
Martini retrieves approved Fieldglass transactions, validates supplier, company-code, tax, currency, and cost-center data, transforms the payload for the target SAP interface, and submits it. Durable source identifiers and posting responses prevent duplicate writes, while transient API failures are retried and business rejections are routed for correction.
Martini capabilities used
- workflows
- API consumption
- data mapping
- validation
- business rules
- idempotency
- error handling
Pattern 3: Load Fieldglass files into a data warehouse
When to use this pattern
Use this pattern when Fieldglass outbound extracts are the approved source for reporting, workforce analytics, payroll preparation, or operational reconciliation.
Integration direction
Example Mapping
| SAP Fieldglass Field | Canonical Field | Target Field |
|---|---|---|
| Worker ID | workerId | worker_id |
| Work Order status | workOrderStatus | work_order_status |
| Timesheet hours | approvedHours | approved_hours |
| Invoice amount | invoiceAmount | invoice_amount |
Martini implementation pattern
A scheduled Martini workflow securely retrieves Fieldglass files, checks file identity and structure, parses and normalizes Workers, Suppliers, Work Orders, Timesheets, and Invoices, and writes them to database staging and curated tables. Duplicate-file detection, rejected-record quarantine, and source-to-target count reconciliation provide operational control.
Martini capabilities used
- workflows
- scheduling
- file processing
- data mapping
- SQL database integration
- validation
- reconciliation
Pattern 4: Drive service-management actions from assignment status
When to use this pattern
Use this pattern when worker onboarding, offboarding, access requests, or operational tasks in ServiceNow depend on SAP Fieldglass assignment and lifecycle changes.
Integration direction
Example Mapping
| SAP Fieldglass Field | Canonical Field | Target Field |
|---|---|---|
| Worker ID | workerId | u_external_worker_id |
| Work Order status | assignmentStatus | state |
| Assignment start date | startDate | planned_start_date |
| Assignment end date | endDate | planned_end_date |
Martini implementation pattern
Martini polls supported Fieldglass changes or receives selected notifications, translates status transitions into ServiceNow requests or tasks, validates worker and assignment identifiers, and applies routing rules for onboarding or offboarding. The workflow records correlation IDs and avoids reopening or duplicating tasks when the same status is observed again.
Martini capabilities used
- workflows
- API consumption
- scheduled synchronization
- data mapping
- business rules
- idempotency
- monitoring
Applications commonly integrated with SAP Fieldglass
SAP Fieldglass commonly participates in broader HR, procurement, finance, workforce, and service-management landscapes. The exact objects and direction depend on the customer’s tenant configuration, entitlements, and target-system processes; Martini can coordinate these exchanges without requiring a dedicated SAP Fieldglass connector.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP SuccessFactors | Synchronize external worker assignments, organizational information, and lifecycle changes with HR processes. | SAP Fieldglass → Martini → SAP SuccessFactors | Schedule incremental retrieval of Workers and Work Orders, validate organizational and cost-center data, map assignment structures to SuccessFactors payloads, and persist source and target identifiers for reconciliation. |
| SAP S/4HANA | Transfer approved Work Orders, Statements of Work, Timesheets, Invoices, Suppliers, and accounting information into procurement and finance processes. | SAP Fieldglass → Martini → SAP S/4HANA | Retrieve approved transactions, apply supplier, company-code, currency, tax, and cost-center rules, transform them for the target SAP interface, and retry transient posting failures without duplicating successful documents. |
| SAP Ariba | Coordinate supplier, procurement, and external-services processes where Fieldglass and Ariba are used in the same SAP landscape. | SAP Fieldglass → Martini → SAP Ariba | Exchange supported supplier and procurement attributes through tenant-approved APIs or files, normalize statuses, validate identifiers, and route rejected records to an operational exception flow. |
| SAP Concur | Exchange approved external-worker expenses or related financial information where expense processing is handled by Concur. | SAP Fieldglass → Martini → SAP Concur | Retrieve eligible financial transactions, apply approval and employee or supplier matching rules, map the results to the target interface, and record processing outcomes for status feedback. |
| Workday | Synchronize worker, organizational, supplier, or assignment information where Workday is the HR system of record. | Workday → Martini → SAP Fieldglass | Consume the available Workday and Fieldglass interfaces, map canonical worker and organization data, apply lifecycle rules, and use stable identifiers to prevent duplicate assignments. |
| ServiceNow | Create or update access, onboarding, offboarding, or service-management records from worker and assignment status changes. | SAP Fieldglass → Martini → ServiceNow | Poll or receive supported Fieldglass changes, translate lifecycle states into ServiceNow requests or tasks, apply routing rules, and send selected status updates back when the process requires it. |
| Oracle HCM Cloud | Synchronize contingent-worker and organizational data where Oracle HCM Cloud is the HR platform. | Oracle HCM Cloud → Martini → SAP Fieldglass | Orchestrate approved API or file exchanges, maintain cross-system identifiers, validate required organization values, and reconcile active, completed, or cancelled assignments. |
| Salesforce | Share supplier, engagement, or external-worker information with customer-facing and operational applications. | SAP Fieldglass → Martini → Salesforce | Expose or consume controlled APIs, map selected Fieldglass objects to Salesforce data structures, apply field-level validation, and isolate rejected records for review. |
How to build a SAP Fieldglass integration in Martini
Objective
Establish tenant-specific access to the Fieldglass interface and target systems while keeping credentials outside workflow definitions.
Instructions in Martini
- Confirm the Fieldglass API, SOAP, file-transfer, or callback interface required for the process
- Configure OAuth 2.0, SFTP, certificate, API-key, or other tenant-approved credentials
- Store secrets and environment-specific endpoints in secure configuration
- Apply least-privilege permissions for required objects and operations
Objective
Select an execution model that matches Fieldglass capabilities and the required data freshness.
Instructions in Martini
- Use a supported callback only for verified Fieldglass notification processes
- Use a scheduler for incremental API polling or file retrieval where callbacks are unavailable
- Define the synchronization window, overlap period, and checkpoint strategy
- Set concurrency and batch limits appropriate to tenant capacity
Objective
Acquire Workers, Suppliers, Work Orders, Statements of Work, Timesheets, Invoices, or other supported objects reliably.
Instructions in Martini
- Call the documented REST or SOAP operation, or retrieve the expected file
- Handle pagination, continuation tokens, batch status, or acknowledgment behavior as applicable
- Persist source identifiers and checkpoint state only after successful processing
- Capture correlation identifiers and source response details
Objective
Coordinate validation, transformation, target delivery, and operational state in a maintainable Martini workflow.
Instructions in Martini
- Separate transport failures from business validation failures
- Route each object through reusable workflow logic where processes overlap
- Apply conditional paths for approved, rejected, active, completed, and cancelled states
- Use controlled retries for transient service or network failures
Objective
Convert Fieldglass payloads and files into the canonical model required by downstream systems.
Instructions in Martini
- Map actual Fieldglass fields such as Worker ID, Work Order ID, Supplier ID, and Invoice ID
- Transform dates, currencies, statuses, amounts, and nested structures
- Preserve source identifiers and relevant unknown fields where practical
- Validate required target fields before submission
Objective
Enforce customer-specific controls before records are written to target applications.
Instructions in Martini
- Validate supplier, company-code, cost-center, tax, currency, and assignment relationships
- Maintain explicit mappings for Fieldglass lifecycle states and status reversals
- Check idempotency state before creating or posting transactions
- Send incomplete or rejected records to an operational exception path
Common SAP Fieldglass data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Workers | Represent contingent or external workers and their assignment-related information. | SAP SuccessFactors, Workday, Oracle HCM Cloud, ServiceNow | Martini retrieves or receives Workers through supported APIs or files, validates identifiers and organization data, maps lifecycle states, and stores synchronization checkpoints. |
| Job Postings | Represent requests or postings used to source external workers. | Supplier-management applications, procurement platforms, workforce applications | Martini maps posting details and statuses, applies routing or approval rules, and sends selected data to target applications through their supported APIs or files. |
| Work Orders | Define worker assignments, terms, dates, rates, and engagement status. | SAP SuccessFactors, SAP S/4HANA, Workday, ServiceNow | Martini uses stable Work Order identifiers for idempotency, maps dates and commercial fields, and reconciles active, completed, and cancelled states. |
| Statements of Work | Represent project- or service-based engagements, deliverables, milestones, and commercial terms. | SAP S/4HANA, SAP Ariba, procurement and finance applications | Martini validates supplier, currency, cost-center, and approval data before transforming Statements of Work for downstream procurement or finance processes. |
| Suppliers | Represent staffing firms or service providers participating in external workforce processes. | SAP Ariba, SAP S/4HANA, Workday, procurement applications | Martini normalizes supplier identifiers and status values, applies duplicate checks, and routes incomplete or rejected supplier data for correction. |
| Timesheets | Represent submitted and approved time associated with worker assignments. | SAP S/4HANA, payroll applications, SAP Concur, data warehouses | Martini retrieves approved Timesheets, validates assignment and period data, prevents duplicate submission, and records target processing results. |
Authentication and security considerations
Tenant-specific authentication
SAP Fieldglass authentication varies by interface and tenant. Supported API services may use OAuth 2.0 client credentials, access tokens, and scopes, while file and legacy web-service integrations may use SFTP credentials, SSH keys, certificates, API keys, or other tenant-provisioned credentials.
Least-privilege access
Limit API clients, integration users, suppliers, and file accounts to the objects and operations required by each workflow. Keep development, testing, and production credentials separate.
Secure configuration
Martini can store OAuth secrets, API credentials, certificates, and SFTP keys in secure environment configuration rather than workflow definitions. Use TLS-protected endpoints and protect callback APIs with appropriate authentication and authorization.
Operational considerations for SAP Fieldglass integrations
Limits and pagination
Confirm Fieldglass request limits, concurrency restrictions, payload sizes, batch limits, and the pagination or continuation model for each interface. Control parallelism and apply backoff for transient failures.
Idempotency and lifecycle states
Use durable Fieldglass identifiers and persist target identifiers and processing states so retries do not create duplicate Workers, Timesheets, Invoices, or other transactions. Map pending, approved, rejected, active, completed, and cancelled states explicitly.
Files and schema changes
Define file naming, encoding, headers, acknowledgments, rejection handling, duplicate-file detection, and retention. Treat tenant- and module-specific payloads as versioned contracts and test mappings against representative data.
Monitoring and reconciliation
Separate technical failures from business validation failures. Retry timeouts and temporary service errors, but route missing cost centers, invalid suppliers, duplicate transactions, and rejected approvals for operational review. Reconcile source and target counts and statuses periodically.
Why use Martini instead of scripts or point-to-point integrations?
Centralized orchestration
Martini coordinates SAP Fieldglass APIs, SOAP services, files, schedules, callbacks, target applications, and databases in workflows rather than spreading logic across isolated scripts.
Reusable transformation and rules
Mappings, validations, lifecycle rules, identifier handling, and error paths can be maintained as reusable integration assets. This is useful when Fieldglass data must be delivered to multiple HR, procurement, finance, or service-management systems.
Operational control
Martini supports controlled retries, checkpointing, idempotency, exception routing, logging, and reconciliation. It can also expose a governed API façade for downstream consumers, reducing direct coupling to tenant-specific Fieldglass interfaces.
Frequently asked questions
SAP Fieldglass can be integrated through REST-oriented APIs for applicable processes, selected SOAP or web-service interfaces, secure file exchange, batch processing, and tenant-dependent notification mechanisms. The appropriate method depends on the Fieldglass module, tenant entitlement, object, and interface requirements.
Yes. Martini can consume supported SAP Fieldglass REST APIs and SOAP services, process files exchanged through an approved transfer arrangement, schedule incremental synchronization, and expose an API endpoint for supported callbacks or notifications. Exact resources and authentication must be confirmed for the customer tenant.
No. A dedicated SAP Fieldglass connector is not required. Martini can integrate using Fieldglass's confirmed native mechanisms, including REST APIs, applicable SOAP services, secure file exchange, scheduled polling, and selected callbacks or notifications.
Lonti does not charge an additional per-connector or per-vendor fee to integrate SAP Fieldglass. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from SAP, cloud infrastructure, SFTP providers, or other third-party systems based on subscriptions, usage, and deployment model.
Use REST APIs where SAP documents the required Fieldglass process and the tenant has the appropriate entitlement. Use secure file exchange or batch services for approved bulk workloads, and consider SOAP for existing or specifically supported services. Confirm object-level support, limits, and authentication before implementation.
Notification or callback mechanisms may be available for selected Fieldglass processes, but universal webhook coverage is not confirmed. Martini can receive supported callbacks through an exposed API and use scheduled API polling or file extracts for processes without an approved event mechanism.
Use supported modification timestamps, status filters, continuation tokens, or file schedules for incremental processing. Store the last successful checkpoint and use stable identifiers such as Worker ID, Work Order ID, Timesheet ID, or Invoice ID as idempotency keys. Overlap windows and reconciliation can address uncertain change tracking.
Yes. Martini can expose a controlled API that retrieves or presents approved Fieldglass data without requiring downstream applications to access Fieldglass directly. The façade can apply authorization, field filtering, transformation, caching or orchestration logic, and consistent error handling.
Related Martini documentation
API Integration
Data Processing
Integrate SAP Fieldglass with Martini
Connect SAP Fieldglass to HR, procurement, finance, workforce, and service-management applications using governed APIs, workflows, mappings, secure file processing, and operational controls.