Asset Management (EAM)
Connect IBM Maximo and field apps straight to SAP
Link IBM Maximo, any EAM or CMMS, or your field-service apps to SAP ECC 6 or S/4HANA for live spare-parts stock, reservations, requisitions, notifications and work orders. CGR SAP Connector runs inside SAP, so there is no middleware to buy, host or map.
Each call runs under an SAP user · whitelisted objects only · logged in SAP
Illustrative flow. Objects and steps depend on your process.
CGR SAP Connector runs in production at

What it does
Maintenance and SAP, working from the same data
When the field and the back office are not connected, repairs wait on parts nobody checked and costs reach SAP late. The connector puts SAP stock and SAP postings one REST call away.
Check SAP stock before a job is assigned
Before a technician is sent out, the EAM system or field app reads unrestricted stock by plant and storage location straight from SAP. Planners know whether parts are on hand, and a stock-out triggers a requisition instead of a wasted trip.
Reservations and requisitions posted in SAP
When Maximo runs the work orders, it creates reservations and purchase requisitions in SAP. SAP returns the document number, or the exact reason it could not post, in the same call.
Notifications from the field
When SAP PM is your system of record, field apps create maintenance notifications through standard SAP BAPIs, so a fault reported on site is in SAP straight away.
Work orders kept current
Field apps read and update maintenance orders in SAP PM: equipment, functional location, operations and status. Each update goes through SAP’s own validation.
IBM Maximo
Maximo calls SAP directly, through its own integration framework
For Maximo, the integration framework’s publish and invocation channels call CGR’s endpoints directly. No adapter server or integration platform sits in between.
Maximo two-pager
A short technical overview of the Maximo and SAP flows is available on request. Email sales@cgrsoft.com.
EquipmentEquipment and functional locations, read from SAP PMNotificationsCreated and updated through standard BAPIsWork ordersMaintenance orders read and updated in SAPStockUnrestricted stock by plant and storage locationReservationsParts reserved against the job in SAPRequisitionsPurchase requisitions raised when stock is shortAny EAM, CMMS, field-service app or IoT platform that can call a REST API and read JSON can use the same SAP endpoints.
Governance
Security that stays inside SAP
Whitelisted objects only
An administrator approves each SAP PM table, BAPI or report by name. No ABAP development is needed to expose them.
SAP authorizations apply
Every call runs as an SAP user and passes that user’s SAP authorizations. Connect through REST endpoints, or through OData with OAuth 2.0.
Every update logged
Every call from a field tool is logged in SAP: who called, which object, when, and the result. Your SAP team reviews it in the connector’s monitor.
How it compares
CGR SAP Connector next to an adapter plus middleware
| Feature | CGR SAP Connector | Adapter plus middleware |
|---|---|---|
| Architecture | REST call from Maximo’s integration framework or any app into an add-on inside SAP | Adapter plus PI/PO, Integration Suite or another integration server |
| Setup | Install in hours; first working integration in days to a week | Middleware set up and mappings built before the first flow |
| What it reaches | Standard BAPIs and your own function modules, as they are | Re-mapped in the middleware |
| Response | Real time, per call | Often queued or scheduled |
| Governance | Every call logged in SAP | Spread across middleware logs |
| Pricing model | Flat per SAP production system | Middleware licence and servers, plus adapter costs |
Comparison reflects typical setups as of November 2026; individual offerings vary.
AI for maintenance
Let planners ask SAP in plain language
With CGR MCP Server for SAP, a planner asks their AI assistant about equipment and orders, and the answer comes from live SAP PM data, under their own SAP user.
Maintenance
Tested end to end“Which maintenance orders are open for this equipment?”
List notifications and work orders; create a notification when something breaks.
How do we make sure technicians’ updates can’t compromise SAP security?
Only whitelisted objects are reachable, every call runs with the SAP user’s own authorizations, and every update is logged in SAP with the user, object and result.
Does a field app need middleware mapping or custom ABAP code?
No. The app calls whitelisted SAP objects over REST and gets JSON back. If a flow needs custom SAP logic, an existing or new function module is exposed as it is.
Which SAP systems are supported?
Any SAP ECC 6 release and any S/4HANA release, on-premise, in private cloud or with RISE. S/4HANA Public Cloud is not supported. The connector is a native ABAP add-on in its own /CGR/ namespace, installed by your Basis team via SAINT.
Can we try it before we buy?
Yes. The 90-day free trial runs in your own SAP system, and the add-on can be removed through SAINT.
AI in SAP
Want your team to ask SAP directly?
See CGR MCP Server for SAP: any MCP-capable AI assistant, working in SAP under each user’s own SAP user.
Give planners live SAP stock and parts
And get maintenance costs into SAP the day they happen. See the connector API in a live SAP system, then try it in yours.