Kontakt

Ansicht
Dokumentation

RBDLSMAP_OLD - Report RBDLSMAP_OLD

RBDLSMAP_OLD - Report RBDLSMAP_OLD

General Data in Customer Master   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program converts a logical system name, which has already been defined in the system, to a new name. The program determines all relevant tables for the conversion, and converts the corresponding entries.

Note the following points:

  • It is not possible to convert logical system names in a productive system.
  • While the conversion program is running, no other activities can be executed in the system, including communication with other systems.
  • All IDocs in the system must be processed, because the logical system name could be contained in the IDoc data record. Logical system names in IDoc data records are ignored by the conversion.
  • The conversion takes place in the current client. In some circumstances, the logical system name may also need to be converted in all partner systems. The tables for the definition of logical system names (TBDLS, TBDLST) receive special treatment. After you have entered the system names, the system checks whether they have already been defined. The old system name is not changed in conversion. Instead, you add the new system name, and when the conversion process is complete, including in all partner systems, manually delete the old system name from the tables.
  • Do not manually change the logical system names in the relevant tables. If you do, the application documents will not be found, or will only partially be found.
Note: Authorization
  • To execute this program, you need authorization for converting logical system names (authorization object B_ALE_LSYS).

You have the following options for converting logical system names:

  1. Convert Client-Specific and Cross-Client Tables
Typical applications:
  • Renaming the logical system name, therefore changing the logical system name in all application tables of all partner systems.

  • Creating a new system by database copy. In this case, give the new system a different name from the original system.

  1. Convert Client-Specific Tables
An example application is converting the logical system name after client copy.

Choose the appropriate option for your application.

On the initial screen, enter the logical system name that you want to convert in the Old Logical System Name field. Enter the new name in the New Logical System Name field.

It is advisable to carry out the conversion first in test mode. If you select the Test Run radio button, the system first analyzes all the relevant tables, and determines the number of entries to be converted. This information is displayed as a list. If the radio button Check Whether New Names Exist in Tables is selected, the system checks whether the new logical system name already exists in application tables. If this is the case, a warning is displayed in the results list. Check the table in which the logical system name is found, and determine whether these entries need to be converted. If you do not want to convert these entries, cancel the conversion.

The conversion also applies to tables for communication partners, which are identified by partner number and partner type. If the partner number and the logical system name are the same, these table entries are also converted.

The value in the Number of Entries per Commit is only relevant for conversion. To improve performance, this value should be as large as possible, as long as the database roll area is sufficient.

In the selection screen Tables for Conversion, you can select and exclude the tables to be converted, so that you only select and convert certain data. Table T000, for assigning the client to the logical system, receives preferential treatment and cannot be excluded. This table is checked and converted at the start of the conversion process. 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 converted tables are found, because they refer to the new system names, while application documents in tables that have not yet been converted are not found, because they still refer to the old logical system names. It is therefore advisable to convert all tables in one step.

Check the results of the conversion. For example, a * character at the end of the table name indicates a cross-client table. If you use Convert Client-Dependent and Cross-Client Tables, the existing entries in these tables are replaced by the new logical system names. If you do not want to replace these entries, choose Convert Client-Specific Tables, so the old entries in cross-client tables are retained.

After the program has been successfully executed, the system creates a list of which tables and fields have been determined for the conversion, and how many entries are relevant or have been converted. This is displayed in the application log. To display the logs, call transaction SLG1, with the object CALE, and the subobject LOGSYSNAME.

Note: Starting the conversion in the background
  • The program RBDLSXYZ can also be executed in the background, if you assign values to the appropriate entry fields. In this case, all the security questions during the run are confirmed with Yes.

Note: Performance
  • The value in the Number of Entries per Commit field is only relevant for the actual conversion (not for the test run). To improve performance, this value should be as large as possible, as long as the database roll area is sufficient.

  • Depending on the size of the dataset in the system, the conversion process can last a long time.

  • The test run for certain parameters is executed once, and the result of the test run is used for the actual conversion. To improve performance, you can execute the program for the actual conversion at the same time. This parallel processing can take place in a different client, or in the same client for different tables.

  • If you are sure that the new logical system name has not been used previously, you can deactivate the existence check in a test run.

  • If you definitely do not want to convert same tables, or you want to handle some objects individually, use transaction BDLSC to exclude these tables or define the objects. Note that defining objects in this way affects all clients, including the order in which the objects are to be handled.

Note: Restart capability
  • If the conversion process is terminated for any reason, it can be restarted, because the converted data is committed as a table or in sections within a table.

Note: Checking and changing the communication settings
  • Asynchronous communication: Partner profile

When a logical system name is converted, the partner name is also converted in the corresponding partner profile, and the partner status in the partner profile is set to inactive.
After conversion, check the partner profile (port and RFC destination). Change these if necessary, and activate the changed partner profile.
  • Synchronous communication: RFC Destination

After the logical system name has been converted, check the RFC destination for synchronous communication, and change it if necessary.

Starting the Program During Client Copy

This program is executed during the client copy process, in the phase Generation and checking, but without authorization checks. Before the conversion can take place, the logical system name must have been defined in the source client and a new name defined for the new client.

Note: Scope of data
The conversion takes place in the current client, which means that all client-specific table entries are converted. If the entries in a table have not been converted, or are not completely converted, an error message is produced in the transport log. The reason for this could be that this table already contains the old logical system name, or errors occur in the database change during conversion. In this case, you may need to subsequently process the table manually.
For cross-client table entries, a warning is displayed in the transport log indicating that the conversion of these table entries is not carried out in client copy. This means that the old table entries remain unchanged in the client copy. Depending on the applications of the new client, subsequent processing of these tables may be necessary. The new entries for the new logical system name can be manually extended.
Note: Results
After the program has been successfully converted, the results of the conversion are displayed in the transport log. Only the tables are displayed that are relevant for the conversion, or in which data has been converted. The level numbers 2, 3 and 4 in the logs identify error messages and warnings, as well as normal messages.

Requirements

Output

Example






Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 11350 Date: 20240601 Time: 080329     sap01-206 ( 203 ms )