CONFIGURATION GUIDE | PUBLIC

2020-01-29

Migration Guide for Offer-to-Cash Based on BRIM

Using SAP S/4HANA and SAP CRM
© 2020 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Motivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

5 Migration Strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2 Migration of Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3 Migration of Transaction Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Migration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1 Preparatory Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.2 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Contract Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Prepaid Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Provider Contract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Master Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.3 Transaction Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Prerequisites for the Migration of Transaction Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Open Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Optically-Archived Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Payments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Billable Items with Status Raw (BIT0) and Billable (BIT2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Consumption Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Prepaid Balances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

7 FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

8 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.1 List of Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.2 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
2 PUBLIC Content
1 Disclaimer

 Caution

● This document is not part of the official SAP documentation.

● This document only gives examples of how to use, configure and implement functions.
● You are responsible for determining whether the examples given can be applied to your system
landscape and system configuration.
● If you follow the examples given, you do so at your own risk.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Disclaimer PUBLIC 3
2 Document History

Version Date Description of the Change

1.0 February 2019

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
4 PUBLIC Document History
3 System Requirements

The tools described in this Migration Guide are available starting with the following Release levels of the
components involved:

● SAP S/4HANA 1511

● Enhancement package 3 for SAP CRM 7.00
● SAP Convergent Charging 4.0

If you use SAP CRM 7.00 enhancement package 3 for SAP CRM 4.0 or SAP Convergent Charging , implement
the notes in SAP collective note 1948097 in the sequence specified, in your system.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
System Requirements PUBLIC 5
4 Motivation

The Offer-to-Cash end-to-end process enables you to more efficiently organize your business processes. The
end-to-end process extends over the following three SAP components, each of which runs in a separate system
(see figure 1):

● SAP Customer Relationship Management (SAP CRM)

● SAP Convergent Charging (SAP CC)
● SAP S/4HANA

Since the entire process is integrated across the three systems, integration at the data level is of primary
importance. For example, the master data objects business partner, contract account, prepaid account, and
provider contract have to be known in all three systems. With regard to transaction data, such as open items,
payments, and billable items, SAP S/4HANA plays the leading role. The current balance of prepaid accounts is
persisted solely in SAP CC.

System Landscape for Offer-to-Cash End-to-End Process

To be able to convert your existing business processes to the Offer-to-Cash end-to-end process, you have to
migrate the necessary master data and transaction data from your legacy system as part of a migration project
to the SAP systems mentioned.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
6 PUBLIC Motivation
This document describes how you can migrate your existing solution to the complete product with all of its
components, that is, SAP CRM, SAP S/4HANA and SAP CC. If you only use parts of the product, although this
document is able to support you with your migration project to some extent, it does not explicitly deal with the
following scenarios:

● You use only the Billing Suite (SAP S/4HANA and SAP CC).
● You use only SAP S/4HANA and SAP CRM without SAP CC.
● You use SAP CC and SAP CRM without SAP S/4HANA.
● You use only SAP S/4HANA.
● You use only SAP CC.
● You use only SAP CC.

This Migration Guide is focused on issues and questions that arise in relation to the 3-system architecture. For
answers to general questions related to migration (for example in Contract Accounts Receivable and Payable
(FI-CA)), see the guide for data migration for FI-CA-based industry solutions. Issues that are already dealt with
there are not handled again in the current document.

For information on the data model of the Offer-to-Cash end-to-end process, see the Integration Guide. One of
the points discussed in the Integration Guide is the master data used in the individual systems. Additionally,
the possible replication settings from SAP S/4HANA to SAP CC are described as follows:

● Joint master data replication

● Joint master data replication to multiple SAP CC systems

This means that migration here has to always be executed taking the rating areas into consideration.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Motivation PUBLIC 7
5 Migration Strategy

5.1 Overview
In this document, the migration strategy is divided into the following areas: Master Data Migration (business
partner, contract account, prepaid account, provider contract, product, master agreement) and Transaction
Data Migration (open items, payments, invoices, billable items, prepaid balances).

For details on the migration of individual objects, see the following chapters.

5.2 Migration of Master Data

When migrating master data, it is important to follow a specific sequence due to the dependencies among the
different objects (see figure 2).

Migration of Master Data: Business Partner, Contract Account, and Prepaid Account

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
8 PUBLIC Migration Strategy
First you migrate the business partner to SAP SAP S/4HANA using the Industry Solution Migration Workbench
(ISMW).

From the SAP S/4HANA system, you replicate the business partner to SAP CRM using CRM Middleware (MW)
by initial load. There is a link to the CRM Middleware documentation in section Additional Information [page
99].

If you migrate to an ERP system, you then have to migrate the assignment of these objects for rating areas to
SAP S/4HANA for the business partner (and then also for contract accounts and prepaid accounts). Note that
this step has already been required for joint master data replication, even if you only want to use a CC system
first of all. In this case, the rating area “space” is used.

Parallel to the replication of the business partner to SAP CRM, you can migrate contract accounts to SAP S/
4HANA using the ISMW. Additionally, the assignments of the contract accounts for rating areas are to be
migrated to SAP S/4HANA (see above).

If you use prepaid processes, migrate prepaid accounts to SAP S/4HANA using the ISMW after the migration
of contract accounts to SAP S/4HANA. At the same time, you can replicate contract accounts, for which you do
not create prepaid accounts in SAP S/4HANA, to SAP CRM. Additionally, the assignments of the prepaid
accounts for rating areas are to be migrated to SAP S/4HANA (see above).

Once contract accounts and, if applicable, prepaid accounts, are migrated to SAP S/4HANA, you can perform
the following two migration steps in parallel:

● In SAP CRM, the master data of prepaid accounts is an optional part of business agreements. Replicate
business agreements with prepaid account data to SAP CRM using Middleware (initial load).
● In SAP CC, the master data of business partners, contract accounts and prepaid accounts is combined in
one object, the subscriber account. Therefore, you cannot create subscriber accounts in SAP CC until all
required data is available in SAP S/4HANA.
● Replicate the subscriber accounts (including external accounts and prepaid accounts) to SAP CC using
SOAP.

At the same time as the migration of business partners, contract accounts, and prepaid accounts, you can
migrate your products. You first enter the necessary data manually in SAP CC and SAP CRM. Then you
replicate the product components that are relevant for SAP S/4HANA from SAP CRM to SAP S/4HANA using
Middleware. For more information on product modeling, see SAP Note 1647059 .

After migrating business partners, contract accounts, prepaid accounts, and products, you can continue with
the migration of provider contracts. Figure 3 shows the strategy for the migration of provider contracts.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Strategy PUBLIC 9
 Migration of Provider Contracts

When you create provider contracts in SAP CRM, the system creates import files for the migration to SAP S/
4HANA and SAP CC. You migrate using the ISMW in SAP S/4HANA.

As soon as the provider contracts exist in SAP S/4HANA, you can begin with the migration of transaction data
in the SAP S/4HANA system. In parallel with this, you can migrate the provider contracts to SAP CC.

If you migrate provider contracts that have a reference to a master agreement, then you have to migrate the
master agreements before you migrate the provider contracts. Or else you can perform the migration of
master agreements at the same time as the migration of provider contracts.

For the migration of business partners, contract accounts, and prepaid accounts, the data is always migrated
first to SAP S/4HANA, and from there to SAP CRM and SAP CC. For products, master agreements and provider
contracts, SAP S/4HANA stores only a part of the master data. For this reason, you need to use a different
procedure for them.

If you want to use joint master data replication on multiple SAP CC systems, you must enter the rating area for
a provider contract when migrating the provider contracts to SAP CRM. Afterwards, the rating area is migrated
to SAP S/4HANA to the provider contract. When migrating to SAP CC, the rating area specifies to which SAP
CC system the master data (provider contract including the referenced business partner, contract account and
prepaid accounts) is to be replicated. To migrate the individual master data objects in isolation from each other,
the following describes how you can migrate the rating area information by means of a separate migration
object via ISMW per master data object with the migration objects.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
10 PUBLIC Migration Strategy
  Note

Instead carrying out the assignment of the rating areas for business partner, contract accounts and prepaid
accounts as in separate migration step, this can alternatively be done when migrating the provider
contracts to SAP S/4HANA: The assignment of the provider contract for the rating area is inherited by the
relevant business partner, the associated contract accounts and prepaid accounts. Therefore, it is however
first of all necessary for the migration of the master data (business partner, contract account, prepaid
account and provider contract) only takes place to SAP S/4HANA and SAP CRM. The migration of the
master data (business partner and accounts) may only be carried out to SAP CC by means of transaction
FKKCC_MD_MIG. This necessary serialization during the migration prevents the parallel execution of
migration steps as described above for business partner, contract accounts and prepaid accounts.
Afterwards, it is possible for the migration of the provider contracts to be carried out to SAP CC.

5.3 Migration of Transaction Data

You can migrate the following transaction data.

● Optically-archived invoices
If you need them for your business processes, you can migrate optically-archived invoices (for example,
PDF files).
● Open items
You can migrate open items and, as part of a project, link the migrated invoices with the items in a Z table.

Migration of Transaction Data

● Payments
You can migrate payments both with and without a reference to open items. If you migrate payments
without any reference to open items, you can migrate the payments at the same time as the open items.
● Billable items (see figure 5)
You only migrate the billable items that you have not yet billed and which therefore have not resulted in
postings in your legacy system.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Strategy PUBLIC 11
 Items that were already billed in your legacy system are part of an invoice, which you take into account
using the above-mentioned migration of invoices and open items.

Migration of Billable Items

● Consumption Items
You can store consumption items in SAP S/4HANA.
● Prepaid Balances
If you use prepaid processes, you can migrate prepaid balances. For more information, see section
Migration of Prepaid Balances [page 83].

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
12 PUBLIC Migration Strategy
6 Migration Objects

6.1 Preparatory Steps

The ISMW is the migration tool for many of the migration objects listed in the following. If you use the ISMW,
you have to enter a company (migration company) on the initial screen. Create your own company for this.

Using the ISMW, you generate various repository objects (loading reports).

You need a separate package for saving the repository objects generated by the ISMW. Create this package in
the customer namespace and assign the package to your company.

6.2 Master Data

6.2.1 Business Partner

Migration of Business Partner

Step 1: Migration of Business Partners to SAP S/4HANA

Migration Tool ISMW

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 13
Migration Object PARTNER

To achieve the best possible performance during the loading of data to SAP S/4HANA, set the ISMW control
parameters, CRM_REPL_OFF and CC_REPL_OFF, that are described below. These parameters only have an
effect on objects created by the ISMW. If you manually create objects in the system during migration using
ISMW, then these parameters have no effect on them.

ISMW Control Parameter CRM_REPL_OFF

During the migration of the business partner to SAP S/4HANA using ISMW, you need to prevent the newly
created business partners from being replicated directly to SAP CRM using Middleware. To do so, you have to
deactivate the online replication mechanism of the Middleware.

Start transaction EMIGALL and from the menu choose IS Migration Settings SAP Settings . Set the
value X there for the control parameter CRM_REPL_OFF (see figure 7). This prevents the objects created using
ISMW from being replicated online to SAP CRM.

ISMW Control Parameter CRM_REPL_OFF

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
14 PUBLIC Migration Objects
  Caution

Control parameter CRM_REPL_OFF works only if you are using the software component IS-UT (SAP
Utilities/Telecommunication).

If you are not using this software component, then deactivate the Middleware for the time period during
which the data is being loaded. To do so, start transaction BF11 and deselect the Application Active
indicator for the application indicator BC-MID (Middleware).

Once the migration is complete, activate the Middleware again.

ISMW Control Parameter CC_REPL_OFF

During the migration of the business partner to SAP S/4HANA using ISMW, you need to prevent the newly
created business partners from being replicated directly to SAP CC using master data distribution. To do so,
you have to deactivate the distribution to SAP CC.

Start transaction EMIGALL and from the menu choose IS Migration Settings SAP Settings . Here, set
the control parameter CC_REPL_OFF to the value X. If this control parameter is set, the objects created via
ISMW are not replicated online to SAP CC.

Migration of Rating Areas to SAP S/4HANA for Business Partners

If you migrate to a SAP S/4HANA system, perform the following steps for migration. Note that this migration
step is necessary if you only want to use the joint master data distribution with an SAP CC system. In this case,
the rating area with the value SPACE is used.

 Note

It is first possible to carry out migration of rating areas for master data (business partner, contract
accounts, prepaid accounts) during the migration of provider contracts. The prerequisite for this is that all
the master data (business partner, contract accounts, prepaid accounts, provider contracts) are migrated
first of all to SAP S/4HANA, before you start with the migration to SAP CC.

Migration Tool ISMW

Migration Object Create the migration object RATGAREA_P in the SAP S/

4HANA system in transaction EMIGALL.

Migration Class BAPI

Short Name RAP (Rating Area Partner)

Service Module FKK_MIGRATION_RATING_AREA

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 15
To migrate rating areas for business partners to SAP S/4HANA, proceed as follows:

1. Make the following changes in the screen for maintaining the migration object (the value 000 for the
Blocking Status field is only a default value):

Creating Migration Object RATGAREA_P

2. Save your entries.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
16 PUBLIC Migration Objects
3. The field CLIENT should not be taken into account for the migration. You ensure that this is attained using
the field rule Initial. To maintain the field rule, double click on the CLIENT field:

Call of Field Maintenance for Migration Object RATGAREA_P - CLIENT

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 17
4. Make the following adjustments in field maintenance:

Field Maintenance for Migration Object RATGAREA_P - CLIENT

This enables you to provide the field CLIENT with an initial value when migrating internally.
5. Save your entries.
6. The rating area information should only be created if the business partner account that is used already
exists in SAP S/4HANA. You ensure that this is the case using the field rule Via KSM. To maintain the field
rule, double click on the OBJID field:

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
18 PUBLIC Migration Objects
7. Make the following adjustments:

Field Maintenance for Migration Object RATGAREA_P - OBJID

8. Save your entries.
9. The field OBJTYPE should be provided with a fixed value. You ensure that this is attained using the field rule
Fixed Value. To maintain the field rule, double click on the OBJTYPE field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 19
10. Make the following adjustments:

Field Maintenance for Migration Object RATGAREA_P - OBJTYPE

First define the fixed value OBJTYPE_PA of type String with the fixed value content 1. Enter this fixed value
for the field OBJTYPE.
11. Save your entries.
12. Save the changes you made.
13. Generate the loading report.

You can now use migration object RATGAREA_P.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
20 PUBLIC Migration Objects
  Note

You only need the legacy system key and the relevant rating area when importing the data for this migration
object. All other fields do not need to be specified for the call up.

Step 2a: Migration of Business Partners to SAP CRM

Migration Tool Middleware - Initial Download

Adapter Object BUPA_MAIN

Step 2b: Migration of Business Partners to SAP CC

Migration Tool Transaction FKKCC_MD_MIG in SAP S/4HANA (Migration of Master Data to SAP Con­
vergent Charging)

 Caution
Do not perform this step until business partners, contract accounts, and (if ap­
plicable) prepaid accounts were already migrated to SAP S/4HANA.

Transaction FKKCC_MD_MIG

Using transaction FKKCC_MD_MIG, you can distribute business partners and the contract accounts and prepaid
accounts belonging to them to SAP Convergent Charging. Do not distribute business partners to SAP CC
unless the related contract accounts and prepaid accounts have already been migrated to SAP S/4HANA.

The transaction internally uses mass-capable Web service operations that make it possible to transfer multiple
objects to SAP CC for each service call:

Business Partner

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 21
Web Service suacProvisioning

Operation subscriberAccountMaintainMass

Contract Account

Web Service suacProvisioning

Operation externalAccountMaintainMass

Prepaid Account

Web Service suacProvisioning

Operation prepaidAccountMaintainMass

Using transaction FKKCC_MD_MIG, you can replicate various ranges of business partners in parallel jobs.
Schedule the transaction manually using appropriate ranges. You can define the ranges using the business
partner number, as well as using Custom Selections.

 Note

For more information about Custom Selections, see SAP Note 1939253 .

The mass-capable Web service operations used in transaction FKKCC_MD_MIG are available starting with
SAP CC 4.0. If these service operations are not available, only one object is distributed to SAP CC for each
call of a Web service operation.

If you are not using SAP CC 4.0, use transaction FKKCC_MD_MAN in SAP S/4HANA (Manual Replication to
SAP Convergent Charging).

Transaction FKKCC_MD_MAN

Using transaction FKKCC_MD_MAN, you can replicate business partners, contract accounts, and prepaid
accounts to SAP CC individually. There has to be one Web service call for each object.

Business Partner

Web Service suacProvisioning

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
22 PUBLIC Migration Objects
 Operation subscriberAccountMaintain

Contract Account

Web Service suacProvisioning

Operation externalAccountMaintain

Prepaid Account

Web Service suacProvisioning

Operation prepaidAccountMaintain

6.2.2 Contract Account

Migration of Contract Account

Step 1: Migration of Contract Accounts to SAP S/4HANA

Migration Tool ISMW

Migration Object ACCOUNT

Migration of rating areas to SAP S/4HANA for contract accounts

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 23
Migration Tool ISWM

Migration Object Create the migration object RATGAREA_A in the SAP S/

4HANA system in transaction EMIGALL.

Migration Class BAPI

Short Name RAP (Rating Area Partner)

Service Module FKK_MIGRATION_RATING_AREA

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
24 PUBLIC Migration Objects
To migrate rating areas for contract accounts to SAP S/4HANA, proceed as follows:

1. Make the following changes in the screen for maintaining the migration object (the value 000 for the
Blocking Status field is only a default value):

Creating Migration Object RATGAREA_A

2. Save your entries.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 25
3. The field CLIENT should not be taken into account for the migration. You ensure that this is attained using
the field rule Initial. To maintain the field rule, double click on the CLIENT field:

Call of Field Maintenance for Migration Object RATGAREA_A - CLIENT

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
26 PUBLIC Migration Objects
4. Make the following adjustments in field maintenance:

Field Maintenance for Migration Object RATGAREA_A - CLIENT

This enables you to provide the field CLIENT with an initial value when migrating internally.
5. Save your entries.
6. The rating area information should only be created if the business partner that is used already exists in
SAP S/4HANA. You ensure that this is the case using the field rule Via KSM. To maintain the field rule,
double click on the OBJID field:

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 27
7. Make the following adjustments:

Field Maintenance for Migration Object RATGAREA_A - OBJID

8. Save your entries.
9. The field OBJTYPE should be provided with a fixed value. You ensure that this is attained using the field rule
Fixed Value. To maintain the field rule, double click on the OBJTYPE field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
28 PUBLIC Migration Objects
10. Make the following adjustments:

Field Maintenance for Migration Object RATGAREA_A - OBJTYPE

First define the fixed value OBJTYPE_CA of type String with the fixed value content 2. Enter this fixed value
for the field OBJTYPE.
11. Save your entries.
12. Save the changes you made.
13. Generate the loading report.

You can now use migration object RATGAREA_A.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 29
  Note

You only need the legacy system key and the relevant rating area when importing the data for this migration
object. All other fields do not need to be specified for the call up.

Step 2a: Migration of Contract Accounts to SAP CRM

Migration Tool Middleware - Initial Download

Adapter Object BUAG_MAIN

Step 2b: Migration of Contract Accounts to SAP CC

The migration takes place as described in Step 2b for the migration of business partners to SAP CC.

 Caution

Do not perform this step until business partners, contract accounts, and (if applicable) prepaid accounts
were already migrated to SAP S/4HANA.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
30 PUBLIC Migration Objects
6.2.3 Prepaid Account

Migration of Prepaid Account

Step 1: Migration of Prepaid Accounts to SAP S/4HANA

Migration Tool ISMW

Migration Object Create the migration object CA_PREPACC in the SAP S/

4HANA system in transaction EMIGALL.

Migration Class BAPI

Short Name PPA (Prepaid Account)

Service Module BAPI_CTRACPREPAIDACCOUNT_CREA

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 31
To migrate prepaid accounts to SAP S/4HANA, proceed as follows:

1. Make the following changes in the screen for maintaining the migration object (the value 000 for the
Blocking Status field is only a default value):

Creating Migration Object CA_PREPACC

2. Save your changes.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
32 PUBLIC Migration Objects
3. Maintain the interface as follows:

Interface for Migration Object CA_PREPACC (Exporting)

The result is that no change documents are updated during the migration of the prepaid accounts.
4. Save the migration object.
5. If you want to use internal number assignment for the migration of prepaid accounts, the IMPORT_FIELDS
substructure is not relevant. In that case, you can exclude the substructure from the generation. Maintain
the IMPORT_FIELDS substructure (double click on the migration object CA_PREPACC, double click on
IMPORT_FIELDS, then choose Automatic Structure Change from the menu):

Path for Structure Maintenance of Migration Object CA_PREPACC

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 33
6. Deselect the Generation indicator on the upper part of the screen:

Structure Maintenance for Migration Object CA_PREPACC - Substructure IMPORT_FIELDS

7. Save your changes.
8. If you want to use external number assignment for prepaid accounts, then you are not allowed to exclude
the IMPORT_FIELDS substructure from the generation. In that case, you have make sure the value SPACE
is entered for the TESTRUN field of the substructure. (If TESTRUN = X is set, then the prepaid data is not
written to the database. Despite this, the ISMW would store the keys as processed successfully.)

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
34 PUBLIC Migration Objects
9. The prepaid account should only be created if the business partner that is used already exists in SAP S/
4HANA. You ensure that this is the case using the field rule Via KSM. To maintain the field rule, double click
on the BUSPARTNER field:

Call of Field Maintenance for Migration Object CA_PREPACC - BUSPARTNER

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 35
10. Make the following adjustments in field maintenance:

Field Maintenance for Migration Object CA_PREPACC - BUSPARTNER

The result is that the ISMW checks if an object with the entered external business partner number was
already migrated for the business partner used in migration object CA_PREPACC.
11. Save your input.
12. The prepaid account should only be created if the contract account that is used already exists in SAP S/
4HANA. You ensure that this is the case using the field rule Via KSM. To maintain the field rule, double click
on the CONT_ACCT field:

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
36 PUBLIC Migration Objects
13. Make the following adjustments in field maintenance:

Field Maintenance for Migration Object CA_PREPACC - CONT_ACCT

The result is that the ISMW checks if an object with the entered external contract account number was
already migrated for the contract account used in migration object CA_PREPACC.
14. Save your field maintenance.
15. To create a prepaid account without errors, you have to enter a currency. The fields CURRENCY (currency
key) or CURRENCY_ISO (ISO code of currency) are available in the PREPAIDACCOUNTDATA substructure.
Using field maintenance, ensure that one of these two fields is defined as a required entry field. Figure 19
shows an example of what this looks like for the CURRENCY field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 37
 Field Maintenance for Migration Object CA_PREPACC - CURRENCY
16. Save your entries.
17. The fields LIMIT1_AMOUNT, LIMIT2_AMOUNT, LIMIT3_AMOUNT and MIN_AMOUNT of the prepaid account
are for packed numbers. For the values of these fields to be transferred correctly, you have to choose the
Screen display pushbutton for the field rule Transfer. To maintain the field rule, double click on the given
field: The example below shows field maintenance for the LIMIT1_AMOUNT field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
38 PUBLIC Migration Objects
 Field Maintenance for Migration Object CA_PREPACC - LIMIT1_AMOUNT
18. Save your entries.
19. Save the changes you made.
20.Generate the loading report.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 39
 Generation of Loading Reports in ISMW for Prepaid Accounts

You can now use migration object CA_PREPACC.

○ Be aware that for the field PAYMENT_BY (Payment By for Prepaid Accounts) of substructure
PREPAIDACCOUNTDATA, the values 3 and 4 are not intended for replication to SAP CRM.

Migration of Rating Areas to SAP S/4HANA for Prepaid Accounts

Migration Tool ISMW

Migration Object Create the migration object RATGAREA_C in the SAP S/

4HANA system in transaction EMIGALL.

Migration Class BAPI

Short Name RAP (Rating Area Partner)

Service Module FKK_MIGRATION_RATING_AREA

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
40 PUBLIC Migration Objects
To migrate rating areas for prepaid accounts to SAP S/4HANA, proceed as follows:

1. Make the following changes in the screen for maintaining the migration object (the value 000 for the
Blocking Status field is only a default value):

Creating Migration Object RATGAREA_C

2. Save your entries.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 41
3. The field CLIENT should not be taken into account for the migration. You ensure that this is attained using
the field rule Initial. To maintain the field rule, double click on the CLIENT field:

Call of Field Maintenance for Migration Object RATGAREA_C - CLIENT

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
42 PUBLIC Migration Objects
4. Make the following adjustments in field maintenance:

Field Maintenance for Migration Object RATGAREA_C - CLIENT

This enables you to provide the field CLIENT with an initial value when migrating internally.
5. Save your entries.
6. The rating area information should only be created if the prepaid account that is used already exists in SAP
S/4HANA. You ensure that this is the case using the field rule Via KSM. To maintain the field rule, double
click on the OBJID field:

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 43
7. Make the following adjustments:

Field Maintenance for Migration Object RATGAREA_C - OBJID

8. Save your entries.
9. The field OBJTYPE should be provided with a fixed value. You ensure that this is attained using the field rule
Fixed Value. To maintain the field rule, double click on the OBJTYPE field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
44 PUBLIC Migration Objects
10. Make the following adjustments:

Field Maintenance for Migration Object RATGAREA_C - OBJTYPE

First define the fixed value OBJTYPE_PP of type String with the fixed value content 3. Enter this fixed value
for the field OBJTYPE.
11. Save your entries.
12. Save the changes you made.
13. Generate the loading report.

You can now use migration object RATGAREA_C.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 45
  Note

You only need the legacy system key and the relevant rating area when importing the data for this migration
object. All other fields do not need to be specified for the call up.

Step 2a: Migration of Prepaid Accounts to SAP CRM

Migration Tool Middleware - Initial Download

Adapter Object BUAG_MAIN

In SAP CRM, the prepaid account is implemented as a subobject of the business agreement (BUAG_MAIN).
Therefore, the prepaid accounts belonging to a contract account are replicated with their contract accounts
from the SAP S/4HANA system to the CRM system.

If you use prepaid processes, migrate your contract accounts to SAP CRM only after the related prepaid
accounts were already migrated to the SAP S/4HANA system.

Prepaid Schema

In SAP CRM, each prepaid account is assigned to a prepaid schema (product-dependent).

This schema controls the input values that are allowed for a prepaid account:

● Notifications for 1, 2 or 3 amount limits

● Amount of the amount limit
● Amount of the minimum balance
● Rules for the amount limits entered in the prepaid account (without steps between two amount limits, list
of amounts: 10, 20, 30, 40 and so on)

The prepaid schema is currency-dependent.

SAP S/4HANA does not use the prepaid schema. Therefore, when you initially load prepaid accounts from the
SAP S/4HANA system to the CRM system, you have to determine a prepaid schema for each prepaid account.
The following Business Add-In (BAdI) is available for this in SAP CRM:

BAdI for Determining the Schema When Creating a Prepaid Account in the SAP S/4HANA System (for example, for the Ini­
tial Load)

Enhancement spot CRM_ISX_PREPAID_ENH_SPOT

BAdI CRM_ISX_PREPAID_SCHEMA_GET

 Note

If you use just one schema for each currency, you can determine a schema on the basis of the currency
entered in the prepaid account using this BAdI.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
46 PUBLIC Migration Objects
BAdI for Checks of Prepaid Account

The following BAdI is available in SAP CRM:

BAdI Before Saving the Prepaid Account

Enhancement spot CRM_ISX_PREPAID_ENH_SPOT

BAdI CRM_ISX_PREPAID_CHECK

This BAdI makes further checks of a prepaid account possible, such as amount checks.

If you want the system to perform the same checks when the prepaid account is changed in the SAP S/4HANA
system as in the CRM system, you have to ensure this in your project by implementing the appropriate
additional BDT modules (such as BDT event DCHCK).

BAdI for Setting PPACC_RELATION When Loading Prepaid Accounts to SAP

CRM

The following BAdI is available in SAP CRM:

BAdI Before Saving the Prepaid Account

Enhancement spot CRM_ISX_PREPAID_ENH_SPOT

BAdI CRM_ISX_PREPAID_MIGRATION

If Sales & Order Management is active in SAP CRM, then only one prepaid account is possible for a business
agreement (CRMM_BUAG_H-PPACC_RELATION = 1). If Sales & Order Management is not active (that is, you use
SAP CRM solely for Financial Customer Care (FCC) or your own contract management), then you can create
multiple prepaid accounts for a business agreement (CRMM_BUAG_H-PPACC_RELATION = 2).

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 47
Re-Replication of Prepaid Accounts

 Note

If you are using enhancement package 6 for SAP ERP 6.0 and enhancement package 2 for SAP CRM 7.0,
then install the following SAP Notes before the migration, so that you can use re-replication (replication
back to SAP CRM) for prepaid accounts:

Component Note Note Text Available As Of

CRM-MD-BP-BAG 1659535 Correction of back-replication for prepaid CRM 702 SP 02

account

XX-PROJ-FI-CA 1660052 Correction of back-replication for prepaid FI-CA 606 SP 02

account ERP

AP-MD-BP 1664848 Correction of back-replication for prepaid SAP_APPL 606 SP 02

account SAP_APPL

Step 2b: Migration of Prepaid Accounts to SAP CC

The migration takes place as described in Step 2b for the migration of business partners to SAP CC.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
48 PUBLIC Migration Objects
6.2.4 Provider Contract

Migration of Provider Contract

During the migration of provider contracts, only the current status of provider contracts is considered.
Changes to the contract in the past, which led to a chronology of the provider contract in the legacy system, are
not transferred.

Step 1: Migration of Provider Contracts to SAP CRM

Migration Tool Program CRM_FICA_MIG_PROVIDER_CONTRACT

This program makes it possible to migrate provider contracts in parallel to SAP CRM.

The program internally calls the mass-capable interface for creation of provider contracts in SAP CRM
(function module CRM_ISX_BTX_API_CONT_CREATE). Function module CRM_ISX_BTX_API_CONT_CREATE
makes it possible to create multiple provider contracts in one LUW.

You call the function module in a mode (IS_CONTROL-ACTIVATION = B), in which the data is not replicated
online to SAP S/4HANA and SAP CC. In this mode, the function module returns the data in a format that can be
processed by the SAP S/4HANA System.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 49
The report records successfully created provider contracts in table CRM_ISU_TEMKSV:

● FIRMA = SAP (The Migration Company is an inbound parameter of the report and can therefore be
overwritten.)
● OBJECT = CA_BILLCTR (The Migration Object Contract is an inbound parameter of the report and can
therefore be overwritten.)
● OLDKEY = ID of the provider contract in the legacy system
● NEWKEY = ID of the provider contract in SAP CRM

Using this table, the report can prevent multiple migration of one and the same provider contract from a legacy
system. The provider contract ID from the legacy system is not persisted in the provider contract in SAP CRM.

 Note

If the report determines that a provider contract already existed for the entries that were made (migration
company, migration object contract, and legacy system key), then that provider contract is not created
again. In such cases, the system issues an error message and continues with the next provider contract.

The report creates the provider contracts in the CRM system and also, using the data returned from the CRM
system, creates two import files in ISMW binary format for import files:

● A file for creating provider contracts using ISMW in SAP S/4HANA

● A file for creating provider contracts using ISMW in SAP CC

For storing the files, use a directory that you can access both from the CRM system and from the SAP S/
4HANA system.

 Caution

So the report can generate the ISMW files for creating provider contracts in SAP S/4HANA and SAP CC, the
migration objects used for this have to be available already in the SAP S/4HANA system. Therefore, you
must create the migration objects in the SAP S/4HANA system before you run this report. For a step-by-
step guide, see step 2 and step 3 of the migration of the provider contract.

Inbound File for SAP CRM

Data of the inbound file is used to create provider contracts in SAP CRM. The provider contracts are created by
calling function module CRM_ISX_BTX_API_CONT_CREATE. For creating your inbound file, use the interface
parameter IT_CONTRACT_DATA of this function module as a reference.

Also refer to the further instructions in this section.

The inbound file that is transferred to the program for creating the provider contracts in SAP CRM is a text file
in CSV format. You can choose any separator (delimiter) for the file (for example, tab). For better readability,
the bar symbol (|) is used as a separator in the following. The inbound file consists of three blocks.

The three blocks are:

● Administrative data
Introduce the block using the CNTRL (Control) expression, and end it with &END&. Between these two,
specify in pairs (parameter name and parameter value) the tables that can be used to translate legacy
system keys entered in the contract data into internal keys. (For this, you can also use multiple CNTRL data

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
50 PUBLIC Migration Objects
 records.) If you already use the keys that are known in the SAP system in your file containing the contract
data, then no conversion is necessary. In that case, do not enter any further information after CNTRL. Enter
this block only once.
○ Business partner identification
You can use the PARTNER_NO parameter to convert the business partner. The following partner
parameters are available for this:
○ CRM_ISU_TEMKSV-PARTNER: The transferred legacy system key is replaced by the appropriate
reference entry in table CRM_ISU_TEMKSV. For determining the reference entry in table
CRM_ISU_TEMKSV, the fields entered on the selection screen – Migration Company and Migration
Object Bus. Partner – are used.

 Note

Before you can use table CRM_ISU_TEMKSV for the migration of provider contracts, you have
to make sure that the corresponding business partner keys are available in it.

○ BUT000-BPEXT: The transferred legacy system key is replaced thereby by the value of the
PARTNER field of table BUT000. The legacy system key has to be the same as the BPEXT field of
table BUT000.
○ Business agreement identification
You can use the BUAG_ID parameter to convert the business agreement. The following partner
parameters are available for this:
○ CRM_ISU_TEMKSV-BUAG: The transferred legacy system key is replaced by the appropriate
reference entry in table CRM_ISU_TEMKSV. For determining the reference entry in table
CRM_ISU_TEMKSV, the fields entered on the selection screen – Migration Company and Migration
Object Business Agreement – are used.

 Note

Before you can use table CRM_ISU_TEMKSV for the migration of provider contracts, you have
to make sure that the corresponding business agreement keys are available in it.

○ CRMM_BUAG-BUAG_ID_LEGACY: The transferred legacy system key is replaced thereby by the

value of the BUAG_ID field of table CRMM_BUAG. The legacy system key has to be the same as the
BUAG_ID_LEGACY field of table CRMM_BUAG.
To improve performance for this translation, you need an index for the legacy system keys for the
following field names in table CRMM_BUAG:
○ CLIENT
○ BUAG_ID_LEGACY
Only using this index is it possible for the report for creating the provider contracts in the inbound
file to convert the transferred legacy system keys correctly and with acceptable performance.

 Note

BUAG_ID_LEGACY is not available in CRMM_BUAG until enhancement package 3 for SAP CRM
7.0.

● Field Description Data

This block begins in the continuation line following the administrative block. In the Field Description Data
block, you make the structures used and their fields known on a line-by-line basis. The block also ends with
&END&. The structure name is always at the beginning of the line. The individual field names that are used

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 51
 in the structure follow the structure name. You can only make a structure name known once. You can
designate required entry fields using the character entered in report
CRM_FICA_MIG_PROVIDER_CONTRACT. Set this character directly before the field name (for example,
*SOLD_TO_PARTY-PARTNER_NO – if an asterisk (*) is used as the indicator for a required entry field).
Enter this block only once.

 Note

The contract data of the inbound file is transferred to the automation structure of the provider contract
interface CRMT_ISX_PROVIDER_CREATE_API. The substructures contained therein conform to the
following data record types:

Data Record Type Description Data Dictionary (DDIC) Structure

HEADER General data CRMT_ISX_GEN_DATA_DC_API

SOLD_TO_PARTY1) Partner data CRMT_ISX_PARTNER_API

