Changes in SAP Multichannel

Foundation for Utilities and Public

Sector (Utilities) on SAP S/4HANA

Version Status Date

1.0 Final August 11, 2016
SAP MCF Changes

Table of Content
1. Introduction ___________________________________________________________ 3
2. Changes in MCF ____________________________________________________________ 3
2.1. Model change ______________________________________________________________ 3
2.2. Class change _______________________________________________________________ 5
2.3. UI Change __________________________________________________________________ 6
2.4. BAdI Change _______________________________________________________________ 6

© 2016 – SAP SE Page 2 of 6

SAP MCF Changes

1. Introduction
The SAP MCF add-on (UMCERP01) is retrofitted into SAP S/4HANA 1610. In some cases, the
change requires the adaptation of the customer code and dictionary, or at least checking whether
code or the dictionary need to be adapted. This cookbook aims to help users to understand the
changes and their consequences.

2. Changes in SAP MCF

To facilitate reuse by other industries, for example, Public Sector, non IS-U specific logic of SAP MCF
is split into the FI-CA layer. The corresponding OData classes, APIs, structures, data elements,
etc. have been moved to the FI-CA layer. The rest remain in IS-U layer.
Package: FKK_UMC and sub package: FKK_UMC_BEA, FKK_UMC_CUST, FKK_UMC_ODC are
created in FI-CA layer following the same name convention.

2.1. Model Change

Old service models ERP_UTILITIES_UMC and ERP_UTILITIES_UMC_PUBLIC_SRV are replaced by

ERP_ISU_UMC and ERP_ISU_UMC_PUBLIC respectively. ERP_ISU_UMC is redefined from new
OData service ERP_FICA_UMC.

© 2016 – SAP SE Page 3 of 6

SAP MCF Changes

© 2016 – SAP SE Page 4 of 6

SAP MCF Changes

2.1.1 Impact on Customer Model Enhancement

The enhancement made to the model, which is rare, should be done on the new models. Model
ERP_ISU_UMC is redefined from new OData service ERP_FICA_UMC. Enhancement for entities,
e.g. Account, which is inherent from ERP_FICA_UMC should be done in the model: ERP_FICA_UMC.
After all the enhancements, all the models should be regenerated in the order of inheritance.

2.1.2 Impact on Customer UI Code

The OData service name, which is defined as constant, has to be updated accordingly. Change UI
ERP ODATA services name from ERP_UTILITIES_UMC and ERP_UTILITIES_UMC_PUBLIC_SRV
to ERP_ISU_UMC and ERP_ISU_UMC_PUBLIC respectively

2.1.3 Impact on Customer Code

The customer code enhancement made to the following classes has to be adapt to the corresponding
new classes.

Old
CL_ERP_UTILITIES_UMC_DPC
CL_ERP_UTILITIES_UMC_DPC_EXT
CL_ERP_UTILITIES_UMC_MPC
CL_ERP_UTILITIES_UMC_MPC_EXT
CL_ERP_UTILITIES_UMC_P_DPC
CL_ERP_UTILITIES_UMC_P_DPC_EXT
CL_ERP_UTILITIES_UMC_P_MPC
CL_ERP_UTILITIES_UMC_P_MPC_EXT
New
CL_ERP_ISU_UMC_DPC
CL_ERP_ISU_UMC_DPC_EXT
CL_ERP_ISU_UMC_MPC
CL_ERP_ISU_UMC_MPC_EXT
CL_ERP_ISU_UMC_PUBLIC_DPC
CL_ERP_ISU_UMC_PUBLIC_DPC_EXT
CL_ERP_ISU_UMC_PUBLIC_MPC
CL_ERP_ISU_UMC_PUBLIC_MPC

2.2. Class Change

2.2.1 OData Class Change

The classes in IS-U layer inherit from those in FI-CA layer with some methods redefined.

Entity FI-CA layer IS-U layer

AccountContact CL_FKK_UMC_ODATA_ACCCONTACT CL_ISU_UMC_ODATA_ACCCONTACT
AccountAlert CL_FKK_UMC_ODATA_ACCOUNTALERT CL_ISU_UMC_ODATA_ACCOUNTALERT
CommunicationPreference CL_FKK_UMC_ODATA_COMMPREF CL_ISU_UMC_ODATA_COMMPREF
ContractAccount CL_FKK_UMC_ODATA_CONTRACC CL_ISU_UMC_ODATA_CONTRACC

2.2.2 API Class Change

The common logics are in FI-CA layer, while specific logics reside in IS-U layer.

FI-CA layer IS-U layer

API service for ContractAccount CL_FKK_UMC_API_CONTRACC CL_ISU_UMC_API_CONTRACC

© 2016 – SAP SE Page 5 of 6

SAP MCF Changes

API service for Correspondence CL_FKK_UMC_API_CORRESPONDENCE CL_ISU_UMC_API_CORRESPONDENCE

2.2.3 Impact on Customer Code

The customer code enhancement made to the changed classes has to be adapted.

2.3. UI Change
2.3.1 SAP ERP as Leading System

The UI template is available in SAP S/4HANA on-premise edition 1610 as add-on: UIS4MCF. The UI
template has been changed to SAP ERP as leading system.
User management is changed as well so that user will be created first in SAP ERP and then created
via RFC in SAP CRM.

2.3.2 Batch Processing

Read Access Logging (RAL) is used to monitor and log read access to sensitive data. In MCF RAL
configuration, BankAccount and PaymentCard are involved for read access logging. They require
batch processing for the OData request.

2.3.3 Impact on Customer UI Code

Customer needs to apply note: 2306909 to enable user management when ERP is a leading system.
Customer UI Code for BankAccount, PaymentCard requests have to be changed to batch processing.

2.4. BAdI Change

BAdI ISU_UMC_CREATE_EMAIL and ISU_UMC_CHANNEL are replaced by
BAdI FICA_UMC_CREATE_EMAIL and FICA_UMC_CHANNEL under new enhancement spot
FICA_UMC_ODATA in FI-CA layer respectively.

2.4.1 Impact on Customer BAdI Enhancement

Customer enhancement made to BAdI ISU_UMC_CREATE_EMAIL and ISU_UMC_CHANNEL need

to be done on new BAdI FICA_UMC_CREATE_EMAIL and FICA_UMC_CHANNEL under new
enhancement spot FICA_UMC_ODATA in FI-CA layer respectively.

2.4.2 Impact on Customer Code

For customer code, in case BAdI ISU_UMC_CREATE_EMAIL and/or ISU_UMC_CHANNEL are

called, change to BAdI FICA_UMC_CREATE_EMAIL and FICA_UMC_CHANNEL respectively.

© 2016 – SAP SE Page 6 of 6