Ansicht
Dokumentation
RLMDB_EXPORT_TECH_SYS - Export technical systems from a source CIM namespace
Fill RESBD Structure from EBP Component Structure SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Purpose
With the report RLMDB_EXPORT_TECH_SYS, you can export a complete technical system description from SLD or LMDB into a ZIP file. The ZIP file can be imported into another SLD or LMDB. Because references to external data are exported, such an import may partially fail with error messages.
Integration
The report is used instead of RLMDB_TRANSFER_TECH_SYS when no network connection can be established to the target SLD or LMDB.
Prerequisites
In transaction SM59, create an SLD destination with the following characteristics:
- Destination type: HTTP Connections to External Server (Type G).
- Use name prefix LMDB_SLD_ (example: LMDB_SLD_TRANSFER_SRC).
- 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).
- 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.
If you want to run this report as background job, start transaction FILE and define the actual file system values for logical path 'AI_LMDB_REPO_EXPORT_PATH' and logical file 'AI_LMDB_DATA_EXPORT_FILE'. The job exports the data into the specified server directory.
Features
Export a set of technical system descriptions from a source CIM namespace.
Selection
- The first block of input parameters defines the target HTTP destination and target CIM namespace.
-
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: AS ABAP and
.SystemNumber. .SystemHome. ) or by short text (example: AS ABAP and on ). 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. - 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 export result later on.
You can view the application log with transaction SLG1: object = AI_LMDB, subobject = CLUSTER_BUILDER and EXPORT_BUILDER.
You can activate expert logging in transaction SM30: view = V_LMDB_LOG_CONF, domain = LDB, subobjects CLUSTER_BUILDER and EXPORT_BUILDER.
Standard Variants
Output
The output lists system selection statistics and the file being exported. Further detailed information is in the application log.
Activities
Select the source 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.
The resulting ZIP file may be imported into SLD or LMDB. Importing the file into SLD may run into multiple error messages due to missing association ends or conflicting data in SLD. It depends on the use case whether further exports are needed or an upfront deletion of data is required to reach the desired result. Importing the ZIP file into LMDB executes the same conflict handling as described for report RLMDB_TRANSFER_TECH_SYS.
Example
ROGBILLS - Synchronize billing plans CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 4403 Date: 20240520 Time: 062335 sap01-206 ( 74 ms )
