In what usually is a rather uneventful month for challenging projects the world over, December proved to be pretty challenging for my team. We had to help a firm overcome a number of pain points they experienced with the SAP CRM, particularly those associated with the Service Equipment and Install Base functionalities. While helping the customer out, I thought I could list down these pain points and how we countered them, as I believe they could work as a crystal ball for other firms as we move into 2017. So, here goes!


Challenge 1: Pain Points/Limitations in the SAP CRM Service Equipment functionality 

 

  1. Lack of quick overview of equipment information
  2. Limited search criteria for efficient equipment search
  3. Limited visibility of warranty info linked to equipment
  4. Lack of capability to list equipments based on warranty expiry dates for follow-up actions
  5. Registered product summary not available for field technicians
  6. Mass data maintenance utility not available for equipments and functional locations
  7. Inaccurate data on equipment location to be used for service processes
  8. Automatic actions or update on equipments and install bases
  9. Lack of operational reporting and dashboards for Registered Products and Install Bases

 

 

Solution to Challenge 1

 

Some of the above mentioned pain points have been addressed in SAP Hybris Cloud for Service solution as below.

  1. SAP Cloud for Service enables user-friendly searching for a registered product with the ability to add all important data in result list to get a complete view

 

 

  1. Multiple search queries are available for standard search in the case of registered products based on linked warranty information and responsibilities, which makes search quicker and easie

 


 

 

 

  1. Registered Product PDF Preview (Summary) and Repair History

 

In SAP Hybris Cloud for Service, it is possible to generate a summary of the registered products. The summary will include information such as General Data, Address, Notes, Warranty Information, Involved Parties, associated Contracts, and Maintenance Plans details. Through this functionality, the field service technicians can get an overview of the registered products and the repairs done on them and carry this information when on the move and even when not connected to SAP Hybris Cloud for Service. This functionality was missing in SAP CRM service and many customers were looking forward to it in the new cloud solution.

  1. Mass Data Maintenance for Registered Products, Installation Points, and Install Bases

 In many business scenarios, there is a need to update service master data frequently based on changes in products, service organization structure, service history, and so on. Many SAP CRM customers were looking for an easy way to perform mass update of equipment and install base master data, which is now available as a standard capability in the SAP Hybris Cloud for Service solution.

 

 

  1. Partner and Service Location Determination

 

SAP Hybris Cloud for Service has an out-of-the-box feature to identify the default product location from the ship-to-party address maintained with the registered product, which can be used in service processes. This needs to be enabled in project scoping.

 

 

  1. Automatic Notifications, Field update, and Email for Registered Products and Install Bases using Workflow Rules

 

SAP Hybris Cloud for Service offers out-of-the-box capabilities such as Send Notifications, Emails, Messages, and Update fields based on different conditions and events for service-related business objects such as registered products, installation points, and install bases.

 

Business Benefits

  • Omni-Channel communication between internal and external service business users
  • Reduction in admin tasks to update fields at different levels of install base
  • Deeper 360-degree view of customer’s assets, install base for reporting and tracking
  • Auto email communications between field service employees and back-office
  • Improved service operations with reduction in turnaround time for customer services

 

Workflow Rules Types

 

  1. E-Mail   [To trigger an email notification based on the defined condition in previous steps with email body as defined in the HTML template file]
  2. Field Update [To update any standard or custom fields based on the required conditions]
  3. Messaging [To send SMS messages]
  4. Notification  [To create a C4C notification based on the conditions defined and to the recipient group or employee]

 

 

Previously, customers used to develop their own custom solutions to fulfil the above business requirements.

  1. Reporting on Registered Products and Install Bases

 

Cloud for Service offers out-of-the-box reports on registered products and install bases, which can be leveraged to configure reports and dashboards for customer-specific business requirements.

 

 

Challenge 2: Pain Points/Limitations in the SAP CRM Install Base functionality 

 

  1. Install base searches are not quick and user-friendly based on required attributes
  2. Partner inheritance for lower level of install base structure
  3. Lack of ability to maintain competitor’s products in customer install bases
  4. Lack of capability to create service order (service ticket) from install base view
  5. Difficulty in managing equipment movement between customers and country border
  6. Inflexible install base access restriction based on organizational attributes
  7. No means for mass data update/maintenance for Install Base data
  8. Inability to migrate equipment, functional locations, and install base in standalone SAP CRM systems

 

