Modern field operations generate data constantly - inspections completed, work orders closed, measurements recorded, parts used. The challenge is rarely capturing that data; it's getting it into SAP reliably, in the right format, without building a custom integration from scratch every time. TrueContext solves that problem through a flexible, API-driven integration model that works with SAP S/4HANA EAM, SAP Field Service Management (FSM), and the OData services that underpin both.
This article walks through how TrueContext connects to SAP, the core use cases it supports, and how middleware fits into the picture when your environment calls for it.
How TrueContext Integrations Work
TrueContext communicates with back-office systems through two mechanisms: HTTP GET (pulling data in) and HTTP POST (pushing data out). Between those two, a templating layer handles the transformation.
HTTP GET - Data Sources TrueContext uses HTTP GET requests to pull reference data from SAP into forms before and during field work. Equipment records, functional locations, work order lists, and measurement points can all be retrieved from SAP's OData endpoints and surfaced as dropdowns, auto-populated fields, or filterable lists inside the mobile form. Data syncs on a configurable schedule so technicians have what they need even when connectivity is limited.
FreeMarker Templates - Data Transformation When a form is submitted, TrueContext uses FreeMarker templates to shape the raw submission data into exactly the JSON payload that SAP expects. FreeMarker gives you fine-grained control: pulling specific field values, applying conditional logic, formatting dates to ISO 8601, building arrays from repeating sections, and handling edge cases like attachment file extension validation. This is where the integration logic lives - separate from the form design and the back-end system.
HTTP POST - Data Destinations Once the FreeMarker template has rendered the payload, TrueContext fires an HTTP POST to the appropriate SAP OData endpoint, creating or updating records in real time. Multiple destinations can trigger from a single form submission - for example, updating a work order status, writing inspection results to a measurement document, and attaching a photo, all from one completed form.
Core Use Cases
Work Order Lifecycle Management
TrueContext's most common SAP integration pattern is straightforward: field technicians receive work assignments in a mobile app, execute the work, and close out the record - all without touching a desktop.
With SAP PM or S/4HANA EAM, this means:
-
Pulling open work orders assigned to a technician or crew via HTTP GET against the MaintenanceOrder or MaintenanceNotification OData entities
-
Updating work order status on arrival and completion via HTTP POST (e.g., transitioning from REL to TECO)
-
Writing labor confirmations - actual start/end times and hours worked - back to the work order
-
Attaching documents and photos captured in the field directly to the SAP object
FreeMarker handles the status mapping, date formatting, and conditional inclusion of fields based on what the technician actually filled in. If a follow-up notification needs to be created when a defect is flagged, a second destination template handles that automatically from the same form submission.
Inspection Results and Measurement Documents
For asset-intensive industries - utilities, oil and gas, manufacturing - inspections are the backbone of SAP PM. TrueContext can write directly to SAP inspection lots and measurement documents, closing the loop between physical inspection and the SAP record.
A typical flow looks like this: a technician opens a form pre-populated with the equipment tag and measuring point details (pulled via HTTP GET). They record readings, select pass/fail responses, and add photos where needed. On submission, FreeMarker maps each answer to the corresponding SAP characteristic or inspection result field, including setting an Action Required flag when a response falls outside acceptable range. The payload is POSTed to the SAP OData inspection results endpoint.
For multi-point inspections - where a single form covers dozens of measuring points - FreeMarker's array-building capability iterates over repeating sections and assembles the full results payload in a single request.
Field Service Dispatch and Completion
SAP Field Service Management (FSM) operates as a cloud-native layer above S/4HANA, handling scheduling, dispatch, and technician-facing workflows. TrueContext integrates with FSM by consuming activity and service order data via HTTP GET, giving technicians the full job context in the mobile app before they arrive on site.
On completion, the TrueContext form submission writes back to FSM via HTTP POST - updating the service activity status, recording time and materials, and triggering any downstream workflows (warranty registration, customer sign-off, parts consumption). Because TrueContext works offline, technicians can complete forms in areas without connectivity and sync when they're back in range, with no data loss.
For organisations already running the SAP FSM mobile app, TrueContext can be launched directly from within it using SAP FSM's native Launch External App feature. A button placed on the activity or work order detail screen passes live context - activity ID, equipment, customer - directly to TrueContext via a deep link, opening the right form pre-populated and ready to complete. This App2App pattern means technicians don't need to switch between apps manually or re-enter data that SAP already holds, and the completed TrueContext submission writes back to the FSM record automatically on close.
When You Need Middleware
TrueContext integrates directly with SAP's OData services in many scenarios, particularly when SAP Gateway is exposed to the network and authentication is straightforward (basic auth or OAuth 2.0). In those cases, TrueContext acts as the integration layer on its own.
However, some SAP environments introduce complexity that calls for a middleware layer between TrueContext and SAP:
SAP Business Technology Platform (BTP) is the natural fit for SAP-first organisations. BTP Integration Suite sits natively inside the SAP ecosystem, which means it can enforce business rules, handle protocol translation, and orchestrate multi-step processes before data lands in your ERP - without any custom code on the SAP side. If your team is already using BTP for other integrations, adding TrueContext is straightforward: TrueContext POSTs to a BTP endpoint, and BTP takes it from there.
MuleSoft comes up frequently in large enterprises that have already standardised on API-led connectivity. In most of these environments, SAP is already abstracted behind a MuleSoft API layer - TrueContext just calls those APIs like any other consumer. Authentication, rate limiting, and routing are all handled by MuleSoft; TrueContext doesn't need to know what's underneath.
Azure Integration Services (Logic Apps, API Management) is the right conversation for organisations running SAP on Azure or in a hybrid Microsoft environment. It handles OAuth token management and gives you a clean audit trail for every submission.
Boomi and other iPaaS platforms follow the same pattern: TrueContext POSTs to a Boomi endpoint, Boomi routes to SAP. If your team is already running Boomi for other workflows, it's usually the path of least resistance.
In each case, TrueContext's job is the same - capture the data, shape it with FreeMarker, deliver a clean HTTP POST. What changes is where that POST lands.
What This Looks Like in Practice
A field technician starts their shift and opens TrueContext. Their work orders - pulled from SAP S/4HANA overnight - are already waiting, filtered to their assigned location and sorted by priority. They tap into a work order, review the asset details and task instructions, and head to site.
During the inspection, they record measurements, select outcomes, photograph any defects, and flag items requiring follow-up. The form guides them through every step, enforcing required fields and validating inputs before they can submit.
On submission, TrueContext fires multiple POST requests to SAP in sequence: the work order status updates to complete, the inspection results land in the measurement document, and a follow-up notification is created for the flagged defect. Each is driven by a separate FreeMarker template hitting the appropriate OData endpoint.
The SAP planner sees the completed records within seconds. No paper, no re-keying, no delay.
TIP: Want to minimize app fatigue? TrueContext can launch directly out of SAP FSM Mobile with an app-to-app call and sends the user back once the work is complete, creating a seamless mobile experience for the technician.
Getting Started
Every SAP environment is different - custom OData services, specific authorization models, multi-system landscapes. TrueContext's integration approach is built to accommodate that variability: the FreeMarker template layer means you can match any payload structure SAP expects, and the HTTP GET/POST model works with or without middleware in the path.
If you're evaluating a TrueContext-to-SAP integration, here are the three steps to take:
-
Map the OData services your SAP instance exposes
-
Confirm the authentication method
-
Identify the two or three core workflows you want to automate first
From there, the integration builds quickly.
Reach out to the TrueContext team to discuss your SAP environment and walk through what a phased integration could look like for your operations.
------------------------------
Ian Chamberlain
Solutions Architect
TrueContext
------------------------------