S4HANA Utilities For CE IS-U CRM Migration
S4HANA Utilities For CE IS-U CRM Migration
S4HANA Utilities For CE IS-U CRM Migration
SAP S/4HANA Utilities for customer engagement is a simplified version of SAP CRM embedded into SAP
S/4HANA. While its first versions were technically delivered as an add-on (as software component S4CRM).
It has been fully embedded into S/4HANA with the 1909 release.
Within SAP S/4HANA Utilities for customer engagement, the S/4HANA Interaction Center serves as central
entry point for customer service specialists of a utility company, allowing them to access numerous industry
processes and functions. Technically the Interaction Center leverages SAP’s proven CRM Web UI
Framework technology, and new UI themes offer a harmonized Fiori user experience following SAP Fiori
user interface strategy.
This guide focuses on possible migration scenarios to SAP S/4HANA Utilities for customer engagement. It
incorporates questions and feedback received so far from the first implementation projects at utility
companies in various regions.
There are various documentations published on the SAP Help Portal. To access all the relevant information,
you need to be locked in with your user account. Component-based documentation for all functions and
processes that are supported by this product can be found here:
The SAP Support Portal offers support tools, services, applications, as well as related documentation and
community content. Simplification Items can be found here.
System Documentation
For each IMG activity, there is documentation available directly in the SAP S/4HANA system, and in many
cases as well F1 help documentation for single attributes of the customizing table.
The information in this guide complements the system documentation. Therefore, we strongly recommend to
always read the available system documentation as well. To avoid duplication of documentation, we did not
copy the system documentation into this guide.
For customers migrating from IS-U a data load for selected business partner contacts to interaction records
is recommended. Therefore see cookbook "Integration and Migration of Interaction Records".
The configuration of IC framework and customer engagement basics is required.
The reuse of front office processes (FOPs) is possible and some of those processes will run as-is. Other
processes such as "Move-in" can be eliminated because customer engagement replaces those processes.
Some processes will require data flow adjustments.
For selected CRM business activities the migration tool CRM_S4_BTX_ACTIVITY_MIGRATION is available.
Configuration and enhancements need to be migrated manually. Despite high degree of similarity (like-for-
like), caution applies to data object changed and simplifications.
*** Note: Products to be used for the integration process must be created as a material in the S/4HANA
system first (transaction MM02) For further information see SAP documentation of Utilities Product
Integration Layer (UPIL).
• Assign product to division, you must configurate one of the following options, otherwise the integration
process cannot be processed:
A. Create a standard product which serves as a kind of placeholder. You can use this product across the
entire division without specifying a rate type.
B. Create products that match the division and rate types. One product must be stored per rate category.
The product must correspond to this rate category.
Typically, the rate category and the installation facts are defined in the product. During integration,
product integration is triggered via the "Utilities Product Integration Layer" (UPIL) (IS-U-BI-PI)
component.
To avoid product integration, the product must not have an allocated rate category.
• Choose in the node Define Product Proposal for which assigned product you want to define configuration
values by activating the line
• Open node: Define Product Configuration Values (optional)
• You can assign one or more characteristics (internal characteristic number) to each product that you want
to use for integration and one or more values (characteristic value) to each characteristic. If you assign
multiple values to a characteristic, enter a sequential number in the corresponding column as far as
permissible for the characteristic.
Special Case: Change End Date and Cancel Change End Date
If the user is ending the contract or changes the end date of a contract with a default product without rate
category, no product integration is triggered. Therefore it will be possible to cancel the process “Change
End Date” and “End Contract” without a product integration being processed.
BAdI Implementation
The integration process can be customized using a Business Add-In. To do this, the customer can use the
enhancement spot CRMS4_IU_CM_PROCESS_FRAMEWORK to use the BAdI
CRMS4_IU_CM_INTEGRATION.
A BAdI interface is provided, as well as standard values for the respective processes. By implementing it as
a BAdI interface, customers have the option of customizing the individual integration processes or replacing
them completely with their own implementations. To do this, the customer can use the enhancement
spot CRMS4_IU_CM_PROCESS_FRAMEWORK to use the BAdI CRMS4_IU_CM_INTEGRATION.
Method Description
CHECK_PRECONDITION Used for a general check to see whether the current transaction (move-in/out) is
relevant for integration at all and whether the current data situation allows integration
with sales contract management
PERFORM_INTEGRATION Implementation of the integration with sales contract management using the
respective PF processes
Supported Processes
For the Basic Edition additionally, the process Fast Move In/Out in the WebClient is also relevant.
*** Note: It is possible to run the report on o regular basis by scheduling a job for the execution.
Log is displayed:
*** Note: To use the migration objects for the migration to utilities sales contract management it is
mandatory to prepare the Customizing (see chapter Customizing for the Integration). You can either use
a default product or define specific product values for the migration.
It is possible to schedule a job for the execution.