With the introduction of the utility extension to C4C, SAP enabled the C4C solution to be used as the Sales and Call Center solution running on top of IS-U. This is not a replacement of the CRM OP for Utilities, but should be considered an alternative.
The purpose of this blog are 2 things:
- Provide a 5 minute overview of the utility solution
- Contains links to further information about the solution
THE TARGET AUDIENCE
I guess there is 2 major groups of people interested in this solution, one is Hybris consultants interested in the utility content and the others are the resources that has histrorically implemented IS-U and CRM OP for Utilities. The target group here is for the last group – those who already understand IS-U and to some extend the utility industry.
C4C@Utilities is supporting both the call center processes as well as the sales process, and as such is applicable for both regulated and deregulated utilities. In order for this to be short, I will cover the most often asked questions:
- What utility processes are supported
- How is the integration
- What objects are replicated between the systems
As of 1608 the following processes are supported:
Except for ‘Service Tickets’ – all processes are specifically designed to support utilities.
As for the standard C4C integration, the connection between IS-U (ERP) and C4C is done via PI or HCI. So in a simple diagram it looks like this:
Data Objects Replicated
The replication for the utility specific objects is only from IS-U to C4C and the objects replicated are:
- Contract Account, only required for sales scenario otherwise optional
- Connection Object
- Point of Delivery (POD), only required for sales scenario otherwise optional
Business Partner is also replicated, but this is part of the standard C4C to ERP integration, and here there is the option of a 2 way replication.
More Detailed Information
- Work Centers and views in C4C @ Utilities
- Link to on-line Administration Guide
- Short overview of C4C @ Utilities
Extending the functionality in C4C
- Calling the Master Data Generator (in IS-U) via a web service from C4C – Overview of use case
- Adding custom logic during step navigation to the guided move-in process
- Adding fields to the guided move-in using KUT
- Adding custom fields and logic to the guided move-in using PDI
- How to activate the badi for the guided move-in
- How to configure the MDT called by the guided move-in