ORGMAN1) Organizational data CRMT_ISX_ORGMAN_API

ITEM Item header data CRMT_ISX_PROV_ITEM_DC_API

TIMFRM2) Item dates CRMT_ISX_DATES_API

CONFIG Configuration values CRMT_ISX_CONFIG_API

TECRES Technical resources CRMT_ISX_TECH_RES_API

1) You can also address the fields of these data record types using the data record type HEADER.
2) You can also address the fields of this data record type using the data record type ITEM.

See the listed DDIC structures for the available fields of the different data record types.

● Contract data
This block Contract Data begins in the continuation line following the field description data. In this block,
you enter the contract data in the form that is specified in the field description data block. Data record
types that refer to an internal table (ITEM, CONFIG, TECRES) can be scheduled multiple times. You use
&END& to indicate that the contract data for a contract is entered completely. After &END&, the unique
contract number in the legacy system has to follow (<OLDKEY>).
You can enter this block multiple times to transfer the data for multiple contracts in one file. You indicate
the logical end of the file using &EOF&.

 Note

If an initial value is entered for a field designated as a required field in the field description data, the
system issues an error message and the data of the provider contract is not included in the import to
SAP CRM.

Figure 23 shows the file structure described above schematically.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
52 PUBLIC Migration Objects
 Inbound File for Creating Provider Contracts in SAP CRM

