Kontakt

Ansicht
Dokumentation

RLMDB_TRANSFER_PRODUCT - Transfer product descriptions from source to target CIM namespace

RLMDB_TRANSFER_PRODUCT - Transfer product descriptions from source to target CIM namespace

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

Purpose

With the report RLMDB_TRANSFER_PRODUCT, you can transfer a complete definition of a product or product version 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 product or product version. 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.

Integration

The full automatic content synchronization between SLD and LMDB transfers the data of a CIM namespace. The synchronized data cannot be limited to individual product definitions. In rare cases, an update of individual product definitions is required.

With this report, you can transfer individual products or product versions and overrule the standard conflict resolution for such data. The report synchronizes products regularly if you schedule it as a periodic batch job.

Copying individual product definitions can repair or destroy the CR content of an SLD or LMDB. If the source namespace contains a validated content with the same CR content version as the target namespace, you can repair the target CR content with this report. Applying this report to differing CR content versions most likely destroys the consistency of the target CR content.

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 or LMDB target host
    Service No.: HTTP Port of the SLD or LMDB target system
    Path Prefix: the path to select and call the HTTP request handler (leave empty or enter /sld/cimom for SLD or enter /lmdb/cimom for a remote LMDB)

  • 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 component repository (role/group SAP_SLD_ORGANIZER).

  • 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 product definitions 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, select several products or product name patterns. You can select products by a technical name (example: MOB_ADDON_ERP) or by short text (example: MOBILE ADD-ON FOR ERP). 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. If you enter a value for the version, only matching product versions are selected (no wildcards supported here). Checking the option to transfer all directly included software component versions is helpful for new products, but increases the runtime strongly.
  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. Writing of an application log is useful to review the transfer result later on.
    When you deselect the simulation flag, the product definition 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 product 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 referenced, but missing CIM element of the software catalog, for example CIM instances of SAP_Product or SAP_SoftwareComponent. 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 product definition. 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 and a list of products. You can select products 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 products.)

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 products.

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

Example






TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 6827 Date: 20240520 Time: 082011     sap01-206 ( 120 ms )