Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Hi All,

The BDTCompare Program is a standard delivered ABAP program that compares BDT (Business Data Toolset) customizing tables between two clients.   This program should not be confused with the Customizing-Cross System Viewer (Transaction OY19), which provides a view of standard customizing tables between two r/3 systems.  This program produces a report that can be used to validate the completeness of BDT configuration between a new client against an existing client (for example, the golden configuration client).    Once the compare is complete the program also offers the user the opportunity to include the differences in a transport that can then be sent to the new client. 

Input – Required Fields

Field Value/Comments

RFC Connection

An RFC connection must be established between the two desired clients.  The Basis team creates the RFC connection.


Output - Results

Comments

Configuration Comparison Report

The system provides a working report of all configuration table differences.

Tips and Tricks

Enter the transaction code (OY19 or SCU0) in the Command Field for faster access to the transaction.

Use  to enter or advance the process.

Use  to go back to the previous process selection

Use  to exit to main menu.

To obtain a description of a specific field, highlight the field in question and click the  icon or press F1.

Use  to save new input or changes.

Use  to execute transaction.

Procedural Steps

1.1.       Access ABAP Editor and run  BDT_Compare:

Via Menus

Tools ->ABAP Workbench -> Development -> ABAP Editor -> Customizing Data

Via Transaction Code

SE38

1.2. On screen “ABAP Editor: Initial Screen”, enter information in the fields as specified in the table below:
 

Field Name

Description

R/O/C

User Action and Values

Comments

Program

Program Name

R

Type in the name of the program, BDT_COMPARE.



Execute Button

R

Select this radio button to start the comparison program.


 (Note:  On above table, in column “R/O/C” ; “R” = Required, “O” = Optional, “C” = Conditional)

To create a comparison for CD, select the radio button “Choose Components” and click. 

1.3. On the screen "BDT Comparison and Transport of Control Tables", enter information in the fields as specified in the table below:


 

Field Name

Description

R/O/C

User Action and Values

Comments

RFC Destination

Name of RFC Connection

R

Type in the name of the RFC connection or use the drop down to receive a list of all RFC connections.

Pick the RFC connection of the client you wish to compare against.

Application Object

The Object you wish to do a comparison on.

R

Type in the Application object for which you want to produce a comparison of BDT customizing tables.


Applications(From and To)

These fields limit the applications within an application object that will be check.

O

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.

If you do not enter anything into these fields, all applications within the Application Object with be checked.

Cross-Application Settings

Check box to include BDT customizing that covers Cross-Application settings.

O

Check Cross-Application Settings.


Customizing Tables

Check Box to include customizing tables

O

Include Customizing tables


Display the Same

Check Box to include customizing settings that are identical in both clients.

C

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 length 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.

C

Check if you would like to view those items that are the different between the two clients being compared. This box or one of the 4 other boxes it is group with must be check, that is why this is listed as conditional.

Since you are usually running this program to identify differences, you would usually check this box.

Display existing from Source sy

Check Box to display table entries that only exit in the Source System.

C

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.

Since you are usually running this program to identify differences, you would usually check this box

Display existing from Target Sy

Check Box to display table entries that only exit in the Target System

C

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.

Since you are usually running this program to identify differences, you would usually check this box


Execute Button

R

Hit the execute radio button to begin the comparison.


(Note:  On above table, in column “R/O/C” ; “R” = Required, “O” = Optional, “C” = Conditional)

1.4. The results of the compare  will be listed in a table.  Differences will be highlighted in Red.  Entries existing only in the source system will be highlighted in Blue and entries only exiting in the target system will be highlighted in yellow as shown below:

 

 

1.5. To view any particular variance, right click twice on the line the variance occurs. A pop-up window will appear to display the difference between the table entries in the two systems as shown below:

In the above example, the first entry has been compared.  The first two entries in the pop-up box indicate the clients and objects being compared.  The third box indicates the entry in the first field.  In this case, both clients have an entry for FLDGR 0061, however, the field X_CUSTAUS for this field group has a different value in client 100 vs client 315 which is clearly indicates that there is descrepencies between clients. That is the way we compares the BDT Configuration and its Tables. How to check the lost Configuration by Transport Request. Please check the link below which tell about "How to Identify Lost BDT Configuration By Transport Request ".

Thanks & Regards,

Venkat Sesha

  • No labels