Ansicht
Dokumentation

RWLC_PROCESS_IN_PARALLEL - Load Distribution and External Parallel Processing

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Title

Workload Distribution and External Parallel Processing

Purpose

Many reports cannot be parallel processed. They only process their worklist sequentially. The time available for processing the data in a critical time frame can often only be adhered to by parallel processing the report.

It is possible to parallel process reports that are not considered to be "parallel processing-compliant" and this is done by manually maintaining a large number of variants for a parallel process. But this statistical division of the worklist can lead eventually to parallel jobs with an uneven workload. The individual variants therefore often have very varied runtimes. The shorter runtime, which is the aim of dividing up the workload manually, may therefore approach the same sort of runtime as is required for sequential processing. Therefore, statistical division of the workload is not always the solution to parallel processing criteria (for example, increasing number ranges in purchase orders, deliveries).

By choosing the transaction WLCPAR, you are able to automatically parallel process reports that cannot be parallel processed with the report RWLC_PROCESS_IN_PARALLEL. This is done by embedding the report that is to be parallel processed in a report that has been generated by the report RWLC_PROCESS_IN_PARALLEL, and then saving it as a separate report. This separate report, which provides the functionality for external parallel processing and for reports that are to be parallel processed, can be planned like any standard job as long as a variant is maintained for this report.

A worklist is created in a preprocessing run and then distributed among the parallel jobs. Selection variants are created for these jobs with which the report can be started automatically. The workload is distributed every time the report is called so that all the parallel jobs take more or less the same amount of time and therefore have a much shorter runtime than sequential processing or manual distribution.

You must also create a variant Vr in the report R that is to be parallel processed. This is necessary for defining the worklist that is to be processed.

Using the report RWLC_PROCESS_IN_PARALLEL, generate a separate report Rpin the development system (transaction WLCPAR) for every report R that has to be parallel processed. Rp preselects the worklist, distributes the workload among the parallel jobs, creates selection variants Vrp (which are derived from the variant Vr) for the parallel jobs and to start the parallel jobs for report R.

The generated report Rp is automatically entered into a change and transport request with which the report can be transferred to the production system. You do not need to make any more Customizing settings in the production system.

This means that you must maintain the Mandatory Options and the Additional Selection Optionsviews in Customizing in the development system. You can maintain the view Default Values for Selection Screen in Customizing; you can/must define the current values in the variant Vp.

You must plan the generated report Rp, rather than the report R, in the production system with one of the variants Vp that was defined for this report.

Ensure when you are planning follow-on jobs that once the generated report Rphas been processed, all the reports R have been processed. Therefore, a planned follow-on job can start immediately after.

Integration

Prerequisites

Reports that are to be parallel processed externally have to fulfill the following prerequisites:

• The selection screen must contain at least one selection option.

• You must be able to define the worklist in advance: a maximum of 4 tables can be read generically whose keys match at least the field number and the data type. Dependent tables must copy and, if necessary, enhance the key from the higher level table.

PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 5328 Date: 20240601 Time: 061719     sap01-206 ( 119 ms )