Gain Experience with Business Partner for SAP S/4HANA Conversion

Unit 9: Additional Information and

Recommendations

2PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

CVI – phases

Post Conversion

Configure CVI in your

SAP S/4HANA system for

the synchronization of

BP → C/V

SAP ERP SAP S/4HANA

Preparation

Configure CVI in your

SAP ERP system for the

synchronization of

customer/vendor-to-BP

Conversion

Convert the system

SAP ERP →

SAP S/4HANA

Synchronization

Create and synchronize

business partners for all the

existing customers and vendors

C/V → BP

Objects in

SAP S/4HANA

Leading Object

Roles

Customer

Vendor

Objects in

SAP ERP

Customer

VendorBusiness Partner

The CVI interface ensures the synchronization between the

business partner object and the customer/vendor objects in both

SAP ERP and SAP S/4HANA

CVI implementation is a prerequisite for converting an SAP ERP system to an SAP S/4HANA system.

All customers, vendors, and contact persons must be converted to business partners in SAP ERP before starting system conversion.

3PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

Approach and recommendation

Execute post-

conversion

activities

SAP ERP SAP S/4HANA

CVI implementation

Convert system

from SAP ERP to

SAP S/4HANA

Convert

data

Continue to use customer /

vendor transactions

CVI creates/updates

corresponding BPs

Customer

BPVendor

Contact

Person

Leading Object

Business Partner

Roles

Customer

Vendor

Contact Person

Goal

▪ Not part of the SAP S/4HANA conversion downtime

▪ Not in the critical path of SAP S/4HANA conversion

▪ No last minute surprises

Check MDS_PPO2 and address issues,

if any

Use of transaction BP is not

recommended

XD01, XD02… XK01, XK02…

System conversion may be planned with a time delay

Recommendation

▪ Run first cycle of CVI in sandbox with a copy of production

▪ Analyze data errors and identify correction approaches

▪ Correct all the data errors in production

▪ Execute CVI synchronization DEV → QAS → PROD

4PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

SAP ERP HCM

▪ Employee vendors should be synchronized to BPs of

category “Person” during CVI synchronization

▪ To achieve this you can use standard BAdI

implementation CVI_MAP_BP_CATEGORY of BAdI

CVI_MAP_TITLE

▪ You can create your own implementation of BAdI

CVI_MAP_TITLE with your own criteria as needed

▪ SAP Note 2539457 – CVI & employee vendors in

wrong BP category

5PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

SAP ERP HCM

▪ A new data model based on the business partner is

introduced for employee records in SAP S/4HANA. A

business partner must be assigned to each employee.

▪ 2340095 – S4TWL – Conversion of Employees to

Business Partners

– Attachment “Integration Guide – OP 2020 FPS02.pdf”

6PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

SAP CRM

▪ CRM is implemented in the landscape and you want to

continue to use CRM after converting your SAP ERP

system to SAP S/4HANA

▪ BPs from CRM should be mapped to BPs in SAP ERP

▪ SAP Notes:

– 2283695 – Synchronization cockpit generates

business partners with wrong GUIDs by ignoring

CRM mapping tables

– 2303003 – S4TC BP data exchange between

SAP S/4HANA, on-premise edition and SAP CRM:

Pre-check class for BAdI implementation

CVI_MAPPER

– 2304337 – Description note for Pre Check Class for

Badi implementation CVI_MAPPER

7PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

TCI Note for CVI

▪ Transport-based Correction Instructions (TCI) is a

new channel to ship ABAP corrections with SAP

Notes.

▪ TCI combines the benefits of a support package with

the advantages of SAP Notes

▪ No need to perform any manual steps

▪ Corrects many program errors at once

▪ 2951811 – Transport-based correction instructions

(TCIs) for customer vendor integration (CVI) on ECC

(SAP_APPL)

▪ 2187425 – Information about SAP Note Transport

based Correction Instructions (TCI)

TCIs are delivered through an SAP Note

8PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

How much time do you need?

▪ Time required to complete CVI synchronization

depends on the following and more

– Customer/vendor/BP number ranges complexity

– Customizing consistency between BP and

customer/vendor, including field attributes

– Customer/vendor/business partner data consistency

and quality

This can be a very long process if the master data

needs cleansing, e.g. updating phone numbers/email

address, tax code, etc.

– Customer/vendor enhancements

– Data volume

– Master data/CVI/pre-check/synchronization

knowledge

9PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

Custom enhancements

Customer-specific fields (enhancements) in customer

and vendor need to be included in transaction BP

Integrate these custom fields to business partner so that

maintenance of these fields is possible after moving to

SAP S/4HANA.

SAP Notes:

2309153 –

BP_CVI: Guideline Version 1.14 for customer

enhancements in CVI (customer/vendor integration)

in SAP S/4HANA releases

2295823 –

BP_CVI: Transfer of customer / vendor fields to the

business partner – template source code

1623809 –

Developer documentation for the XO framework

10PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

Additional SAP Notes

▪ IS Utilities: SAP Note 2344100 – S4TWL – CVI

Integration for SAP ISU

▪ Credit Management: SAP Note 2270544 – S4TWL –

Credit Management

▪ IS Retail: SAP Note 2310884 – SAP S/4HANA

conversion for site master

▪ HCM: SAP Note 2340095 – S4TWL – Conversion of

Employees to Business Partners

▪ CRM: SAP Note 2285062 – S4TWL: Business partner

data exchange between SAP CRM and SAP S/4HANA,

on-premise edition

11PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

Useful links

▪ Cookbook

– https://support.sap.com/content/dam/SAAP/SAP_

Activate/S4H.0781%20SAP%20S4HANA%20Cook

book%20Customer%20Vendor%20Integration.pdf

▪ Notes

– 2713963 – FAQ: CVI – Customer Vendor

Integration for system conversion to SAP S/4HANA

▪ Blogs

– BP and CVI in SAP S/4HANA System Conversion

– SAP S/4HANA Business Partner Conversion –

Merge Customer and Vendor into single Business

Partner

– Employee to Business Partner Synchronization

during S/4HANA system conversion

12PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Additional information and recommendations

Key takeaways

▪ Consider implementing CVI ahead of SAP S/4HANA

conversion project

▪ If CVI is implemented ahead of SAP S/4HANA

conversion project, check periodically MDS_PPO2

and address issues, if any

▪ Implement the TCI Note

▪ If you have solutions such as HCM, CRM, etc. in your

environment, review the relevant notes and blogs

▪ CVI Cookbook is a very useful document; use it as

reference material

Thank you.

Contact information:

open@sap.com

© 2021 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or

any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,

and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and

functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason

without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or

functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ

materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they

should not be relied upon in making purchasing decisions.

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.

See www.sap.com/trademark for additional trademark information and notices.

www.sap.com/contactsap

Follow all of SAP