Ansicht
Dokumentation

DMC_TRANSFER_PERFORMANCE_EVAL -

DMC_TRANSFER_PERFORMANCE_EVAL -

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

Purpose

This report prepares a data transfer with a few conversion objects that aims at evaluating the data transfer speed.

At first, an MWB project and subproject are created. Their identifiers are identical and start with ZPER in customer systems or PERF in SAP systems, followed by a GUID to ensure uniqueness.

Then, a mass transfer is created with the first available (not yet defined) ID starting from ZP0. It includes the sample objects for which the transfer throughput should be determined.

Then the conversion objects are defined and the corresponding runtime objects generated. The reading type is set to 5 (cluster technique), and the data to be transferred are not written into the original tables in the sender system but directly into the cluster table from which they are transferred. This is achieved by specific coding that replaces the coding normally generated for the ACS module.

As a last step, the "access plan calculation" (actually filling the cluster table) is started by scheduling the corresponding batch jobs.

It is recommended to run this report as a batch job.

Integration

As soon as this job has ended, jobs for the access plan calculation will be scheduled. You should check if these jobs have run successfully. After that, you can use report DMC_TRANSFER_PERFORMANCE_JOBS (or press button "Transfer Jobs" in transaction MWB_TRANSFER_PERFORM) in order to schedule batch jobs for the data transfer the performance of which should be evaluated.

Prerequisites

The rfc destinations for sender and receiver system must have been defined, and these systems need to have the DMIS add-on with support package 10 installed.

Features

Selection

It is required to specify the rfc destinations of sender and receiver system. Also the SAP basis release of sender, receiver and central system must be specified.

For the data portions, the block size in bytes must be specified. Concerning the total data volume per table, we recommend a default size of 8 GBytes. But this size can also be adjusted.

Standard Variants

Output

Activities

Example






CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 2415 Date: 20240531 Time: 015815     sap01-206 ( 70 ms )