Kontakt

Ansicht
Dokumentation

RLMDB_TRANSFER_OTHER_SYS - Transfer systems not falling into the technical system category

RLMDB_TRANSFER_OTHER_SYS - Transfer systems not falling into the technical system category

rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With the report RLMDB_TRANSFER_OTHER_SYS, you can transfer a complete non-technical system description from a source CIM namespace to a target CIM namespace (SLD or LMDB). The content of the source namespace overwrites the target namespace with all data belonging exclusively to this system. Non-exclusive data is also transferred but not deleted in the target namespace.

Any additional CIM properties of the target namespace are not deleted at all. The deletion of CIM instances can be protected for data differing between SLD and LMDB, for example the manual LMDB changes made in the host editor.

Integration

The full automatic content synchronization between SLD and LMDB transfers the data of a CIM namespace. The synchronized data cannot be limited by any system. A ranking defines the conflict resolution for the full automatic content synchronization. For individual system data, this conflict resolution may not lead to the desired result.

With this report, you can transfer individual non-technical systems and overrule the standard conflict resolution for a system. The report synchronizes systems regularly if you schedule it as a periodic batch job.

Prerequisites

In transaction SM59, create SLD destinations with the following characteristics:

  • Destination type: HTTP Connections to External Server (Type G).
  • Use name prefix LMDB_SLD_ (example: LMDB_SLD_TRANSFER_SRC and LMDB_SLD_TRANSFER_TRG).
  • Set the destination settings:
  • On the Technical Settings tab, enter the target system settings as follows:
    Target Host: name of the SLD target host
    Service No.: HTTP Port of the SLD target host
    Path Prefix: the path to select and call the HTTP request handler (leave empty or enter /sld/cimom)

  • On the Logon & Security tab, under Logon with User, enter user and password for Basic Authentication. The user in the source RFC destination must have at least read authorization for SLD (role/group SAP_SLD_GUEST). The user in the target RFC destination must have write authorization for all objects in the landscape description (role/group SAP_SLD_CONFIGURATOR).

  • On the Special Options tab, enter the HTTP setting as follows:
    HTTP version: Select HTTP 1.0.
    Compression Status: Select Inactive to disable compression.
    Status of Compressed Response: Select No to disable compression response.
    HTTP Cookies: Select Yes (All) to accept cookies.

  • Test the connection.

Features

Transfer a set of non-technical system descriptions from a source to a target CIM namespace. In simulation mode, all necessary changes are calculated, but not executed.

Selection

  1. The first block of input parameters defines the source HTTP destination and source CIM namespace.
  2. In the second block, enter the type of the system to be transferred, and select several systems or system name patterns. You can select systems by a technical name (example: XI domain and domain..) or by short text (example: XI domain and Domain ). Only the technical name is unique. In both cases, you can enter search patterns with wildcards (* and +) and you can use all other ABAP selection options.
  3. The third block of input parameters defines the target HTTP destination and target CIM namespace.
  4. In the last block, you can switch on and off flags influencing the execution mode. Protecting manual LMDB changes and LMDB outside discovery data is recommended for an LMDB target namespace. Protecting extended SIDs and associations into the CR Content is recommended in any case. Writing of an application log is useful to review the transfer result later on.
    When you deselect the simulation flag, the system information will be transferred to the target namespace.

You can view the application log with transaction SLG1: object = AI_LMDB, subobject = CLUSTER_BUILDER

You can activate expert logging in transaction SM30: view = V_LMDB_LOG_CONF, domain = LDB, subobjects CLUSTER_BUILDER and DELTA_BUILDER.

Standard Variants

Output

The output lists system selection statistics and the changes that were executed or would be executed (in simulation mode). Further detailed information is in the application log.

Conflicts with existing data in the target CIM namespace can occur during change execution. In this case, the data is incompletely transferred. Details of the conflict are in the application log if the target SLD version is 7.1 or higher. An SLD with version 7.0x does not support this logging, only the number of failed operations is logged for such a target SLD. Incomplete data transfer is not always an issue. The conflict analysis and repair depends on the conflict type:

·,,Missing data in the target CIM namespace cannot be associated. A typical example is a missing CIM element of the software catalog, for example CIM instances of SAP_Product or SAP_SoftwareComponent.
In this case, import the latest CR content, as described in SAP Note 669669, and repeat the system transfer.
Ignore the transfer conflict if the missing association is not required in the target CIM namespace.

·,,Existing data in the target CIM namespace also belongs to another system. A typical example is a duplicate, with differing system description originating from a different source CIM namespace. In this case, remove the duplicate from the target namespace and repeat the system transfer. Ignore the transfer conflict if the colliding association is not required in the target CIM namespace.

Activities

Select the source and target CIM namespace parameters, the system type, and a list of systems. You can select systems by text pattern, or by selecting from the value help. (Note: the value help may be hidden by the horizontal scroll bar when selecting multiple systems.)

Store the selection as report variant to use it in batch processing. Typical runtime ranges from a few seconds to a few minutes, so online processing may time out for more than a few systems.

Run the report in simulation mode first if you are unsure about the selected systems. This is especially helpful if you select systems by text pattern.

Example






TXBHW - Original Tax Base Amount in Local Currency   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 6945 Date: 20240531 Time: 114842     sap01-206 ( 126 ms )