Ansicht
Dokumentation

CNV_TDMS_05_TI_CLUSTFILL_GLS1 - data selection into cluster table for table GLS1 (via GLSP)

CNV_TDMS_05_TI_CLUSTFILL_GLS1 - data selection into cluster table for table GLS1 (via GLSP)

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

Title

Purpose

For object X_GLS1, the normal TDMS approach of filling the cluster data in the sender system by means of a generated MWB module (ACS module) raised problems with poor performance. The reason for this is that the selection of the physical pool table GLSP cannot be done in an efficient way by the DB interface, if the TDMS selections for client, fiscal year and possibly company codes are applied. The corresponding key fields of table GLS1 need to be mapped to the corresponding sub-areas of the generic key field VARKEY of table GLSP. For this purpose, a sort of the table is executed which runs for a very long time if the table contains many records.

In order to avoid this problem, this report was created which selects entries directly from the physical cluster table GLSP (but only the records of GLSP that pertain to the logical table GLS1).
The original selections for fields of GLS1 need to be mapped on corresponding selections for areas of the one generic key field VARKEY of table GLSP. These selections, however, are not directly applied to the original SELECT for table GLSP, but first all GLS1 records are selected and later, those GLS1 records that don't fullfill the further selection criteria are disregarded.

Integration

This report is executed by a specific TDMS activity.

It gets the selections from the PCL selection group by calling function module CNV_MBT_SEL_STRING_GET.

When the filling of the cluster table is finished, the DTL API to execute the data selection is called, with a selection for this one specific object. Thereby the calculation results (meaning, the portions written to the cluster table) are communicated to the DTL.

Prerequisites

Features

Selection

migration package ID (needed to get the mass transfer and access plan ID of the DTL object)

session ID

distinction if cluster should really be filled, or if only a size determination should be done

Standard Variants

Output

Activities

Example






Fill RESBD Structure from EBP Component Structure   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 2317 Date: 20240531 Time: 215346     sap01-206 ( 57 ms )