Title
Program for Comparing and Transporting BDT Settings Between DifferentClients and Systems

Purpose
All table entries are compared that are found in the standard area menuBUPT behind the menu option "Application Object Control" and"Application Object". The relevant tables are assigned to the packageBUPA and have the name TBZ*. They are of the category C and areclient-specific.
The compared entries are output in a list. The entries can be selectedand are placed if wished in a Customizing transport request. It must beensured that the transport request leads into the target system.

Integration
The BDT application is an important term as a subordinate term of theBDT application object. The program uses the application as thesmallest meaningful unit for which the relevant control settings can begrouped and transported. The starting point is the naming convention(BDT Manual) with the help of which all BDT entities like screens,object parts, datasets, etc. are assigned to an application.
For a given application all entities are compared that qualifythemselves via the relevant naming convention. The assignments betweentwo entities are regarded as belonging to the application, if at leastone of the two entities belongs to the application. Example: If theapplication BUP is selected in the application object BUPA, then thesection BUP010 itself, the assignments to the views that it contains onthe one hand, and on the other hand the assignments to the screens inwhich it is contained, are also selected Here it is not importantwhether the views or screens for their part are assigned via theirnames or the application BUP.
The completeness of the comparison to an application depends on thenaming convention being taken into account consistently.
Table entries that are directly dependent on the entities (e.g. texttables) automatically belong to the same application. This also appliesto the field groups, screen fields and the assignments to the screenfields that depend directly on the view of an application.

Prerequisites
Basically, an RFC connection should be defined via SM59 (even if thesource and target system differ only in the client).
The function module BDT_SELECT must exist in the target system.
The coding is operational only as of 4.6.

Features

The user has to state an application object.
If the applications are not specified, all the entries that arerelevant for the stated application object are selected. In this caseit would make sense to set the flag for cross-application settings, inorder to transport all the settings necessary for the applicationobject.
In addition, one or more applications can be specified. In this caseyou should usually not carry out a transport of cross-applicationsettings, and should not set the corresponding flag.
The user can determine whether he wants to display the same entries,different entries, entries found only in the source system, or thosefound only in the target system.
It is also possible to display only the settings belonging to alanguage.

Output
The comparison result is output in a list that is based on the ALV GridControl. The output result can be formatted accordingly.
A detailed list is displayed for each list line by means of adouble-click.
Any entries can be marked (hold down the Ctrl button). The action"Transport" in the menu of the list causes a Customizing request and aCustomizing task to be created for transport (SE10) and to be writteninto the tables E071 and E071K.
It is possible to select entries for a transport request not only ifthey are different or only available in the source system, but also ifthe entries are only available in the target system. In this case theentries are deleted along with the appropriate key in the targetsystem. In order to enable a complete transport, the transport ofconcurrent entries is also possible.