Solution to Challenge 2

SAP Hybris Cloud for Service offers the following capabilities to overcome some of the limitations of the SAP CRM install base functionality listed above.

  1. Install base search queries based on responsibilities and organizational units

The following install base search queries can be useful for service technicians and service administrators to search and get quick visibility of the install bases and registered products for which they are responsible.

  1. My Installed Bases – Employee Responsible
  2. My Installed Bases – Service Technician
  3. My Team’s Installed Bases- Employee Responsible
  4. My Team’s Installed Bases- Service Team
  5. My Territories Installed Bases

 

  1. Involved Parties (Partners) Inheritance to Lower Level of Install Base Items

 

An install base can have multiple partners such as Customer, Employee Responsible, Service Technician, Service Technician team, and so on. Details of these partners should be logically inherited (applicable) at the lower levels of the install base items. This is in order to avoid partner maintenance at every level which is difficult to manage and not desirable for business users.

 

SAP Hybris Cloud for Service has the out-of-the-box capability where Involved Parties (Partners)  maintained at the install base level are applicable to all items (lower levels) unless different Involved Parties (Partners) are maintained at the lower items. In SAP CRM, the logical inheritance of Partners and Address is supported for the lower level of the install base components but is limited to searches only.

 

  1. Competitor Products Installed at Customer Install Bases

Competitor product information can be used for product recommendations and for cross-sell during service or sales processes.  SAP CRM does not offer the capability to maintain competitor products at the install base. However, Cloud for Service comes with this functionality.



 

  1. Create Service Ticket from Install Base Item Overview

 

The SAP CRM install base view has an assignment block with a list of service orders created for equipment or install base, but it does not allow the creation of a new ticket. In Cloud for Service, a ticket can be created from the registered product view or – when creating a ticket – the agent can search for a registered product and add it to the ticket.

 

Some of the information maintained in the registered product is carried over to the ticket, for example, location or party information.

 

 

  1. Managing Install Base Movement Between Two Customers and Country Borders

 

In many service business scenarios, there is often transfer of ownership of registered products (equipments) between two customers. In these scenarios, it’s critical for customer service departments to update customers and other partners at the install base top level and its lower level structure in order to reflect the correct customer ownership.

In the SAP CRM install base functionality, users needs to manually update customer details on the top level of the install base and its lower equipment structure. This is a painful and time-consuming activity, specifically for businesses that often involve local customer equipment movement within regions, territories, and across country borders.

In SAP Hybris Cloud for Service, once users update the customer on the top level of the install base, it’s possible to automatically update customer to all the items (lower level structure) by executing a standard function called “Update Customer of Items.

You can then check logs for a customer update on the “Items Logs” facet.

 

  1. Flexible Access Restrictions for Install Base

 

In SAP CRM, user access to install base can be configured based on the authorization group, which is assigned to different categories of install bases. This authorization group controls the display, change, or create access for business users. But, often, customer service groups are divided based on different organization attributes and responsibilities that require different levels of access control for install bases.

 

SAP Hybris Cloud for Service has the following attributes to control user access to create, view, and update the install base.

 

  1. Employee Responsible (Access Group – Employees)
  2. Service Technician (Access Group – Employees)
  3. Service Technician Team (Access Group – Organization)
  4. Territory (Access Group – Territories)
  5. Combination of Assigned Territories, Service Organization, or Employee

 

 

  1. Migration of Registered Products, Installation Points, and Install Bases in Cloud for Service

 

SAP Hybris Cloud for Service has out-of-the-box data migration templates for registered products, installation points, and install base.

Takeaway: I expect a number of big brands to move to SAP Hybris Cloud for Service in 2017. The pain points presented by SAP CRM will be alleviated for most firms and the customer experience will be enhanced like never before as they take this step.

This blog is also available on our site http://knacksystems.com/blog/some-solutions-to-your-sap-crm-service-pain-points-to-bookmark-for-2017/

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply