App catalogue Logistics and warehouse

Warranty check and claim

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Serial lookupscreenS02 Coverage detailscreenS03 Customer portalscreenS04 Claim decisionscreenS05 Service orderscreendh_warrantyWarrantydh_customerCustomer masterdh_soSales order linedh_return_Return orderdh_quoteQuotationS/4HANABGMK · BGMSS/4HANAKNA1 · KNB1 · KNVVS/4HANAVBAK · VBAP · VBEPS/4HANAVBAK · VBAPS/4HANAVBAK · VBAProws stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
5 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Service agentlooks up the serial, records the fault, submits the claim
Customerreports the fault on the portal screen, uploads photos, sees the decision and the appointment
Warranty assessordecides covered repair, replacement, goodwill or chargeable
Service plannercreates the service order, assigns the engineer and the parts, or books the return
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Serial lookupserial 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 detailwarranty 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 portalportal screen: report a fault by serial, upload photos, see the claim status, the decision and the service appointment; accept a repair quote
S04 Claim decisionassessor options: covered repair, replacement, goodwill with amount, chargeable with quote; note; approve or decline with reason
S05 Service orderservice order type, priority, engineer, parts, visit date; return order for a unit that comes back; order number returned from the ERP
S06 Boardclaims by status, age and cost; share covered; goodwill value per month; time from serial entry to service order
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Warrantythe warranty attached to the serial: equipment, start, end, type and customer, read with the equipment record it belongs toS/4HANA · Oracle Fusion · Salesforce · Snowflake
Customer masterthe account that holds the unit: contact, block status, termsS/4HANA · Oracle Fusion · Salesforce · Snowflake
Sales order linethe sales order line that delivered the unit: date, quantity, valueS/4HANA · Oracle Fusion · Salesforce · Snowflake
Return orderthe return order when the unit comes back for repair or replacementS/4HANA · Oracle Fusion · Salesforce · Snowflake
Quotationthe repair quotation for a fault outside coverageS/4HANA · Oracle Fusion · Salesforce · Snowflake

Written back

ObjectWhat changes
Warrantyclaim 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 orderreturn order created with the serial and reason code when the unit comes back
Quotationrepair quotation created for a chargeable fault and sent to the customer for acceptance
The flow

From the trigger to the last write

THE FLOW · WARRANTY CHECK AND CLAIM1Serial enteredthe serial matches anequipment record; thecoverage card appearswithin seconds2Fault recordedfault type, faultdate and at least 1photo present; claimsubmitted3Coveragecheckedfault date on orbefore the warrantyend and fault typeinside the warrantytype: covered;otherwise theassessor decides4Claim decidedcovered and below500: approved byrule; above 500,goodwill orchargeable: theassessor decides;goodwill above 1,000goes to the servicemanager5Service ordercreatedorder number stored;customer sees theappointment on theportal; return orderopened when the unitcomes back6Closedengineer confirms theorder; claim costrecorded against thewarranty
Each step and the criterion that moves it.

Start: A service agent or a customer enters a serial number and a fault description on S01.

StepMoves when
Serial enteredthe serial matches an equipment record; the coverage card appears within seconds
Fault recordedfault type, fault date and at least 1 photo present; claim submitted
Coverage checkedfault date on or before the warranty end and fault type inside the warranty type: covered; otherwise the assessor decides
Claim decidedcovered 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 createdorder number stored; customer sees the appointment on the portal; return order opened when the unit comes back
Closedengineer confirms the order; claim cost recorded against the warranty
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
fld_serialon 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_claimon 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_decisionon change → show the fields the option needs: service type, replacement material, goodwill amount or quote → require a note for goodwill and chargeable
btn_create_orderon 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

Clocks

StepTime limit and escalation
Claim assessment1 working day, then the service manager is copied
Service order creation4 working hours after approval, then the service planner is reminded
Customer informationthe decision reaches the customer within 1 hour of approval; a delay flags the claim on the board

Measures

claims decided within 1 dayshare of claims covered by the warrantygoodwill value per monthtime from serial entry to service orderrepeat claims per serial
A day with the app

Illustrative

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.

illustrative scenario · Warranty check and claim
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Serial numberThe identifier of one physical unit of a product; the equipment record in the ERP carries it.
Master warrantyThe warranty terms attached to the equipment record: start, end and the faults it covers.
Service orderThe order in the ERP that plans and costs a repair: the engineer, the parts and the visit.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.