Turns a service request into a dispatched visit: the dispatcher picks the engineer and parts, the engineer closes the job on mobile, and the service order is confirmed for billing.
Tables are read in place through the SAP connector, using released read interfaces; changed rows arrive through change capture where the basis team allows it. The rows stay in SAP.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Sales order line | VBAK · VBAP · VBEP | VBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer) · VBAP.MATNR (material) | live; change capture where enabled |
| Warranty | BGMK · BGMS (master warranties) · EQUI.GWLEN | EQUI.EQUNR (equipment) · EQUI.SERNR (serial) · EQUI.GWLDT (warranty start) · EQUI.GWLEN (warranty end) | live; change capture where enabled |
| Customer master | KNA1 · KNB1 · KNVV | KNA1.KUNNR (id) · KNA1.NAME1 (name) · KNA1.LAND1 (country) · KNVV.VKORG (sales org) | live; change capture where enabled |
| Employee | PA0001 · PA0002 (SAP HCM) or SuccessFactors | PA0001.PERNR (id) · PA0002.VORNA + NACHN (name) · PA0001.ORGEH (org unit) · PA0001.PLANS (position) | live; change capture where enabled |
In plain words: A customer submits S01 on the portal screen, or the service desk logs a request from a call or from the service case in the CRM.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
A customer submits S01 on the portal screen, or the service desk logs a request from a call or from the service case in the CRM. The instance then reads its rows from S/4HANA through the handlers above.
Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and the app records both beside the decision.
| Object | What changes | Interface |
|---|---|---|
| Sales order line | service order created with the visit, parts and labour lines; confirmed quantities and completion written when the engineer closes the job | BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2 |
Each write stores the identifier S/4HANA returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
SAP roles are mapped to Lima access policies once. A buyer who sees purchasing organisation 1000 in SAP sees the same rows in the app.
On SAP ECC the same objects live in the classic tables named beside each row; MATDOC becomes MKPF and MSEG, ACDOCA becomes BKPF and BSEG. The BAPIs are the same.
| Object | On S/4HANA | On SAP ECC |
|---|---|---|
| Sales order line | VBAK · VBAP · VBEP | same tables |
| Warranty | BGMK · BGMS (master warranties) · EQUI.GWLEN | same tables |
| Customer master | KNA1 · KNB1 · KNVV | same tables |
| Employee | PA0001 · PA0002 (SAP HCM) or SuccessFactors | same infotypes |
The screens read through handlers that leave the rows in S/4HANA. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.
The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.
