What it can read on day one.
13 verified mappings for the S/4 objects field service actually touches, so the first screen starts from something that already works rather than a blank page and a metadata document.
- 13
- curated mappings
- 296
- mapped fields
- 9
- carry their child collections
| Object | What the mapping covers | Fields | Child lists |
|---|---|---|---|
| Billing document (invoice) snapshot | Header view of an S/4 Billing Document (invoice / credit memo): identity & billing type, sales-org structure, sold-to/payer, billing & accounting dates, net/tax/gross amounts and currency, payment terms, the posted FI document, and the overall billing/posting/clearing status. | 25 | 1 |
| Business partner snapshot | Header view of an S/4 Business Partner (the unified customer/supplier master): identity & category, organization/person names, search terms, title & language, industry & legal form, plus the customer/supplier role flags and central block. | 25 | 1 |
| Equipment warranty | Warranty assignments of an equipment from the standard S/4 Equipment API (API_EQUIPMENT, entity EquipmentWarranty): one row per equipment / warranty type with the assigned master warranty and the warranty validity window, plus the hierarchy inheritance flags. | 7 | — |
| Equipment snapshot | Master-data view of an S/4 Equipment (technical object): identity, manufacturer, physical attributes, validity, maintenance structure, on-site address and lifecycle status. | 31 | — |
| Maintenance Order snapshot | Header view of an S/4 Maintenance Order (EAM work order): identity & order type, description, the reference technical object (equipment / functional location), planning & maintenance plant, main work center, planner group, priority & activity type, the linked notification, basic scheduling dates, responsibility and (derived) cost assignment & status — plus the operation-component (material) collection. | 26 | 1 |
| Material document (goods movement) | An S/4 material document — the posted record of a goods movement (receipt, issue, transfer, cancellation) from the standard Material Documents API (API_MATERIAL_DOCUMENT_SRV): posting/document dates, transaction and movement codes, creator and reference, plus an Items collection with material, plant, storage location, batch, movement type, quantities and the issuing/receiving side of transfers. | 8 | 1 |
| Material stock (live) | Current warehouse stock of a material from the standard S/4 Material Stock API (API_MATERIAL_STOCK_SRV, account-assignment model): one row per material / plant / storage location / batch / stock-type segment, with the special-stock assignment (sales order, project, supplier, customer) and the quantity in the material's base unit. | 13 | — |
| Measuring Point snapshot | Header view of an S/4 Plant Maintenance / EAM Measuring Point (the V4/RAP API_MEASURINGPOINT service): identity & description, measuring-point category, the reference technical object (equipment / functional location), counter vs. | 25 | — |
| Notification snapshot | Header view of an S/4 Maintenance Notification (EAM): the report of a malfunction/defect on a technical object — identity & type, priority, malfunction & required dates, reference object, responsibility, plant/work-center assignment and processing status, plus item-level object-part / damage coding. | 22 | 1 |
| Sales quotation snapshot | Header view of an S/4 Sales Quotation (presales document): identity & sales-org structure, sold-to customer, document/validity dates, net value, terms and the overall processing/approval/credit status. | 29 | 1 |
| Service Contract snapshot | Header view of an S/4 Service Contract (Service Management, the V4/RAP API_SERVICECONTRACT): identity & transaction type, sold-to / ship-to / bill-to / payer parties, contact and responsible employee, sales & service organization, contract start/end validity, currency & payment terms/method, customer PO reference, lifecycle / billing status and net/tax/gross value, plus item (with item-level validity & response/service profiles) and partner collections. | 29 | 2 |
| Service Order snapshot | Header view of an S/4 Service Order (Service Management, the V4/RAP successor to the deprecated V2 API_SERVICE_ORDER_SRV): identity & transaction type, the sold-to / ship-to / payer parties and responsible employee, sales & service organization, requested service dates, priority, currency & payment terms, lifecycle / billing status and net/tax/gross value, plus an item collection (product, quantity, plant, item category, value). | 29 | 1 |
| Service Quotation snapshot | Header view of an S/4 Service Quotation (Service Management, the V4/RAP API_SERVICEQUOTATION — the CRM/service quotation, distinct from the SD sales quotation): identity & transaction type, sold-to / ship-to parties, contact and responsible employee, sales & service organization, requested-service and validity dates, priority, currency & payment terms, lifecycle / rejection status and net/tax/gross value, plus item and partner collections. | 27 | 2 |
This table is generated from the mappings the engine actually ships. It cannot describe a mapping that is not there, and it cannot omit one that is.
And everything that is not on this list
The curated set is a head start, not a boundary. The engine discovers what your system exposes — services, entity sets, fields, value helps, and which fields a write actually requires — so any OData entity your S/4 publishes can be read, filtered and put on a screen without one of these mappings existing first.
What a curated mapping buys you is the judgement: which fields matter, what they are called in plain language, how the child lists hang off the header, and the awkward details of key and date formatting for that specific service. That is the part worth not rediscovering.
A mapping — ours or one your team wrote — can be validated against the live service, which catches a broken binding before your users find it.
Need an object that is not on the list?
Tell us which one. If it is exposed by your system, it is already readable — and if it deserves a curated mapping, that is a conversation worth having.