Module Notes Description
BASIS 2206932 S4TC SAP_APPL : Pre-Check for Material Master Data
BASIS 2324325 Automated pre-implementation steps for SAP Note 2323185
MM Execute Report Executed Note_2324325 || PP|T130F_C|VB|26.02.2019
BASIS 2323185 S/4: migration report for T130F
BASIS 2481837 Creation of MRP areas as preparation of S/4HANA conversion
BASIS 2495067 Creation of MRP areas as preparation of S/4HANA conversion
ABAP 2495067-Report Creation of MRP as preparation of hana s/4 conversion
BASIS 2216528 Pre-upgrade check for storage location migration report
BASIS Activate the Business Function - CA_BP_SOA & CA_SUPPLIER_SOA
BASIS 2216176 Precheck report from business partner
ABAP 2216176- Report
BP S4HANA : Suppress Mandatory BP field groups checks via
2336018
BASIS MDS_LOAD_COCKPIT transaction
BASIS 2345087 BP_BAP: Missing values in required entry fields cause
ABAP 2344034-Pre SAP S/4HANA Automation for Master Data Migration
BASIS 2344034 SAP S/4HANA Automation for Master Data Migration
ABAP 2344034-Post Manual Post-implementation Activity - Zaid
1623677 BP_CVI: Check report for checking CVI Customizing
ABAP 974504-Report ABAP: NOTE 974504 ZCUSTOMER_LINK_CHECK_REPORT by ZAID
ABAP 974504-Report ABAP: NOTE 974504 ZVENDOR_LINK_CHECK_REPORT by ZAID
ABAP 974504-Report ZCUSTCONTACT_LINK_CHECK_REPORT
Business Partner configuration while doing conversion
from ECC to HANA.
Introduction :
While performing SI check, we normally get the error for Business Partner as shown below :
The major errors we usually get is CVI_MAPPING and CHK_CONT_MAP.
Now how do we remove these error?
To remove these errors, follow the below steps :
Main Part :
Step 1: Activate the below objects :
T-Code required to check and activate the objects : SFW5
CA_BP_SOA
CA_SUPPLIER_SOA
Step 2 : Implement the below notes :
2216176 : Pre-check report from Business Partner.
o Report name : PRECHECK_UPGRADATION_REPORT.
2344034 : SAP S/4 HANA Automation for Master Data Migration.
o Report Name : CVI_UPGRADE_CHECK_RESOLVE.
Prerequisites to implement note 2344034 :
o 2336018 : Suppress Mandatory BP field groups checks via
MDS_LOAD_COCKPIT.
o 2345087 : Missing values in required entry field cause posting termination in
mass processing.
1623677 : Check report for checking CVI Customizing.
o Report Name : CVI_FS_CHECK_CUSTOMIZING.
974504 : Inconsistencies in link tables of master data sync.
o Report Names :
ZCUSTOMER_LINK_CHECK_REPORT.
ZVENDOR_LINK_CHECK_REPORT.
ZCUSTCONTACT_LINK_CHECK_REPORT.
Step 3 : Activate Function modules :
Path : SPRO -> Cross application components -> SAP Business Partner -> Data Distribution ->
Activate Function Modules.
Step 4 : Activate creation of post processing order (PPO) :
Path : SPRO -> Cross Application Components -> General Application Functions -> Post
processing Office -> Business Processes -> Activate creation of processing orders.
Pls note that CVI_03 and CVI_04 must be activated after successful synchronization of data.
Step 5 : Activate PPO requests for platform objects
Path : SPRO -> Cross Application Components -> Master Data Synchronization ->
Synchronization Control -> Activate PPO requests for platform objects in the dialog.
Step 6 : Check synchronization objects.
Path : SPRO -> Cross Application Components -> Master Data Synchronization ->
Synchronization control -> Synchronization Objects.
Pls note that, in the above screenshot, the entries highlighted in yellow must exist.
Step 7 : Activate synchronization options :
Path : SPRO -> Cross Application Components -> Master Data Synchronization ->
Synchronization Control -> Activate synchronization options.
The source object and Target object, new entries should be inserted from BP->Customer /
Vendor and Customer / Vendor -> BP.
After synchronization of data, BP -> Customer / Vendor needs to be activated.
Step 8 : Predefined entries that must exist.
T-Code : SM30.
Table : MDSV_CTRL_OPT
The predefined entries are highlighted in yellow :
Step 9 : Number ranges and grouping
Path : SPRO -> Cross Application Components -> SAP Business partner -> Business Partner ->
Basic Settings -> Number ranges and groupings -> Define Number ranges.
SPRO -> Cross Application Components -> SAP Business partner -> Business Partner -> Basic
Settings -> Number ranges and groupings -> Define Groupings and Assign Number Ranges.
Step 10 : Define number ranges for relationships :
Path : SPRO -> Cross Application components -> SAP Business Partner -> Business Partner
Relationships -> Basic Settings -> Define number ranges.
Step 11 : Assign Business Partner roles to Account Groups
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner Settings -> Settings for customer integration -> Define
BP role for direction customer to BP.
SPRO -> Cross Application Components -> Master Data Synchronization -> Customer / Vendor
Integration -> Business Partner Settings -> Settings for vendor integration -> Define BP role for
direction vendor to BP.
As per the account group created, the grouping must assigned accordingly.
Step 12 : Number Assignment (Customer to BP / Vendor to BP)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
Assignment for customer integration -> Assign keys -> Define number assignment for direction
customer to BP.
SPRO -> Cross Application Components -> Master Data Synchronization -> Customer / Vendor
Integration -> Business Partner settings -> Settings for vendor integration -> Field Assignment for
vendor integration -> Assign keys -> Define number assignment for direction vendor to BP.
Step 13 : Activate Customer value mapping (contact person) (Optional)
Path : SPRO -> Cross application components -> Master data synchronization -> Customer /
vendor integration -> Business partner settings -> settings for customer integration -> Field
assignment for customer integration -> Assign Attributes -> Contact person -> Activate
assignment of contact persons.
Step 14 : Assign department numbers for contact person (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign department
numbers for contact person.
Step 15 : Assign functions of contact person (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign functions
of contact person.
Step 16 : Assign authority of contact person (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign Authority
of contact person.
Step 17 : Assign VIP indicator for contact person (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign VIP
indicator for contact person.
Step 18 : Assign Marital Status (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign marital
statuses.
Step 19 : Assign legal form to legal status (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign legal form
to legal status.
Step 20 : Assign Payment cards (Optional)
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign payment
cards.
Step 21 : Assign Industries.
Path : SPRO -> Cross Application Components -> Master Data Synchronization -> Customer /
Vendor Integration -> Business Partner settings -> Settings for customer integration -> Field
assignment for customer integration -> Assign attributes -> Contact person -> Assign Industries.
Here, we need to assign the industry system to both Outgoing industry and Incoming industry as
highlighted in yellow.
Step 22 : Run PRECHECK_UPGRADATION_REPORT
Go to SE38 and enter PRECHECK_UPGRADATION_REPORT and then execute.
After selecting all the Checks, EXECUTE. Pls note to Uncheck the “Display Results for Current
Client”. If any error which pops up, we need to assign or configure accordingly in all the
clients.
Step 23 : Synchronization Cockpit
Transaction : MDS_LOAD_COCKPIT
We can enter the range or the account group of customer / vendor and execute. A message will
pop up in the screen and then we need to click the tab Monitor. If there are no errors, it will reflect
a green signal and if there are any errors, it will reflect in RED signal and the same needs to
corrected accordingly.
If the configuration is done perfectly, you will not find any errors :
If there are any errors, then the status will be RED and we need to follow the direction given
(which pops up along with the error).
Now,
When we run the SI check in SE38 -> /SDF/RC_START_CHECK , we need to check whether all
signals are in GREEN / YELLOW and if yes, then SI Check for BP is successfully completed.
Conclusion :
So, in order to remove those 2 errors related to Business Partner during SI check, we need to
follow the above 23 steps which will help in resolving the error.
----------------------------------------------------------END----------------------------------------------------------
The Below steps are for 1511 but most of the steps will remain same for other versions too.
Business Partner – SAP Strategic Object Model
General data are shared across different roles
One business partner could perform multiple roles, e.g., customer and vendor (supplier)
One business partner could have multiple addresses
Time-dependency object attributes and relationships
Provide harmonized architecture
Customer/Vendor Integration (CVI) component ensure the synchronization between the
Business Partner object and the customer/vendor objects
Check and activate Business Functions
CA_SUPPLIER_SOA
CA_BP_SOA Switch ‘VENDOR_SFWS_SC1’ and switch ‘VENDOR_SFWS_SC2’ have to be
active for the vendor contact person’s data to be synchronized with BP contact person’s data
Before you begin the BP conversion from an SAP ERP system to an SAP S/4 HANA system, you
have to answer the questions Whether the Business Partner ID and Customer-ID /Vendor ID
should be the same in the S/4 HANA System?
Business Partner Master Data Setup Proces
1. Setup BP General Data
Select General Business Partner Role and Grouping, here this grouping is linked with customer/
vendor Number range and this Grouping is key in linking the Vendor/Customer & BP groups as
well as number ranges which is explained below in detail.
Table BUT000 will be updated once General BP role is completed.
2. Setup FI Vendor
BP Role FLVN00 FI Vendor extension enables Invoice to be posted directly in FI.
Here vendor master table LFA1 and LFB1 will be updated.
FI document can be posted but cannot create PO as purchasing data is not yet extended so for
extending purchasing data use ROLE FLVN01
Table LFM1 will be updated once the BP Role is extended to Supplier BP Role
Once BP is extended to Purchase Organization using BP Role FLVN01 the vendor can be used
PO can be created.
Setting up Customer
Table KNA1 will be updated once BP Role is extended to FI Customer and Finance can start
posting directly in FI for example FB70 etc.
Extend Customer to Sales Area
BP Role FLCU01 is extended to sales area.
Table KNVV updated with Sales view details and henceforth Customer can be used in sales
area.
Extend Customer to Credit Segment
able UKMBP_CMS_SGM updated
Note- S4 Hana credit Management setting should be enabled to check the credit limits for
customers
Maintaining Tax details
You can add customer Tax details in Identification tab of BP which will enable you to enter tax
details with tax category and tax number and once you save this detail in BP the same you can
see in KNA1 table , you can check whether these tax categories exists in
table V_TFKTAXNUMTYPE & V_TFKTAXNUMTYPEC & also check field BP status that these
tax number fields are optional/mandatory not hidden..
Customizing
Business Partner Customizing
Activate the PPO Request for the synchronization object Business Partner
Cross-Application Components–> Master Data Synchronization –> Synchronization Control–>
Synchronization
Active Synchronization between Customer/Vendor and BP is active
Define BP Roles
Assign BP Role to BP Role Category
Cross-Application Components–> SAP Business Partner–>Business Partner–> Basic Settings –
> Business Partner Roles–> Define BP Roles
This setting is already available in standard delivered system for standard roles.
Account Group /Number Range Mapping
I am explaining below with an example of requirement for setting up One Time Vendor and One
Time Customer Account and as a summary we need to setup Vendor/Customer Account group &
assign number ranges to respective Vendor/Customer account group as it was required in
classic ERP environment.
Additionally BP grouping is mapped with Vendor/Customer account group
Define Account Groups Vendor
Financial Accounting (New)–> Accounts Receivable and Accounts Payable–> Vendor Accounts–
> Master Data–> Preparations for Creating Vendor Master Data
Assign Number Ranges to Vendor Account Groups
Similarly for Customers we need to define Account Group and assign number range to Customer
account groups.
Define Number Assignment for Direction BP to Vendor/Customer
Cross-Application Components–> Master Data Synchronization–>Customer/Vendor Integration –
> Business Partner Settings –> Settings for Vendor Integration –> Field Assignment for Vendor
Integration–> Assign Keys
Define Number Assignment for Direction BP to Vendor
Define BP Number Range and assigning to BP Grouping
Cross-Application Components–> SAP Business Partner–> Business Partner–> Basic Settings –
>Number Ranges and Groupings
Define Number Ranges-BP
Define Groupings and Assign Number Ranges
Create Number Ranges for Vendor/Customer
Financial Accounting (New)–> Accounts Receivable and Accounts Payable–> Vendor Accounts–
> Master Data –> Preparations for Creating Vendor Master Data
Create Number Ranges for Vendor Accounts
Similarly create Number Ranges for Customer Accounts.
How to maintain Field Status ?
Refer SAP KBA Note 2565164 to know how to maintain field Status for BP
This will enable to start work with new Business Partner in S4 Hana Enterprise Management
Environment.
Do you want to know how to convert existing Vendor/Customers while
doing system conversion from ECC to S/4HANA ?
Very detailed information for deep dive you can refer this CVI cookbook link from Christoph Dutz,
Michael Foo and Alexander Roebel which focuses on BP conversion from ECC to S4HANA
https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H.0781%20SAP%20S4HANA%20C
ookbook%20Customer%20Vendor%20Integration.pdf
Do you want to know how to handle custom fields added in
customer/vendor master in ECC during conversion to S/4 ?
In SAP Business Suite (ERP 600 and Enhancement Packages), customer master data and
vendor master data transactions such as FD01, FD02, FD03, XD01, XD02, XD03, FK01, FK02,
FK03, XK01, XK02 and XK03 have been enhanced by customers with additional fields using
BAdI. In the customer and vendor master dialog transactions, these fields were integrated by
adding additional sub-screens to the existing screens.
Moving to a SAP S4HANA release, traditional customer/vendor master transactions are made
obsolete and replaced by the business partner transaction BP. Because of this, all extension-
specific fields have to be integrated into the business partner.
PDF document attached with OSS note 2309153 provides a guideline how customers can
transfer the enhancements they have made in the customer/vendor transactions to transaction
BP, so that a maintenance of these fields remains possible after the upgrade to a S4HANA
release.
----------------------------------------------------------END----------------------------------------------------------
SAP Note 2265093 explains this prerequisite for converting an SAP ERP system to SAP
S/4HANA.
----------------------------------------------------------END----------------------------------------------------------
