SAP CS

CS manages the service side of the customer relationship: recording installed base/equipment at customers, processing service notifications and orders, managing warranties and service contracts, and handling repairs (including in-house and field service). It supports revenue and satisfaction from after-sales service.

• Installed base & equipment at customers.
• Service Notifications & Orders.
• Warranties & Service Contracts.
• Repairs and returns.

CS exists to answer one question: what have we sold, where is it now, and what has happened to it. Everything else follows from that.

The installed base is the structure recording equipment at customer sites, including how components fit together. A machine with replaceable parts is modelled as a hierarchy, so a service call about a component knows which machine and which customer it belongs to.

Equipment records carry serial numbers and history. That history is the asset: it tells an engineer what was done last time, and it tells the business whether this model fails more than it should.

Warranties attach to equipment with dates and terms, and they decide whether a service call is billable. Getting warranty determination right is a large part of whether CS pays for itself, because the alternative is invoicing customers for work under warranty or absorbing work that was chargeable.

Service contracts go further, defining entitlement and response times, and they are what service level reporting measures against.

Half an hour, and it is the CS cycle in one pass.

1. A customer reports a fault. Create a service notification against the equipment at their site. The installed base tells you what it is and where.
2. Check entitlement. Warranty or contract determines whether the work is chargeable, and that answer changes what happens next.
3. Create a service order. Add operations for the labour and components for the spare parts.
4. Execute: issue the parts from stock, confirm the hours. Cost accumulates on the order exactly as it does in maintenance.
5. Complete and bill. Where the work is chargeable, resource-related billing turns the confirmed time and materials into a sales invoice through SD. Where it is under warranty, the cost settles internally instead.

Step five is the difference between CS and plant maintenance: the same shape of work, and an invoice at the end of it.

CS integrates with SD (service billing), MM (spare parts), PM (technical objects and maintenance), and FI/CO (service costs and revenue). In modern landscapes, service is also delivered via SAP Service Cloud (CX) and S/4HANA Service, integrated with the core.

CS is close enough to plant maintenance to share much of its structure, and the distinction is whose equipment it is. PM maintains your own assets and settles cost internally. CS services customer equipment and can bill for it. Where a business does both, the two are usually configured together because the technical objects and the order logic overlap heavily. See SAP CO for where the costs land in either case.

• How much of the installed base to model. Full component hierarchies give precise history and take real effort to keep accurate as parts are swapped.
• Where warranty is determined. Automatic determination from the equipment is the whole point; manual entry means somebody decides case by case and the revenue leaks.
• Resource-related billing or fixed price. Billing actual time and materials is transparent and produces disputes about hours. Fixed price is simpler and carries the risk.
• Field service scheduling. Dispatching engineers with skills, parts and travel is a discipline of its own, and it may point at a dedicated field service product rather than core CS.

Service businesses are judged on responsiveness, and CS is where that is recorded, which makes the measurement design a real part of the implementation.

Response time is from a call being logged to somebody responding. Resolution time is from logged to fixed. Contracts usually specify both, and they are measured differently: response is largely a dispatching question, resolution depends on parts and travel.

Service profiles define when the clock runs. A customer with cover from nine to five does not accrue elapsed time overnight, and a twenty-four hour contract does. Getting the working time calendars right is what makes the measurement fair, and it is the part most often left at defaults.

Response profiles define the escalation stages: notify at this point, escalate at that one. Those triggers are what make a service level agreement operational rather than a number in a contract.

First time fix is the measure service organisations care about most, because a second visit costs as much as the first and disappoints the customer twice. It is driven less by the system and more by whether the engineer arrived with the right part, which is a parts planning question feeding back into materials management.

The reporting that follows tells you which equipment types fail most, which engineers resolve first time, and which contracts are unprofitable. That last one is often uncomfortable and it is the main commercial argument for implementing CS properly rather than running service on spreadsheets.

Learn CS through its core processes, its master data and configuration, and its integration with the rest of the SAP landscape. Hands-on practice cements it.

An engineer without the right part is a wasted visit, and spare parts planning is where service economics are won or lost.

Where parts are held is the first decision. Central stock is cheap to hold and slow to reach a customer. Regional depots are faster and multiply inventory. Van stock is fastest and is the most expensive and hardest to control, since every vehicle is effectively a storage location.

What to hold follows from failure data, which is exactly what the installed base and service history provide. Parts that fail predictably can be stocked close to where the equipment is; rare parts are held centrally and shipped.

Reservations against orders connect service to materials management. A service order with components creates demand, and whether that demand triggers replenishment depends on how planning is configured for those materials.

Returns and repairs add a loop most businesses handle poorly. A failed part removed from a customer site may be repairable, so it comes back, is assessed, repaired and returned to stock as a refurbished item. Modelling that properly needs its own material handling and valuation.

The measure that ties it together is first time fix rate, and it is mostly a parts availability number rather than an engineering skill number.

• Learning features, not the end-to-end process.
• Ignoring integration with finance and neighbouring areas.
• Skipping master data/configuration the process depends on.

• An installed base nobody updates. Once it diverges from reality, engineers stop trusting it and enter what they find, which is the end of the history.
• Service orders that are never technically completed. Cost stays on the order and never reaches billing or settlement.
• Treating CS as PM with an invoice bolted on. See SAP CRM for the customer-facing side and SAP BW for reporting across it.

• Warranty determined manually. Every case becomes a judgement, and the revenue leaks quietly in whichever direction is least confrontational.

Taking a call is the easy half, and configuring the installed base, warranty determination and resource-related billing so service is profitable is the part you do in the course.

The measure to watch is first time fix, because it exposes everything else: whether the installed base is accurate, whether entitlement was determined correctly, and whether the right part was on the van.