S/4HANA Business Partner BDT configuration comparison between clients
At BP transaction in your S/4HANA system you might notice that some descriptions of tabs, sections etc. are not correct or missing. That could happen in some cases where you convert your ECC system into a S/4HANA system. Another case could be after setting up a new client.
SAP offers a comparison tool to compare 2 clients in regards of BDT settings and offers the user the opportunity to include the differences in a transport that can then be sent to the new client.
This blog is relevant for all releases working with Business Partner, meaning ECC 6.0 onwards. Main focus is SAP S/4HANA on-premise and private cloud edition, which is the most relevant working with Business Partner.
Screenshot below shows wrong descriptions at a screen (tab) and a screen section. Target at this example is to compare the BDT setup of screenshot client (target client) with BDT setup of standard delivery client 000 (source client) to correct wrong descriptions. Source or target client could be any client in your system.
Run comparison tool
An RFC connection must be established between the two desired clients.
Run Transaction BDT_COMPARE or execute program BDT_COMPARE at source client.
|RFC Destination||Name of RFC Connection||Type in the name of the RFC connection or use the drop down to receive a list of all RFC connections.|
|Application Object||The Object you wish to do a comparison on.||
Type in the Application object for which you want to produce a comparison of BDT customizing tables.
most relevant objects:
|Applications||These fields limit the applications within an application object that will be check.||If you do not want a full comparison of the Application object, use these field to limit the comparison to only those applications you would like checked.|
|Cross-Application Settings||Check box to include BDT customizing that covers Cross-Application settings.||Check Cross-Application Settings.|
|Customizing Tables||Check Box to include customizing tables||Check Customizing tables|
|Language||Language for description texts||leave blank to compare all languages|
|Display the Same||Check Box to include customizing settings that are identical in both clients||
Check if you would like to view those items that are the same in both clients. This box or one of the 4 that follows it must be checked, that is why this is listed as conditional.
I would not recommend checking this box. It is likely to produce a very long list. Since this program is usually used to detect differences, there will not usually be any added value to checking this box.
|Display Different||Check Box to include customizing settings that are different between the two clients being compared.||
Since you are usually running this program to identify differences, you would usually check this box.
Check if you would like to view those items that are the difference between the two clients being compared. This box or one of the 4 other boxes it is group with must be checked, that is why this is listed as conditional.
|Display existing fr source sys||Check Box to display table entries that only exit in the Source System.||
Since you are usually running this program to identify differences, you would usually check this box
Check this box if you would like to see entries that only exits only in the source system. This box or one of the 4 other boxes it is group with must be check, that is why this is listed as conditional.
|Display existing fr target sys||Check Box to display table entries that only exit in the Target System||Check this box if you would like to see entries that only exits only in the target system. This box or one of the 4 other boxes in it’s group with must be check, that is why this is listed as conditional.|
After execution you will see the result list.
Result list is splitted into 3 areas – only two are shown at my example.
There are the same key entries in customizing tables at both clients but with different configuration.
There are key entries in customizing tables in target system only.
At target client there is one custom field at BP transaction (KNA1-ZCUST) which is not implemented at source client (000). The reason for many lines just for one custom field implementation is caused by BDT configuration settings of Field Group and View configuration and assignment.
Custom field implementation is described at this blog post.
Blue entries (unfortunately not shown at my example)
There are key entries in customizing tables in source system only.
If you use client 000 as source client and there are entries in source client only, meaning in this case there are configuration entries in delivery client which are not in target client you should import them into target client using transport request.
Comparison details and action
Double klick at result line will give you more details.
As you can see at client 000 there is another displayed title at screen BUP110. Original delivered title is ‘Address’. To take over original title close the pop-up first.
Take over source value into transport request
Mark the line in question and push the button ‘Transport Request for Selected’.
Create a new transport request or enter an already existing one.
Setup of specific line selected is now put into your transport request.
Next line is just a customized setting in target system to avoid calling a function module at BDT event DELE2.
You can ignore this due to the fact this is a wanted difference.
Proceeding to the next text difference I want to correct.
To add this correction to your transport request mark this line and push the button ‘Transport Request for Selected’.
Import Transport Request into target client
To import your Transport Request into your target client use your usual transport procedure or use transaction SCC1 in your target client.
Test comparison changes in target client
Run transaction BP in target client to check your correction.
Tab name and section description has been updated