Transaction code BDLS is a Tool: Conversion of Logical System Names. This program is used to convert a logical system name, which has already been defined or used in this system, to a new name. The program determines all the relevant tables and converts the corresponding entries.
Options
1. Convert client-specific and cross-client tables
Changing the logical system name. This means changing the logical system name in all application tables of all partner systems. Creating a new system by database copy. In this case, you need to give the new system a different name to the original system.
2. Convert client-specific tables
A typical application is converting the logical system name after client copy.
On the initial screen, enter the logical system name that you want to convert in the Old Logical System Name field. Enter the new logical system name in the New Logical System Name field.
It is advisable to start the test mode first. If you select the radio button Test Run, the system first analyzes all the relevant tables and determines the number of entries to be converted. These are displayed in a list. If the radio button Check Existence of New Names in Tables is selected, the system checks whether the new logical system name already exists in the application tables. If it does, a warning is displayed in the results list. Check the table in which the new logical system name is found, and determine whether you need to convert these entries. If you do not, terminate the conversion.
The conversion is also relevant for communication partners identified by partner number and partner type. If the partner number and logical system name are the same, these table entries are also converted.
The value in the field Number of Entries per Commit is only relevant for conversion. To improve performance, this value should be as large as possible, depending on the limits of the database roll area.
In the selection screen Tables for Conversion, you can select and exclude tables for conversion, and therefore target specific data in the database. Table T000, for assigning the client to the logical system, receives special treatment and cannot be excluded if you use Convert client-specific and cross-client tables. This table is converted last. Note that if only one table is converted, the definition of the client for the logical system is also converted, if this assignment is defined in the current client. This means that the application documents in the converted tables can be found because they refer to the new logical system name, while application documents in tables that have not yet been converted are not found, because they still refer to the old logical system name. It is therefore advisable to convert all the tables in one step.
Check the conversion results. For example, the character * after the table name means that it is a cross-client table. If you choose Convert Client-Specific and Cross-Client Tables, the existing entries in the tables are replaced by new logical system names. If you do not want the entries to be replaced, choose Convert Client-Specific Tables, so that the old entries in cross-client tables remain unchanged.
After the program has been successfully executed, a list is produced showing which tables and fields have been determined for conversion, and how many entries are relevant or have been converted. This process is recorded in the application log. To display the application logs, call the transaction SLG1 with the object CALE and the subobject LOGSYSNAME.
Note
• Logical system names cannot be converted in productive systems. While the conversion program is running, no other activities can be performed in any part of the system, including communication with other systems.
• All IDocs in the system must have been processed, because the logical system name could be a part of the IDoc data record. Logical system names within IDoc data records are not considered in conversion.
• The conversion takes place in the current client. Sometimes, you also need to convert the logical system name in all partner systems. The tables for the definition of logical system names (TBDLS, TBDLST) receive preferential treatment. After you enter the system names, the system checks whether they have been defined. The old system name is not converted, and the new system name is entered in its place. Once the conversion process is complete, including in all partner systems, you then need to manually delete the old system name from all the tables.
• Do not make any manual changes to the logical system names in the relevant tables. If you do, the application documents will no longer be found.
