Six blocks of five minutes. You draw three lanes, register two data handlers on live tables, compose three screens, write four criteria, assign roles and publish version 1.
The system is connected and its objects are registered in the catalog: for SAP, the equipment and master warranty tables and the sales order tables; for Oracle Fusion, the installed base and service contract resources and the order lines. Write-back for the service order interface has had its test write. You have the configurator role for a new app and the process owner is with you for the preview.
Everything else happens in the studio. The times below are from the recorded walkthrough on the showcase estate.
Create the app, choose the process way of building, and draw three lanes: customer or agent, service agent, system. Place a start node in the first lane, a screen box in the second, a decision after it, and a write-back box in the third. Five boxes, four arrows. The validator shows green when every box has a way in and a way out.
| Lanes | Customer or agent · Service agent · System |
| Boxes | Start → S01 Lookup and claim → Covered? → S03 Decide → Service order (write-back) |
| Validator | 5 nodes · 5 arrows · entry and exit found · OK |
From the catalog, pick the warranty object; the studio proposes the handler with the equipment record joined (in SAP, BGMK and BGMS with EQUI's warranty dates; in Fusion, serviceContracts with installedBaseAssets). Pick the sales order line object for the delivering order. Each handler shows its rows the moment it is registered; you pick a serial you know and see its dates. Two handlers, seven minutes, most of it looking at the rows.
| dh_warranty | table · BGMK · BGMS · EQUI (GWLDT, GWLEN, SERNR, KUNDE) · read · 31,204 rows |
| dh_so_line | table · VBAK · VBAP · VBEP · read · filter by material and customer |
| Test | serial CX4-0921 → warranty_end 2027-11-30 · customer 10023 · order 0000512345/000010 |
Draft S01 from dh_warranty: a serial field with scan, a lookup button, the coverage card (product, customer, start, end, type, earlier claims), a fault type dropdown, a description, a photo upload and a submit button. Draft S02 as the coverage detail, with the sales order line from dh_so_line. Draft S03 as the decision screen: estimate, decision options, note, approve. The studio lays out desktop and mobile; you rename two labels and move the photos below the fault.
| S01 Lookup and claim | txt_serial (scan) · btn_lookup · card_coverage · dd_fault · txt_desc · up_photos · btn_submit |
| S02 Coverage detail | grid: warranty terms · so line 0000512345/000010 · covered types |
| S03 Decide | num_estimate · dd_decision · txt_note · btn_approve (enabled when note present) |
The start criterion: a claim submitted on S01. The decision after S01: covered when the fault date is on or before the warranty end and the fault type is in the covered types and the estimate is below the band; above band otherwise. The arrow into the write-back: approved. The editor shows 'covered' for CX4-0921 and 'assess' when you change the estimate to 900. Four criteria in five minutes, each tested before it is saved.
# covered? dh_warranty.warranty_end >= dt_fault.value and dd_fault.value in dh_warranty.covered_types and num_estimate.value < glob.claim_band # 500 → covered for CX4-0921 · assess at estimate 900 # write-back arrow app.decision == 'approve' and txt_note.value.length > 10
Attach the service agent role to the second lane and pick two agents from the directory; the system role is the SAP connector. Run the preview as an agent: scan CX4-0921, pick a fault, upload a photo, submit; the decision node reports 'covered'; the write-back is shown as it would be sent, held. Run it again with a 900 estimate and see the assess path. The process owner nods.
| S01 | CX4-0921 · sensor fault · 1 photo · submitted 10:41:05 |
| Decision | covered (band 500, estimate 180) |
| Write-back (held) | BAPI_ALM_ORDER_MAINTAIN · equipment 10004471 · would create service order |
| Log | 3 steps · 2 reads · 1 held write · version draft |
Publish with the note 'v1: lookup, coverage decision, service order'. The process owner approves the gate, write-back for the service order interface is already on, and the first real claim runs: a serial in, 'covered' out, a service order number back from SAP, and a log entry with the acknowledgement. Thirty minutes.
| Start | 10:58:12 · agent L. Martin · serial CX4-0921 |
| Decision | covered · band 500 |
| Write-back | BAPI_ALM_ORDER_MAINTAIN · service order 4000123 · RETURN S · 10:58:14 |
| Board | 1 open · 0 escalations |
The catalogue entry estimates five working days.
Bring one 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.
