Kontakt

Ansicht
Dokumentation

RBDLSMAP - Tool: Update Logical System Names

RBDLSMAP - Tool: Update Logical System Names

CL_GUI_FRONTEND_SERVICES - Frontend Services   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

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

Note the following:

  • 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.
  • 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. If this is the case, you will receive an information message (message number BI 455), which you can confirm in order to continue the conversion. The old system name is not changed during conversion. Instead, you add the new system name. As soon as the conversion process is complete, including in all partner systems, you should 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 - that is, changing the logical system name in all application tables of all partner systems.

  • Creating a new system by database copy. In this case, call the new system a different name to 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 Logical System Name (old) field. Enter the new name in the New Logical System Name field.

It is advisable to carry out the conversion in test mode first. If you select the Test Run checkbox, 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 checkbox 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 this 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 who 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 field is only relevant for conversion. To improve performance, this value should be as large as possible, provided 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 can not be excluded. This table is checked and converted at the start of the conversion process. Note that even if only one table is converted, the definition of the client for the logical system is also converted, provided 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.

The program dynamically determines all database tables that use certain domains (LOGSYS and EDI_PARNUM). If there are applications where the tables do not reference these domains, this data is not converted. Using the option Determine Relevant Tables Again, you can have the tables determined once again if new tables were created or delivered with logical system names that are not yet taken into consideration.

SAP and customers have the option of starting further programs in connection with the conversion of locigal systems (views BDLSEXZ, BDLSEXT). Using the option Start Conversion of Tables with Special Treatment, you can control whether programs that were defined with the class Objects with Special Handling should be started.

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 that the old entries in cross-client tables are retained.

After the program has been successfully executed, the system creates a list that shows 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 CALEand the subobject LOGSYSNAME.

Note: Starting the conversion in background processing
  • The program 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, provided the database roll area is sufficient.

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

  • The test run for certain parameters is executed once only. 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 different clients, 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 certain 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.

  • The option Determine Relevant Tables Again should only be used if new tables were created or delivered with logical system names. This means that subsequent or parallel conversions do not need to use this option in order to determine tables again.

  • Use this program to convert all tables in one process if the option Start conversion of tables to be handled specially is active. If you are using several processes in parallel or one after the other, it is sufficient that programs for objects to be handled specially (such as SAP Office objrects) are started only once.

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 committed 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 for client copy

This program is called during client copy in the Generate and Check phase; no authorization check is performed. 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 - that is, for all client-specific table entries. If entries of a table have not been converted, or not converted fully, an error message appears in the transport log. The reason for this could be that this table already contains the old logical system name or that errors have occurred with 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. This warning indicates that the conversion of such table entries cannot be performed during client copy - that is, the old table entries are retained. 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 that are relevant for the conversion or tables in which data has been converted are displayed. The level numbers 2, 3 and 4 in the logs identify error messages and warnings, as well as normal messages.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example






Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 12551 Date: 20240520 Time: 122805     sap01-206 ( 235 ms )