BUSINESS PARTNERS IN S/4HANA

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

Confidential
|
1
• A legal entity is represented with one Business Partner
• Different Business Partner Categories –Organization, Person, Group
• Maximal data sharing and reuse of data which leads to an easier data consolidation
• General Data available for all different business partner roles, specific data is stored for each role
• Several Addresses possible with a default Address
• Flexible Business Partner Relationships possible like contact, married etc.
• Time dependency on different sub entities e.g. roles, address, relationship, bank data etc.
• Fiori User Interface with a specific Customer and Supplier Partner App

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

Confidential
|
2
 Business Partner Data Supplier(Vendor) Data Address Data

Business
Central Data General Data Address
Partner
Roles Company Code
Organization Data Phone
Person Bank Details Purchasing
Org. Data Fax
Group Identification
Numbers Email
Customer Data
Tax Numbers
URL
Industry General Data
Sectors
Company Code
Relationships Data
Sales
Contact
Org. Data
Partners

Address
Address
Usages

ERP
Vendors
ERP
Customers

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

Confidential
|
3
INTEGRATED OBJECT MODEL: CUSTOMER / VENDOR INTEGRATION

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

Confidential
|
4
 S/4 HANA

Customers
Greenfield
BP update
CVI Vendors
BP
Data Services

Synchronization
Webservice

S/4HANA Contacts
IMPLEMENTATION SCENARIOS

LSMW
IDOC
Manual (KN*, LF*)

CVI Configuration

ERP S/4 HANA

ECC to Customers
CVI BP CVI
Customers
Vendors
S/4HANA Vendors
Contacts Conversion
BP Create
Synchronization Contacts
Conversion
Change
(KN*, LF*)

Preparation Synchronization Conversion Post Processing / Test

©2016 SAP SE or an SAP affiliate company. All rights reserved.
Confidential
|
5
• The use of LSMW for data load to SAP S/4HANA is not recommended and at the customer's own
risk. Please use the link below to get more information about the
workaround: https://blogs.sap.com/2016/03/10/uploading-business-partner-data-using-lsmw
• Instead, SAP S/4HANA data migration content called SAP Rapid Data Migration based on SAP
Data Services software is offered to migrate data into SAP S/4HANA (on premise). You can find
more information under the link below:
http://service.sap.com/public/rds-dm2s4op
• In addition, there is a new basic tool included in SAP S/4HANA (starting with SAP S/4HANA 1610)
that is called SAP S/4HANA Migration Cockpit. This tool can be an alternative for smaller projects
and could also be used in addition to the Rapid Data Migration content. For more information, please
click on the link below:
https://blogs.sap.com/2016/06/21/how-to-migrate-to-sap-s4hana
• For more details migration of BP in S/4HANA please see: Note 2287723 - LSMW in SAP S/4HANA
on-premise edition

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

Confidential
|
6
Business Impact
• SAP Business Suite customer can move from different start releases to SAP S/4 HANA, on-premise
edition
• Only SAP Business Suite customer with C/V integration in place can move to SAP S/4HANA, on-premise
edition 1610
• To ensure a successful upgrade all customers/vendors and all contacts which relates to customer or
vendor must be converted to a Business Partner including customers, vendors and assigned contacts
with the deletion flag
• Before you execute the conversion SAP recommends to archive the customer/vendor with the deletion
flag
• It´s recommended but not mandatory that BuPaID and Customer-ID / Vendor-ID are the same

Precondition
• As the Business Partner is used in different applications and the transformation needs also technical
understanding it requires good business and technical expertise
• On-premise start release needs to have a minimum release level e.g. SAP ERP 6.0, EHP 0-7
• S/4 HANA Simplification list must be known
• Conversion Process must be known
©2016 SAP SE or an SAP affiliate company. All rights reserved. |
Confidential 7
• Implement Pre-Checks as described in Conversion Guide for SAP S/4HANA, on-premise edition 1610:
Link
• Archive customer/vendor data with deletion flag (optional)
• SAP recommends to archive the customer/vendor with the deletion flag
• Activate Business Functions
• For the Transformation the Business Functions Business Foundation: Services for Supplier
(CA_BSOAP) must be active.
• Check and integrate Customer/Vendor enhancements (optional)
• BP/CVI Enhancement Cookbook and Extensible Objects (XO) consulting note 1623809
• Necessary CVI Business Partner transformation customizing settings and checks must be performed. For
more details see Conversion Guide for SAP S/4HANA, on-premise edition note 2265093.
• Remove and avoid inconsistent customizing and inconsistent customer data
• Guided customizing settings and mapping checks available
• Clean up or ignore mandatory and country specific field checks (note 2336018 and 2344034)

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

Confidential
|
8
The total CVI transformation time depends on different factors, such as
• BP/CVI/Pre-Check Know-How
• Customer/Vendor/BP number ranges complexity
• BP Customizing consistency including field attributes
• Customer/Vendor/Business Partner Data consistency
• Customer/Vendor Enhancements (Extensions)
• Data volume

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

Confidential
|
9
General info Note 2265093 - S4TWL - Business Partner Approach

Note 2340095 - S4TWL - Conversion of Employees to

Conversion Employees
Business Partners

Exchange between CRM and Note 2285062 - S4TWL: Business partner data exchange
S/4HANA between SAPCRM and S/4 HANA, on-premise edition

Credit Management Note 2270544 - S4TWL - Credit Management

SAP ISU Note 2344100 - S4TWL - CVI Integration for SAP ISU

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

Confidential
|
10
QUESTIONS & ANSWERS

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

Confidential
|
11
 THANK YOU

Contact information:
Sergey Lukin

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