
Converting Logical System Names
Purpose
Due to the increasing componentization and openness of R/3, logical systems must be able to communicate with each other beyond the boundaries of ALE integrated systems, for example, for in central user administration. Logical systems must therefore have unique names, even those outside the ALE integrated system.
As of Release 4.5A SAP provides a tool to automatically convert the names of logical systems in all application tables, master data tables and control data tables.
As of R/3 Release 4.6C this tool is integrated in the client copy.
This includes both client-dependent and client-independent tables.

Prerequisites
Users of this program must have the authorization object B_ALE_SYS in their user profile.
We recommend that only the ALE system administrator is given this authorization.
Process Flow
To carry out the conversion, start Transaction
BDLS .The default name displayed is the old logical system name.
Enter the new name of the logical system.
You can simulate the conversion in the report’s test mode. Here only the tables in question and the number of the tables entries to be converted are displayed. The table entries in the database are not converted. You can evaluate the results and assess the runtime.
The report carries out the tasks below:
· LOGSYS
· EDI_PARTNUM
Transporting Changes
The table contents are not transported.
Conversion of EDI Tables
When EDI tables are converted, the report also determines the table fields containing the value LS (logical system).for the partner type. The associated logical system names are converted too.
Exceptions
If the new logical system name is maintained on the local R/3 System (where the names are being converted) in table TBDLS, the logical system name cannot be converted. You must assume that the new logical system name is already being used (for example in the ALE distribution model).