121163 - BDLS - Converting logical system names

Symptom

You need a program to convert logical system names. The old report RBDPROSE does not completely convert the logical system names.

Other Terms

ALE, logical system, logical system name, RBDLSMAP, BDLS, RBDPROSE, BD80

Reason and Prerequisites

The new report RBDLSMAP does not yet exist in the standard system.

Solution

The old report RBDPROSE should no longer be used. For the new Transaction BDLS, you can find a patch on the server machines sapservX in the directory
           general/R3server/abap/note.0121163.

Customers who need the tool and have access to the servers can download the patch from there.
Two languages, German and English, are available for the patch.
Details on how to manually download a patch can be found in Note 0013719.
As of SAP Release 4.5B, the tool is contained in the standard delivery.
Further notes:
The conversion of the logical system name has far-reaching consequences. Therefore, we recommend that you contact an SAP consultant before starting it. The following points should be observed:

• In productive systems the conversion of the logical system name is not provided. The reason is that the relevant database tables are dynamically determined by certain domains (LOGSYS and EDI_PARNUM). If there are applications where the tables do not reference these domains, the data are not converted. Another reason is that certain data could be saved as part of fields in cluster or pool tables with regard to the logical system. Such data are not converted.

• During the run of the conversion report, no other activities may be carried out in the system.

• All IDocs in the system must be processed beforehand since the logical system name could be contained in the IDoc data record. The logical system name in IDoc data records would not be taken into account for conversion.

• The conversion is carried out in the current client. Therefore, the process must also be carried out in all partner systems.

• If the new logical system name already exists in the system, it can cause errors for tables in which the logical system is key field or unique index (for example, COFIO1). In this case the number of converted entries is smaller than the number of selected entries. Manual postprocessing must be carried out in this case, and if necessary the conversion must be started again.

• The conversion report that was dynamically generated from Report RBDLSMAP (up to SAP Release 6.10) can also be run in the background, if the corresponding input fields are filled with values. In this case, all confirmation prompts are automatically confirmed with Yes during the run; on the othe rhand, user interaction is required in the online execution. You must pay attention to this during the conversion itself.

• If a termination occurs due to the database roll area, you should either restart the roll area as high as possible or reduce the parameter 'Number of entries per commit' from the default value. In order to gain performance, this parameter should be as great as possible.

After successfully completing the conversion, synchronize the table buffers in the server.
Export the list of conversion results (on the screen) to a local file for test purposes.