Without a legacy system key, the migration of a provider contract is rejected (= error in the file).
If the conversion of the business partner number is specified according to the entries in the administrative
data, then a check takes place during processing of the contract data to verify that the initial download of
the business partner was successful, and the report always converts the number automatically. The same
applies to the business agreement ID. In this case, the report always converts automatically.

 Caution

Keep in mind that the legacy system key is not yet available in table CRMM_BUAG for the conversion of
the business agreement in enhancement package 2 for SAP CRM 7.0.

You can create the file using Notepad, for example.

Step 2: Migration of Provider Contracts to SAP S/4HANA

Migration Tool ISWM

Migration Object In the SAP S/4HANA system, create the migration object
CTRTPRVERP in transaction EMIGALL.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 53
Migration Class BAPI

Short Name PCE (Provider Contract ERP)

Service Module FKK_VT_MIG_VT (calls

CRM_ISX_CONTRACT_MAINTAIN_BULK)

To migrate provider accounts to SAP S/4HANA, proceed as follows:

1. Make the following changes in the screen for maintaining the migration object (the value 000 for the
Blocking Status field is only a default value):

Creating Migration Object CTRTPRVERP

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
54 PUBLIC Migration Objects
2. Maintain the interface as follows (the value SPACE for the parameter IV_WRITE_CHANGE_DOCUMENTS is
only a proposed value):

Interface for Migration Object CTRTPRVERP (Exporting)

3. Maintain a value for Legacy system character set on tab Parameters. The following screenshot shows value
4103 as an example. The correct value can be taken from field Character Set in section ISMW Import Files
on the entry screen of program CRM_FICA_MIG_PROVIDER_CONTRACT in SAP CRM.

Character Set for Migration Object CTRTPRVERP

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 55
4. Save the migration object.
5. Maintain the IMPORT_FIELDS substructure (double click on IMPORT_FIELDS, then choose Automatic
Structure Change from the menu):

Path for Structure Maintenance of Migration Object CTRTPRVERP

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
56 PUBLIC Migration Objects
6. Deselect the Generation indicator on the upper part of the screen:

Structure Maintenance for Migration Object CTRTPRVERP - Substructure IMPORT_FIELDS

7. Save your change.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 57
8. Maintain the IT_HEADER substructure (double click on IT_HEADER, then choose Automatic Structure
Change from the menu). On the Structure tab, set the Multiple Legacy Keys indicator:

Structure Maintenance for Migration Object CTRTPRVERP - Substructure IT_HEADER

9. Save your change.
10. Maintain the STEP_GUID field (double click on IT_HEADER, double click on STEP_GUID). On the upper part
of the screen under Control data, deselect the Generate field and select the No mig. field field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
58 PUBLIC Migration Objects
 Field Maintenance for Migration Object CTRTPRVERP - Substructure IT_HEADER, Field STEP_GUID
11. Save your change.
12. Maintain the TRANS_PRICE field (double click on IT_ITEMS, double click on TRANS_PRICE). On the
Transfer tab, select the Screen display radio button.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 59
 Field Maintenance for Migration Object CTRTPRVERP - Substructure IT_ITEMS, Field TRANS_PRICE
13. Save your change.
14. Maintain the STANDALONE_PRICE field (double click on IT_ITEMS, double click on STANDALONE_PRICE).
On the Transfer tab, select the Screen display radio button.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
60 PUBLIC Migration Objects
 Field Maintenance for Migration Object CTRTPRVERP - Substructure IT_ITEMS, Field STANDALONE_PRICE
15. Save your change.
16. If you want to store the legacy system key in the VTALT field of the provider contract in the SAP S/4HANA
system, then maintain the VTALT field of substructure IT_HEADER (double click on IT_HEADER, then
double click on VTALT). Set the processing type to Rule and enter the ABAP rule MOVE imp-oldkey TO $S$
on the Rule tab.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 61
 Field Maintenance for Migration Object CTRTPRVERP - Field VTALT
17. Save your changes.
18. Generate the loading report.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
62 PUBLIC Migration Objects
 Generation of Loading Reports in ISMW - Provider Contract

You can now use migration object CTRTPRVERP.

Process Flow for the Migration

The ISMW calls function module FKK_VT_MIG_VT, which in turn calls the function module
CRM_ISX_CONTRACT_MAINTAIN_BULK with IV_SCENARIO_ID = FICA.

The function module CRM_ISX_CONTRACT_MAINTAIN_BULK calls the function module

FKK_VT_OBJ_MAINTAIN.

Commit control takes place in the ISMW.

Successfully created provider contracts are written to the database.

Provider contracts with errors are returned.

The ISMW records the IDs of provider contracts that could not be created. You can manually correct the data of
these provider contracts. After you make the corrections, you can try using the ISMW again to create these
provider contracts in SAP S/4HANA.

As soon as all provider contracts were created successfully in SAP S/4HANA, you begin with step 3.

Step 3: Migration of Provider Contracts to SAP CC

Migration Tool ISWM

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 63
Migration Object In the SAP S/4HANA system, create the migration object
CTRTPRVCC in transaction EMIGALL.

Migration Class BAPI

Short Name PCC (Provider Contract CC)

Service Module FKK_VT_MIG_VT (calls

CRM_ISX_CONTRACT_MAINTAIN_BULK)

To migrate provider contracts to SAP CC, proceed as follows:

1. Make the following changes on the screen for maintaining the migration object:

Creating Migration Object CTRTPRVCC

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
64 PUBLIC Migration Objects
2. Maintain the interface as follows:

Interface for Migration Object CTRTPRVCC

3. Maintain a value for Legacy system character set on tab Parameters. The following screenshot shows value
4103 as an example. The correct value can be taken from field Character Set in section ISMW Import Files
on the entry screen of program CRM_FICA_MIG_PROVIDER_CONTRACT in SAP CRM.

Character Set for Migration Object CTRTPRVCC

4. Save the migration object.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 65
5. Maintain the IMPORT_FIELDS substructure (double click on IMPORT_FIELDS, then choose Automatic
Structure Change from the menu):

Path for Structure Maintenance of Migration Object CTRTPRVCC

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
66 PUBLIC Migration Objects
6. Deselect the Generation indicator on the upper part of the screen:

Structure Maintenance for Migration Object CTRTPRVCC - Substructure IMPORT_FIELDS

7. Save your change.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 67
8. Maintain the IT_HEADER substructure (double click on IT_HEADER, then choose Automatic Structure
Change from the menu). On the Structure tab, set the Multiple Legacy Keys indicator:

Structure Maintenance for Migration Object CTRTPRVCC

9. Save your change.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
68 PUBLIC Migration Objects
10. The provider contract should only be created in SAP CC if it already exists in SAP S/4HANA. You ensure
that this is the case using the field rule Via KSM. To maintain the field rule, double click on the
CONTRACT_ID field:

Path for Structure Maintenance of Migration Object CTRTPRVCC

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 69
11. Make the following adjustments in field maintenance:

Field Maintenance for Migration Object CTRTPRVCC

The result is that the ISMW checks if an object with this provider contract ID was already migrated for the
migration object CTRTPRVERP. If this is not the case, then the object is not created in SAP CC.
12. Save your input.
13. Maintain the STEP_GUID field (double click on IT_HEADER, double click on STEP_GUID). On the upper part
of the screen under Control data, deselect the Generate field and select the No mig. field field.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
70 PUBLIC Migration Objects
 Field Maintenance for Migration Object CTRTPRVCC - Substructure IT_HEADER, Field STEP_GUID
14. Save your change.
15. Maintain the TRANS_PRICE field (double click on IT_ITEMS, double click on TRANS_PRICE). On the
Transfer tab, select the Screen display radio button.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 71
 Field Maintenance for Migration Object CTRTPRVCC - Substructure IT_ITEMS, Field TRANS_PRICE
16. Save your change.
17. Maintain the STANDALONE_PRICE field (double click on IT_ITEMS, double click on STANDALONE_PRICE).
On the Transfer tab, select the Screen display radio button.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
72 PUBLIC Migration Objects
 Field Maintenance for Migration Object CTRTPRVCC - Substructure IT_ITEMS, Field STANDALONE_PRICE
18. Save your change.
19. Now generate the loading report.

You can now use migration object CTRTPRVCC.

Process Flow for the Migration

The ISMW calls function module FKK_VT_MIG_VT, which in turn calls the function module
CRM_ISX_CONTRACT_MAINTAIN_BULK with IV_SCENARIO_ID = CC.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 73
Provider contracts are migrated to SAP CC only if the contracts were already successfully created in SAP S/
4HANA.

When the provider contracts are created in the SAP S/4HANA system, some additional attributes (such as
CYCLE_DATE) are added. Since these attributes are also needed for creating the provider contracts in SAP CC,
the data that is in the file has to be enriched by adding this information. Function module FKK_VT_MIG_VT
determines this information from SAP S/4HANA.

With the enriched data, the function module CRM_ISX_CONTRACT_MAINTAIN_BULK is called with
IV_SCENARIO_ID = CC.

This results in the call of the mass-capable Web service operation for creating provider contracts in SAP CC:

Provider Contract

Web Service contractProvisioning

Operation chargingContractMaintainMass

If not all provider contracts can be created in SAP CC, then SAP CC returns a return table, which contains the
IDs of the affected provider contracts and the reasons they could not be created.

The ISMW records the IDs of provider contracts that could not be created. Remove the cause of the error(s)
and then try again to create the provider contracts in SAP CC using the ISMW.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
74 PUBLIC Migration Objects
6.2.5 Product

Product Migration

You first create the data needed for products in SAP CC and SAP CRM manually. Then you replicate the
product components that are relevant for SAP S/4HANA from SAP CRM to SAP S/4HANA online using
Middleware.

Replication Tool Middleware – Online Replication

Adapter Object PRODUCT_MAT and PRODUCT_SRV

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 75
6.2.6 Master Agreement

Master Agreement Migration

You first create the data needed for master agreements manually in SAP CRM. Then you replicate the master
agreement components that are relevant for SAP S/4HANA from SAP CRM to SAP S/4HANA online using
Middleware.

Replication Tool Middleware - Online Replication

Adapter Object BUS_TRANS_MSG

A master agreement is comprised of conditions (valid in provider contracts referencing the master agreement)
that regulate the business activity between the service provider and the customer. These conditions take effect
when future provider contracts are signed. The conditions of a master agreement become effective for
individual customers when they sign a provider contract and the master agreement is assigned to it.

If you migrate provider contracts that have a reference to a master agreement, then you have to migrate the
master agreements before you migrate the provider contracts. Or else you can perform the migration of
master agreements at the same time as the migration of provider contracts.

There are no tools for the migration of master agreements. Therefore, you have to create master agreements in
the system manually.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
76 PUBLIC Migration Objects
Step 1: Migration of Master Agreements to SAP CRM

Create the master agreement in SAP CRM, and assign business partners and products to the master
agreement. The data of the master agreement in SAP CRM answers the question: Who is allowed to buy what?

The master agreement data that is needed in SAP S/4HANA is then replicated automatically to SAP S/4HANA.

Step 2: Migration of Master Agreements to SAP S/4HANA

In SAP S/4HANA, you add the details of the agreements that make up the master agreement. The data of the
master agreement in SAP S/4HANA answers the following questions, for example: What is invoiced and who is
invoiced? Who receives which discounts? Who receives a copy of the invoice?

6.3 Transaction Data

6.3.1 Prerequisites for the Migration of Transaction Data

The starting point for the migration of a subsidiary ledger such as Contract Accounts Receivable and Payable
(FI-CA) must always be a legacy system that is reconciled with the general ledger. All postings from the legacy
system must have been transferred to the general ledger.

You then freeze the legacy system in this state before the migration takes place. This means that no new
postings are allowed to be generated in the legacy system. Otherwise it is not possible to assess after the
migration if the data transfer during the migration was successful.

6.3.2 Open Items

Migration Tool ISMW

Migration Object DOCUMENT

Comment The migration object is based on function module ISU_M_DOCUMENT_CREATE, which

internally calls module FKK_CREATE_DOC_MASS.

The prerequisite for the migration of open items to Contract Accounts Receivable and Payable (FI-CA) in the
SAP S/4HANA system is the migration of the master data objects business partner, contract account, prepaid
account, and provider contract.

Various procedures are available for the migration of open items to Contract Accounts Receivable and Payable
(FI-CA). All of these procedures share the following in common – that open items are always migrated
individually and all open items are always migrated. The open items must in total explain the balances of the
related reconciliation accounts.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 77
At the time of the migration of open items, the migration of the general ledger accounts and balances has
already taken place. Through the transfer of the migrated open items to the general ledger, therefore, the
general ledger would no longer be correct.

Therefore, you have to make a posting to the general ledger before the transfer of the items to be migrated.
This posting has to set the balance of the reconciliation account to zero. This measure is necessary, since at
this point in time the general ledger account can still be posted directly. As soon as you use the account as a
reconciliation account for Contract Accounts Receivable and Payable (FI-CA), the account can no longer be
posted directly. Do not use the general ledger account as a reconciliation account (account type V for Contract
Accounts Receivable and Payable) until after the receivables account has a balance of zero.

For the posting, you use an anonymous transfer account for the revenues, and this account must be a revenue
account and not a balance sheet account.

Normally, revenues are not taken into account during a migration, for the following reasons:

● Items cleared in the legacy system could have already been archived. Archived documents are not taken
into account during a migration. The balance of the revenue account in Financials (FI) can therefore not be
explained by the sum of all postings in the legacy system.
● If the revenues were transferred again to the general ledger, then Controlling would also be updated again.
It is necessary to avoid secondary effects of this kind.

If the original posting is from the previous year, and if account assignments that are no longer valid in the year
of the transfer were used in this posting, then you need to exchange the account assignments accordingly.

 Example

You are using a cost center that was still able to be posted at the time of the original posting, but is already
closed at the time of the migration.

The events 3910 (Migration: Document Transfer - Convert Document Data) and 3920 (Migration: Document
Transfer- Test Document Data ) are processed in Contract Accounts Receivable and Payable (FI-CA) for the
migration of documents. See the documentation of the function modules. These events are called from
function module ISU_M_DOCUMENT_CREATE.

Options for the Migration of Documents

Option 1: Revenue and Tax Items Are Not Migrated

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
78 PUBLIC Migration Objects
 Migration of Documents to Contract Accounts Receivable and Payable (FI-CA) - Option 1

The OLD Receivables account can be posted manually. NEW Receivables becomes the reconciliation account
for Contract Accounts Receivable and Payable (FI-CA).

Every receivable item is migrated with a tax code (FKKOP-MWSKZ); tax items (OPKs) are not migrated.

The offsetting item of the migrated document corresponds to the gross amount of the invoice.

Documents migrated in this way are not allowed to be reversed, since the tax amounts are not known. For
information on how you can prevent the reversal of these types of documents, see section 12.

Rather than reversing documents, you can write them off. For write-offs, the system determines the expense
accounts in a different way. Another alternative is to use manual postings of credits, which you offset against
the existing open items.

Option 2: Revenue and Tax Items Are Migrated

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 79
 Migration of Documents to Contract Accounts Receivable and Payable (FI-CA) - Option 2

The OLD Receivables account can be posted manually. NEW Receivables becomes the reconciliation account
for Contract Accounts Receivable and Payable (FI-CA).

The advantage of migrating revenue items and tax items is that the migrated receivables can be reversed.

For each open item, two postings are migrated to Contract Accounts Receivable and Payable (FI-CA):

3a) Contract account 119 Credit Revenue 100

Tax 19

3b) Revenue 100 Credit Clearing account 119

Tax 19

Migration When Using Tax Reporting in Contract Accounts Receivable and

Payable (FI-CA)

If you are using tax reporting (tax reporting at single document level, tax reporting at payment receipt) in
Contract Accounts Receivable and Payable (FI-CA), then you must migrate tax items. You have to ensure that
taxes are not reported to the tax authorities in duplicate.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
80 PUBLIC Migration Objects
The following are examples of how you can do this:

● Possibility 1
You are using event 0936 (Tax Reporting: Exclude Data Records (0010) to ensure that the migrated
postings (compare postings 3a and 3b) do not lead to an update of tax reporting. You do this by excluding
postings with the origin Migration from processing.
● Possibility 2
You also create entries in tables DFKKREP06 and DFKKREP07 for migrated documents, but you flag these
entries specially. You ensure that entries that have this flag do not lead to a tax report. (In the case of a
reversal, however, the system would take these lines into account.)

Migration option 2 replaces the option of migration using additional postings on a dummy contract account
and a dummy business partner. (For information on migration using dummy objects, see section 7.7.4 of the
ISMW Migration Guide.) The disadvantage of the solution using dummy master data objects is that this master
data has to remain in the system permanently, since the open items posted on them can never be cleared.

We cannot recommend a simple migration of open items, including taxes, revenues, and manual adjustment
postings to General Ledger Accounting (FI-GL), since the amounts for the manual adjustment posting are hard
to determine based on the totals records. It also provides a limited overview of the data, and problems can
occur due to rounding differences.

Migration of Down Payments

Down payments are posted as “real down payments” during a migration.

It is recommended that you make offsetting postings to dummy contract accounts using the same amounts,
but with the opposite positive/negative sign.

6.3.3 Optically-Archived Invoices

If you want to be able to access optically-archived invoices from SAP systems, then use the optically-archived
invoice as the original document for the migrated document.

You can enter the reference to the original document in the document header of the FI-CA document in the
fields AWTYP (CHAR5), AWKEY (CHAR20) and AWSYS (CHAR10).

In AWTYP, only Object Types for Accounting are allowed. Therefore, create your own Object Type for Accounting
in the customer namespace in view TTYP:

Reference Transaction (Object Type) For example, Z_INV

Description - Object Type Opt.-arch. Invoice

Structure

Function Module For example, Z_FKK_DOC_ORIG_INV

You display original documents for FI-CA documents in transaction FPE3 (Display Document). In the menu of
the transaction, choose Environment Original document . When you do so, the function module entered

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 81
for the object type is processed. In the example above, function module Z_FKK_DOC_ORIG_INV would be
processed for object type Z_INV.

For the function module, use the interface of function module FKK_DOCUMENT_SENDER.

Interface of Function Module FKK_DOCUMENT_SENDER

 Caution

The function module does not have an IMPORT parameter I_AWKEY. However, you can determine AWKEY in
your function module as follows:

awkey(10) = i_awref.

awkey+10(10) = i_aworg.

In your function module, implement the display of the optically-archived invoice.

The values that you stored in the fields AWTYP, AWKEY and AWSYS in the document header are available for
this.

6.3.4 Payments

Migration Tool ISMW

Migration Object PAYMENT

Comment The migration object is based on function module

ISU_M_PAYMENT_CREATE, which internally calls module
FKK_CREATE_DOC_MASS_AND_CLEAR.

The prerequisite for migration of payments for open items to Contract Accounts Receivable and Payable (FI-
CA) is the migration of the master data objects business partner, contract account, prepaid account, and
provider contract, as well as the migration of open items (migration object DOCUMENT).

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
82 PUBLIC Migration Objects
6.3.5 Billable Items with Status Raw (BIT0) and Billable
(BIT2)

Use function module FKK_BIX_BIT_CREATE_API to load billable items to the ERP system.

6.3.6 Consumption Items

Use function module FKK_BIX_CIT_CREATE_API to load consumption items to the ERP system.

6.3.7 Prepaid Balances

6.3.7.1 Migration of Prepaid Balances

Prerequisites for the Migration of Prepaid Balances

The starting point is a legacy system that is reconciled with the general ledger. All postings from the legacy
system must have been transferred to the general ledger. The master data from the legacy system is migrated
to the SAP system landscape. As a result, the prepaid accounts are already available in SAP CC, but without
their balances.

The legacy system manages one prepaid balance for each prepaid customer. In the general ledger, the prepaid
balances of all customer accounts are managed on the OLD Prepaid Balance account. The OLD Prepaid Balance
account can be posted directly.

NEW Prepaid Balance is a reconciliation account for Contract Accounts Receivable and Payable (FI-CA). It is not
possible to post directly to this G/L account. After you successfully migrate the prepaid balances, you use this
account for posting of prepaid balances.

The Migration account is the offsetting account for the migration postings to the NEW Prepaid Balance account.

 Example

The prepaid balance of customer 1 is EUR3 4.858. The prepaid balance of customer 2 is EUR3 11.907. All
billable items are billed. The prepaid balance posted in the general ledger (account OLD Prepaid Balance
EUR 16.77) is the rounded total of the prepaid balances in the legacy system.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 83
 Migration of Prepaid Accounts - Ideal Starting Point

The ideal situation, in which all billable items are billed, is generally not found in the real world. Therefore, the
total of the prepaid balances in the legacy system does not match the prepaid balances posted in the general
ledger. The starting point is usually more like the following example:

 Example

For customer 1, there are two usages that are not billed, each for EUR3 -0.077. In addition, there is a refill of
EUR3 5,000 that was not billed.

These three unbilled items have increased the prepaid balance of customer 1 from EUR3 4,858 to EUR3
9,704.

The following formula applies:

G/L Account Balance = Σ All Prepaid Balances - Σ All Not Billed Items

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
84 PUBLIC Migration Objects
 Migration of Prepaid Accounts - Realistic Starting Point

Step 1: Migration of Prepaid Balances and Unbilled Items from Legacy

System to Contract Accounts Receivable and Payable (FI-CA)

Migration Tool ISMW

Migration Object For the migration of billable items, you generate a BAPI migration object for function
module FKK_MIGRATION_PREPAID_BITS.

Comment Function module FKK_MIGRATION_PREPAID_BITS checks if the total of the amounts

of the billable items transferred for the prepaid account is the same as the balance
transferred for the prepaid account (IS_PPACC-PPBAL). The billable items are cre­
ated by calling function module FKK_BIX_BIT_CREATE_API.

 Caution
You transfer credits on prepaid accounts and refills as negative values. You must
transfer usages as positive values.

An entry is generated in table FKKPREPACC_MIG for each prepaid account. The bal­
ance (PPBAL) in this table is the same as the amount that must be reported to SAP
CC (FKKPREPACC_MIG-PPBAL = -IS_PPACC-PPBAL).

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 85
A prerequisite for the migration of prepaid balances is that the mediation system does not send any more
items to be rated to the legacy system. You must transmit this information to the mediation system.

Migration of Prepaid Balances - Mediation System No Longer Sends to Legacy System

You migrate prepaid balances from the legacy system individually for each prepaid customer to Contract
Accounts Receivable and Payable (FI-CA), while deducting the total of unbilled items as billable items with
balance change reason (PPRSN) 18 (Migration), (see ① in figure 54).

In addition, you migrate the unbilled items from the legacy system to Contract Accounts Receivable and
Payable (FI-CA). Always migrate all not yet billed items of a prepaid account together. Ensure that, during the
migration, each billable item receives the correct balance change reason. For example, usages should receive
balance change reason1 SPACE, individual refills 01, and automatic refills 02. (See ② in figure 54).

All migrated billable items use source transaction type Migrated Prepaid BITs MIG01.

An entry is updated in table FKKPREPACC_MIG. The migrated billable items are only billed and invoiced when
the migration is successfully completed (MIGOK = X).

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
86 PUBLIC Migration Objects
 Migration of Prepaid Balances - Migration of Billable Items to Contract Accounts Receivable and Payable (FI-CA)

1 The allowed balance change reasons are the fixed values of domain PPRSN_KK.

Step 2: Migration of Prepaid Balances to SAP CC

Migration Tool You migrate prepaid balances to SAP CC using report

RFKK_MIGRATION_PREPAID_BAL2CC (transaction EMIGPREPBAL) in Contract Ac­
counts Receivable and Payable (FI-CA).

The report determines the balances to be migrated from table FKKPREPACC_MIG. Then you migrate the
balances to SAP CC using the operation prepaidAccountStateChangeMass (Web service
prepaidAccountStateManagement).

The migration of the balances does not cause billable items to be created in Contract Accounts Receivable and
Payable (FI-CA). In a previous step, you already migrated the billable items to Contract Accounts Receivable
and Payable (FI-CA) that explain the migrated prepaid account balances in SAP CC.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 87
The status of the migration is persisted in column MIGOK of table FKKPREPACC_MIG. MIGOK can have one of
the following values:

● SPACE No Confirmation (from SAP CC)

● X
Migration Successful
● E
Errors in Migration

A migration can have errors, for example, if the prepaid account does not yet exist in SAP CC.
Migration of Prepaid Balances - Migration of Balances to SAP CC

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
88 PUBLIC Migration Objects
Step 3: Establishing Communication Between Mediation System and SAP CC
After Successful Migration

Migration of Prepaid Balances - Mediation System Sends to SAP CC

If errors occur during the migration, make sure that the mediation system continues to send the items to be
rated to the legacy system.

In that case, you have to clean up both SAP CC and Contract Accounts Receivable and Payable (FI-CA). You can
use report RFKK_MIGRATION_PREPAID_CLEANUP (transaction EMIGPREPCLE) for this. The report performs
the following steps:

1. Sets prepaid balances in SAP CC to zero

2. Deletes the migrated billable items for the prepaid account in Contract Accounts Receivable and (FI-CA)
3. Deletes the entries in table FKKPREPACC_MIG in Contract Accounts Receivable and Payable (FI-CA)

If errors occur, the report issues error messages in an application log. In this case, the entries in table
FKKPREPACC_MIG are not deleted.

Step 4: Billing and Invoicing

After a successful migration, you can bill and invoice the migrated billable items.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 89
Invoicing generates the corresponding postings and updates table FKKPREPACC_BAL. This table contains the
already invoiced balance for each prepaid account in the currency of the prepaid account. In addition, the table
contains the rounding differences for the prepaid account:

Posting of Initial Prepaid Balances (PPRSN = 18)

Customer 1 Amount 4.858 EUR3

Posting Amount 4.86 EUR

Rounding Difference (FKKPREPACC_BAL-PPRND) -0.002 EUR3

Customer 2 Amount 11.907 EUR3

Posting Amount 11.91 EUR

Rounding Difference (FKKPREPACC_BAL-PPRND) -0.003 EUR3

Posting of Unbilled Items

Refill Customer 1 Amount 5.000 EUR3

Posting Amount 5.00 EUR

Rounding Difference (FKKPREPACC_BAL-PPRND) -0.002 EUR3

Usages Customer 1 Amount -0.077 - 0.077 = -0.0154 EUR3

Posting Amount -0.16 EUR

Rounding Difference (FKKPREPACC_BAL-PPRND) -0.004 EUR3

Figure 57 shows these postings.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
90 PUBLIC Migration Objects
 Migration of Prepaid Balances - Billing and Invoicing

Step 5: Manual Adjustment Postings

OLD Prepaid Balance 16.77 Credit Migration 16.77

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 91
 Migration of Prepaid Accounts - Manual Adjustment Posting

The prerequisite for adjustment postings is that the unbilled items from the legacy system were successfully
migrated to the new landscape. In addition it is necessary that the corresponding billable items and the related
postings were created.

Posting of Migrated Prepaid Balance as Down Payment

If the prepaid credit balance is to be posted like a down payment received (payment of tax when down payment
received), then, instead of balance change reason (PPRSN) 18, use balance change reason 19 (Migration
(Posting as Down Payment)).

If only a part of the prepaid balance to be migrated is to be posted as a down payment, then migrate this part of
the prepaid balance using balance change reason 19. You migrate the remaining part using balance change
reason 18.

Processing in invoicing for PPRSN = 18:

Same process as for PPRSN = 1 (individual refill, payment made in advance)

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
92 PUBLIC Migration Objects
Processing in invoicing for PPRSN = 19:

Same process as for PPRSN = 1 and in addition:

● Call of function module FKK_TAX_ADJUST_DOWN_PAYMT_MIGR The open item is transferred to the

module. Based on this information, the module creates two additional lines – debit tax clearing and credit
tax.
● The system checks if the G/L account determined is a down payment account.

6.3.7.2 Minimizing Downtime

The migration of prepaid balances requires downtime in SAP CC. The migration strategy that is recommended
by SAP is aimed at minimizing this downtime.

You can minimize the downtime further by migrating the balances of prepaid accounts in several phases. To do
so, you divide the prepaid accounts into several blocks (for instance, based on the account number) and
migrate the balances of these accounts in phases, as follows:

1. Inform the mediation system that the balances are being migrated for a part of the prepaid accounts (for
example, ID 1 to ID n), so that the mediation system no longer sends any items to be rated to the old rating
system from that point on. For recommendations on how to handle prepaid accounting during the
migration, see section 10.3.
2. Migrate the balances of this part of your prepaid accounts.
3. Inform the mediation system that items to be rated for this part of your prepaid accounts should now be
sent to SAP CC.
4. Repeat steps 1 to 3 for the remaining prepaid accounts.

6.3.7.3 Behavior During Downtime

During the migration, you do not have access to prepaid accounts. You can react to this situation, for example,
in one of the following ways:

● Since it is not possible to access the affected prepaid accounts, the customer cannot consume any
services during the migration of prepaid balances.
● You grant your customers free use of services during the migration. From a technical perspective, you
manage this by using a dummy service to always answer queries of the mediation system relating to the
affected prepaid accounts with a positive answer. That means that you always allow the customer to use
the requested service during the migration.
● Customers can continue to consume services during the migration, without taking into account their
prepaid balance. During the migration, you collect the items to be rated. SAP CC processes these after the
prepaid balances are migrated successfully. Using this procedure can mean that customers might
consume more of their credit balance than they are entitled to.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Migration Objects PUBLIC 93
7 FAQ

Where can I find information on the Industry Solution Migration Workbench (ISMW)?

For information on the ISMW, see the Migration Guide of the Industry Solution Migration Workbench (see
section 7.2).

How do I prevent a migrated document from being reversed?

To prevent the reversal of documents after the migration:

● During the migration of documents, use origin 3A (Document from Migration).

● Then enter function module FKK_MIGRATION_PREVENT_REVERSAL as an installation-specific function
module at event 0070 (Posting: Check if Reversal Permitted).

How do I migrate partner agreements?

From a technical perspective, partner agreements are the same object as the provider contract. You migrate
partner agreements in exactly the same way as provider contracts. In SAP CRM, the Transaction Type
determines if the provider contract is a partner agreement. In SAP ERP, this is controlled by the Contract Type
field.

What do I need to keep in mind for the migration of provider contracts to SAP CC?

For the migration of a provider contract, SAP CC differentiates between Migration of the Contract Master Data
and Migration of the Contract Status. The migration tools provided by SAP cover only the migration of contract
master data. The migration takes place as described in section 8.4.

If you need the chronology of a migrated contract in SAP CC, then you also have to migrate these changes to
SAP CC. You achieve this by calling the following Web service operation multiple times for a provider contract:

Provider Contract

Web Service contractProvisioning

Operation chargingContractMaintain

As an alternative, you can migrate the contract history for provider contracts to SAP CC as part of a project
solution.

As a second step, you migrate the contract status. SAP CC includes all counters and their values in the status
of a provider contract. These counters and values are used the first time charging is carried out for the provider
contract. The operations of the Web service chargingContractStateManagement are available for
migrating the status of a provider contract.

The migration of the status of the provider contract is not a part of the migration solution described in this
guide. You need to handle this issue yourself in your specific project.

How can I calculate charges retroactively in a provider contract in SAP CC or prevent the retroactive
calculation of charges?

Scenario 1

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
94 PUBLIC FAQ
The provider contract was created in the past and not yet billed. SAP CC must calculate the recurring charges
retroactively.

Scenario 2

The provider contract was created in the past and billed. SAP CC is not allowed to calculate the recurring
charges retroactively.

You have two options for preventing the retroactive calculation of charges:

● You set the date, starting from which the provider contract is valid in SAP CC, to the date of the migration.
Although this is not correct from a business perspective, you are able to prevent the recurring charges
being calculated again retroactively.
● You migrate the contract master data to SAP CC. After the migration, you call the Web service
chargingContractStateManagement. Using this Web service, you can set values for the counters Last
Activation Date and Last Activation Status.
These two values are used by the charging logic to determine if a charged item has to be created.

 Example

Last Activation Date = never activated

In that case, SAP CC calculates the recurring charges starting from the date as of which the provider
contract is valid.

Last Activation Date = active/2016-01-01

In that case, SAP CC calculates the recurring charges starting from 01/01/2016.

How do I migrate dispute cases?

You should process all of the dispute cases that are in the legacy system before the system changeover. In this
way, you can avoid having to migrate dispute cases.

How can I improve performance during the migration?

Do not write change documents during the migration.

What do I have to maintain so that the bulk web services will be used for master data distribution to SAP
CC?

In SAP ERP, make sure that function CC-BULKS has been entered in table TFKCOMP_FC. If this entry is missing,
an error occurs during master data distribution to SAP CC (“Active SAP CC version does not support bulk Web
services”).

How should I proceed when migrating without SAP CRM?

The migration guide can also be used for a migration without SAP CRM.

For migrating provider contracts (see section 8.4), step 1, in which files are automatically created for a
migration from SAP ERP to SAP CC, is then no longer applicable. Instead, you have to make two separate files
available for the ISMW, based on the data in your legacy system:

● A file for the migration of provider contract data to SAP ERP

● A file for the migration of provider contract data to SAP CC

When creating the files, use the migration objects created for the provider contract in the ISMW as a guide. In
the step that follows, the ISMW calls the interface of the provider contract in SAP S/4HANA.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
FAQ PUBLIC 95
What do I need to look out for during a migration that is followed by implementing SAP CRM?

If you have already migrated to SAP ERP and SAP CC, and you implement SAP CRM at a later point in time,
create data in SAP CRM as follows:

● Replicate the business partners from the ERP system using middleware (MW) using an initial load to SAP
CRM.
● After you have replicated your business partners, replicate your business agreements (contract accounts)
with the prepaid account data using middleware (initial load) to SAP CRM.
● Enter your products manually in SAP CRM. For more information on product modeling, see SAP Note
1647059 .

 Note

Make sure that when you create products in SAP CRM, these products have the same ID as the
products in SAP ERP.

 Note

If you run into errors when the products are distributed to SAP ERP, keep in mind that when products
are not created in dialog in SAP ERP, technical settings (product type and logical system) are stored on
the product. When the ERP system accepts product data via middleware, the system looks at these two
fields to ensure that products with the same name from another system or with a different product
type do not overwrite already existing products. In the change transaction for products in the ERP
system, you can reset the technical settings for a product back to their initial values. As soon as you
distribute the product again to the ERP system using middleware, the system sets the values in the
ERP system to those valid at that point in time. If, at a later point in time, there is an attempt from
outside to change the product to a different product type or a different logical system, an error occurs.

● After the business partners, business agreements, and products are available in SAP CRM, migrate your
provider contracts to SAP CRM.
For doing so, we recommend using program CRM_FICA_MIG_PROVIDER_CONTRACT as described in step 1
of section 8.4. Make sure that the data made available in the inbound file for SAP CRM agrees with the
existing contract data in SAP ERP and SAP CC.
The program internally calls the mass-capable interface for creation of provider contracts in SAP CRM
(function module CRM_ISX_BTX_API_CONT_CREATE). Call the function module in a mode (IS_CONTROL-
ACTIVATION = B), in which the data is not replicated online to SAP ERP and SAP CC. Since the data
already exists in SAP ERP and SAP CC, the files created using the program for a migration to SAP ERP and
SAP CC are no longer needed.

 Note

When creating provider contracts in SAP CRM, make sure especially that the contract start date is the
same as the contract start date in the provider contract in SAP ERP and SAP CC.

 Note

In addition, make sure that the cross-system item GUID of the contract items is the same as the GUID
in the provider contract in SAP ERP and SAP CC. The field for this (CONT_ITM_ID) is available on the
interface of provider contracts in SAP CRM as follows:
○ With enhancement package 3 for SAP CRM 7.0 as of support package 05 or by means of SAP
Notes 1997135 and 1996446

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
96 PUBLIC FAQ
 ○ With enhancement package 2 for SAP CRM 7.0 as of support package 12 or by means of SAP Notes
1997134 and 1996446

How do I ensure that the sales area data is included when the business partner is migrated to SAP CRM?

The business partner in SAP ERP does not contain any sales area data. This data exists only in the customer
master in SAP ERP and in the business partner in SAP CRM.

For the industry components Telecommunications (IS-T) and Utilities (IS-U), the ERP business partner and the
customer master are synchronized using the sample customer functions. For the migration of business partner
data to SAP ERP, this means that the relevant data of the customer master must be made available. Only in this
way can you ensure that the sales area data in the customer master is stored and later is included during the
replication of business partner data from SAP ERP to SAP CRM.

For the application area Extended FI-CA (FI-CAX), the sample customer functions are not available. To be able
to synchronize between the business partner data in SAP ERP and the customer master, you can use
customer/vendor integration (CVI) instead. For the migration of business partners to SAP CRM, you have to
distinguish between two scenarios, one with and one without active CVI in SAP ERP.

1. CVI is active in SAP ERP (business partner and customer master are used)
You migrate business partners to SAP ERP.
During the migration of the business partners to SAP ERP, you store data relevant for the customer master
in a Z table.

 Recommendation

During the migration of the business partner data, deactivate the synchronization made using CVI, so
that the customer master is not created synchronously. In a subsequent step, you use the
synchronization cockpit to create the customer masters for the previously migrated business partners.
For this subsequent step, you activate CVI again.

After successfully migrating the business partner data, you synchronize the business partner master
with the customer master using the synchronization cockpit. When doing so, you ensure that the data
you stored beforehand in the Z table is taken into account when the customer master is created, for
example, by transferring this data to the customer master using BAdI CVI_DEFAULT_VALUES.

Once both the business partners and customers have been created in SAP ERP, migrate the business
partners to SAP CRM as described in section 8.1 under step 2a. During this process, assuming CVI is
active, the sales area data is automatically transferred to the CRM business partners using the
middleware.

 Caution

Note: This procedure is only possible with the solution for replicating and synchronizing business
partners in FI-CAX that is available as of enhancement package 7 for SAP ERP 6.0, SPS 05. Up to and
including enhancement package 7 for SAP ERP 6.0, SPS 04, proceed as described in section 2.

2. CVI is not active in SAP ERP (business partner is used, customer master is not used)
You migrate business partners to SAP ERP.
During the migration of the business partners to SAP ERP, you store sales area data relevant for the
business partners in a Z table.
During the migration of the business partners to SAP CRM (see section 8.1, step 2a), make sure that the
sales data previously stored in the Z table is taken into account, by registering a function module with the
needed logic for the middleware.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
FAQ PUBLIC 97
Where can I find information about migration in SAP Revenue Accounting and Reporting?

For more information about migration in SAP Revenue Accounting and Reporting, see the “Migration” chapter
of the application help for SAP Revenue Accounting and Reporting under http://help.sap.com/revacc
(Release 1.1 or higher) .

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
98 PUBLIC FAQ
8 Appendix

8.1 List of Abbreviations

Abbreviation Meaning

FI Financial Accounting

FI-CA Contract Accounts Receivable and Payable

ISMW Industry Solution Migration Workbench

MW Middleware

SAP CC SAP Convergent Charging

SAP CRM SAP Customer Relationship Management

SAP ERP SAP Enterprise Resource Planning

CVI Customer/Vendor Integration

8.2 Additional Information

Document Link

IS Migration Workbench - Data Migration of FI-CA- https://wiki.scn.sap.com/wiki/display/UIndustry/Migration

Based Industry Solutions

Middleware CRM Integration Services | http://help.sap.com/crm <Release>

Application Help Data Exchange and Mobile Technologies CRM

Integration Services

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Appendix PUBLIC 99
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
100 PUBLIC Important Disclaimers and Legal Information
Migration Guide for Offer-to-Cash Based on BRIM Using SAP S/4HANA and SAP CRM
Important Disclaimers and Legal Information PUBLIC 101
www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN