Looks up a serial number, shows the coverage from the warranty and the sale, decides the claim and creates the service order for the repair or replacement.
Today a service agent copies a serial number from an email into the ERP, opens the equipment record, then opens the sales order to find the delivery date, and writes the claim in the service desk tool. The customer calls twice to ask what was decided.
A service agent, or the customer on the portal screen, enters or scans a serial number. Within seconds the app shows the product, the customer, the sales order line that delivered the unit, the warranty start and end dates, the warranty type and every earlier claim on that serial. The agent records the fault with photos and submits the claim; the app checks the fault date against the warranty end and the fault type against what the warranty covers, and routes the claim to the assessor or approves it by rule when it is covered and below the band. On approval the app creates the service order in the ERP through the released interface, informs the customer of the appointment, and opens a return order when the unit has to come back.
| Lane | Does |
|---|---|
| Service agent | looks up the serial, records the fault, submits the claim |
| Customer | reports the fault on the portal screen, uploads photos, sees the decision and the appointment |
| Warranty assessor | decides covered repair, replacement, goodwill or chargeable |
| Service planner | creates the service order, assigns the engineer and the parts, or books the return |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Serial lookup | serial number field with barcode scan on the mobile screen; coverage card: product, customer, sale date, warranty start and end, type, earlier claims; fault description, fault type, photos; submit claim button |
| S02 Coverage detail | warranty terms and what the type covers, the sales order line that delivered the unit, the customer's block status and terms; covered or outside-coverage indicator with the reason |
| S03 Customer portal | portal screen: report a fault by serial, upload photos, see the claim status, the decision and the service appointment; accept a repair quote |
| S04 Claim decision | assessor options: covered repair, replacement, goodwill with amount, chargeable with quote; note; approve or decline with reason |
| S05 Service order | service order type, priority, engineer, parts, visit date; return order for a unit that comes back; order number returned from the ERP |
| S06 Board | claims by status, age and cost; share covered; goodwill value per month; time from serial entry to service order |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Warranty | the warranty attached to the serial: equipment, start, end, type and customer, read with the equipment record it belongs to | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Customer master | the account that holds the unit: contact, block status, terms | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Sales order line | the sales order line that delivered the unit: date, quantity, value | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Return order | the return order when the unit comes back for repair or replacement | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Quotation | the repair quotation for a fault outside coverage | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Object | What changes |
|---|---|
| Warranty | claim decision recorded against the warranty of the serial; a service order created through the service order interface for a covered repair or replacement, with fault, priority and engineer |
| Return order | return order created with the serial and reason code when the unit comes back |
| Quotation | repair quotation created for a chargeable fault and sent to the customer for acceptance |
Start: A service agent or a customer enters a serial number and a fault description on S01.
| Step | Moves when |
|---|---|
| Serial entered | the serial matches an equipment record; the coverage card appears within seconds |
| Fault recorded | fault type, fault date and at least 1 photo present; claim submitted |
| Coverage checked | fault date on or before the warranty end and fault type inside the warranty type: covered; otherwise the assessor decides |
| Claim decided | covered and below 500: approved by rule; above 500, goodwill or chargeable: the assessor decides; goodwill above 1,000 goes to the service manager |
| Service order created | order number stored; customer sees the appointment on the portal; return order opened when the unit comes back |
| Closed | engineer confirms the order; claim cost recorded against the warranty |
| Component | Trigger → action → outcome |
|---|---|
| fld_serial | on enter or scan → read the warranty, the equipment record and the sales order line for the serial → show the coverage card and enable the claim fields |
| btn_submit_claim | on click → compare the fault date with the warranty end and the fault type with the warranty type → approve by rule when covered and below 500, otherwise route to the assessor and start the 1-day clock |
| dd_decision | on change → show the fields the option needs: service type, replacement material, goodwill amount or quote → require a note for goodwill and chargeable |
| btn_create_order | on click → call the service order interface with the equipment, fault, priority and engineer → store the order number, notify the customer and the engineer, close the claim |
| Step | Time limit and escalation |
|---|---|
| Claim assessment | 1 working day, then the service manager is copied |
| Service order creation | 4 working hours after approval, then the service planner is reminded |
| Customer information | the decision reaches the customer within 1 hour of approval; a delay flags the claim on the board |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 09:05 Lena, a service agent in Lyon, scanned the serial of a compressor that a customer had reported at 08:50 on the portal screen. The coverage card showed 14 months left on a 36-month warranty, the sales order line from March of the previous year and one earlier claim for a sensor. She submitted the claim with the customer's 2 photos at 09:12, the assessor approved a covered repair at 10:30, and the service order appeared in SAP a minute later with an engineer visit on Thursday. The customer saw the appointment on the portal before lunch, and the board showed the service manager 41 open claims with their age and cost.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Warranty read from BGMK · BGMS (master warranties) · EQUI.GWLEN; also on SAP ECC.
Open the S/4HANA page →Warranty read from Service Contracts REST: serviceContracts · installedBaseAssets; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Warranty read from Asset · Entitlement; CRM.
Open the Salesforce page →Warranty read from CONFORMED.WARRANTY; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 5 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Salesforce, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.