Professional Documents
Culture Documents
Content
Objective
Executive Summary
Q&A
-2-
Objective
Objective
-4-
Executive Summary
Executive Summary
Vendors and customers must be migrated to business partner frame work in S/4 HANA. Transaction BP is the
single point of entry to create, edit, and display business partners, vendors and customers
It is highly recommended to perform vendor and customer Business partner pre-check and conversion
activities in a clean data environment (ideally Production copy )
Existing Customers and vendors in ECC 6.0 EHP1 or higher can be migrated to Business Partner framework
even before starting S/4 system conversion (BP Conversion can be done ahead of time to ensure that the
system is ready for S/4 migration)
It is recommended but not mandatory that Business Partner ID and Customer-ID / Vendor ID as the same
( For example, Vendor # is 14732 , it is recommended to have BP # as 14732)
Before running the S/4-SUM tool , Business partner configurations ,pre check activities and customizing errors
and data errors must be resolved
SAP provides Transaction MDS_LOAD_COCKPIT to migrate vendors and customers in to Business partner
Frame work. Transaction MDS_PPO2 provides information about customizing /Data errors for vendors and
customers during BP conversion
During BP conversion activities, External number range is assigned to Business partners to facilitate business
partner creation with vendors and customers with existing ECC number range and after BP conversion , BP
number range is set as internal
For Vendors and customers with overlapping number range, Business partner can be created for one of the
master data and business partner can be inked to vendor or customer using transaction FLBPD2 or FLBPC2
-6-
Business Partner Concept
Business Partner Concept
Transaction BP is the single point of entry to create, edit, and display business partners, vendors and customer. For customers and
vendors conversion in to Business partner, Business partner Category type “Organization” is used
Business Grouping
Each Business partner must be allocated to Business partner grouping before BP creation. Business partner grouping drives the
and number range for Business partner (Similar to account group concept in ECC)
-8-
Business Partner Conversion Approach
Business Partner Conversion Approach in S/4 system conversion
CHK_POST_CON_ASSIGNM Checks configuration under Business Partner under Cross-Application Components ->
SAP Business Partner -> Business Partner Relationships -> Contact Person
- 12 -
Preparation Synchronization Post activities
Business partner pre check activities needs to be completed before starting the BP conversion activities
PRE CHECK_UPGRADATION_REPORT
This report highlights the status\missing signals in form of traffic lights
- 13 -
Preparation Synchronization Post activities
1) In this configuration we specify existing ECC system number range for Customer and vendor
account groups and make the number range configuration as External.
Configuration
Rationale 2) This external number range helps to create vendors and customer as Business partners in
S/4 system with existing ECC number range
- 14 -
Preparation Synchronization Post activities
1) In this configuration we create Business partner grouping for each vendor account group
and each customer account group
Configuration Rationale
2) It is recommended to use Business partner account grouping as existing vendor and
customer account group so it is easy for the user while creating business partner
- 15 -
Preparation Synchronization Post activities
1) In this configuration we link applicable Business partner Roles to Business partner account
group
2) Business Partner Role-Similar to Company code/Purchasing view/Sales org view in ECC
Customers: FLCU00-Company code and FLCU01-Sales Org view
Configuration Rationale Vendors: FLVN00-Company code view and FLVN01-Purchasing view
For example, if ZSLD account group has Company code and Sales org view in ECC , we link
FLCU00 and FLCU01 roles to the BP account group
- 16 -
Preparation Synchronization Post activities
1) In this configuration we link applicable Business partner Roles to Business partner account
group
2) Business Partner Role-Similar to Company code/Purchasing view in ECC
Vendors
Configuration Rationale
FLVN00-Company code view
FLVN01-Purchasing view
For example, if ZVEN account group has Company code and purchasing view in ECC , we link
FLVN00 and FLVN01 roles to the BP account group
- 17 -
Preparation Synchronization Post activities
- 18 -
Preparation Synchronization Post activities
1) In this configuration we link Business partner grouping and account grouping and select
Configuration Rationale Same number range . This configuration helps to create business partner with Same number
range of customers and vendors
- 19 -
Preparation Synchronization Post activities
It is recommended to activate all four sycn options and this is important to ensure CVI linkages
Configuration Rationale
- 20 -
Preparation Synchronization Post activities
- 21 -
Preparation Synchronization Post activities
We must ensure that the entries in Assign Department Numbers for Contact Person are available in
Customizing for Business Partner under Cross-Application Components -> SAP Business Partner -> Business
Partner Relationships -> Contact Person -> Define Departments
- 22 -
Preparation Synchronization Post activities
We must ensure that the entries maintained in Assign Department Numbers for Contact Person
are available in Customizing for Business Partner under Cross-Application Components -> SAP
Business Partner -> Business Partner Relationships -> Contact Person -> Define functions
- 23 -
Preparation Synchronization Post activities
We must ensure that the entries maintained in Assign Department Numbers for Contact Person are available in
Customizing for Business Partner under Cross-Application Components -> SAP Business Partner -> Business
Partner Relationships -> Contact Person -> Assign Authority of Contact Person
- 24 -
Preparation Synchronization Post activities
We must ensure that the entries in maintained in Assign Department Numbers for Contact Person are available
in Customizing for Business Partner under Cross-Application Components -> SAP Business Partner -> Business
Partner Relationships -> Contact Person ->Define VIP entries
- 25 -
Preparation Synchronization Post activities
We must ensure that the entries in Assign Marital Statuses for are available in Customizing for Business Partner under
Cross-Application Components -> SAP Business Partner -> Business Partner -> Persons -> Marital Statuses -> Maintain
Marital Status
- 26 -
Preparation Synchronization Post activities
We must ensure that the entries in Assign Legal Form to Legal Status are available in Customizing for Business Partner
under Cross-Application Components -> SAP Business Partner -> Business Partner -> Maintain Legal Forms
- 27 -
Preparation Synchronization Post activities
It is needed to assign the card types of payment cards for the customer master records to the
Configuration Rationale payment card types for the business partner
We must ensure that the entries in Assign Payment Cards are available in Customizing for Business Partner under Cross-
Application Components -> Payment Cards -> Maintain Payment Card Type
- 28 -
Preparation Synchronization Post activities
Industry hasn’t been defined in the industry system. This industry needs to be mapped to the
Configuration Rationale new industry in the Customer/Vendor integration customizing by the definition of the mapping
for outgoing and incoming industries
We must ensure that the entries in Assign Industries are available in Customizing for Business Partner-> under Cross-
Application Components -> SAP Business Partner -> Organizations -> Maintain Industry Systems and Industries
- 29 -
Preparation Synchronization Post activities
- 30 -
Preparation Synchronization Post activities
2232687 - SAP BP: China Tax Number/Missing entry in customizing table TFKTAXNUMTYPE_C.
Configuration Rationale
- 31 -
Business partner Conversion-
Synchronization Phase
Preparation Synchronization Post activities
System creates Business partner GUID in table for CVI_VEND_LINK for vendors and CVI_CUST_LINK for vendors and
customers after completion of MDS_LOAD_COCKPIT execution
- 33 -
Preparation Synchronization Post activities
Transaction MDS_LOAD_COCKPIT can be re executed once the data/customizing errors have been resolved
- 34 -
Preparation Synchronization Post activities
Customizing Issues
Master data and customizing errors related to customers and vendors must be resolved before SUM tool execution
- 35 -
Business Partner Conversion –Post activities
Preparation Synchronization Post activities
IMG Path- Cross-Application Components -> SAP Business Partner Business Partner Basic
Configuration Path settings Number Ranges and Grouping->Define Number Ranges
Business partner number range changed from external to internal post BP migration
Configuration Rationale
IMG Path- Cross-Application Components -> SAP Business Partner Business Partner Basic
Configuration Path settings Number Ranges and Grouping->Define Grouping and Number Ranges
- 37 -
Preparation Synchronization Post activities
- 38 -
Preparation Synchronization Post activities
- 39 -
Vendors and customers with overlapping
number ranges
Vendors and customers with overlapping number ranges
Background:
There are situations where in same number range is often utilized for customers and vendors. Business partner conversion in S/4
HANA has some challenges when migrating overlapping number ranges
As One of the available option, BP conversion can be done for either customer or vendors using MDS_LOAD_COCKPIT and later
Business partner can be linked to either existing customer or vendor using following transaction
- 41 -
Business partner-OSS note reference
2363892 - Linking Customer and Vendor to a single Business Partner during initial load before upgrade to S/4
2000099 - CVI fails with error R1231: "Form of address &1 not designated for organizations“
2371986 - SAP BP: Business Partner is not updated with roles from table CVIC_CUST_TO_BP2 and
CVIC_VEND_TO_BP
- 42 -