Use
One option for the transfer of data from a sender to a receiver system is to first put the data that should be transferred in a cluster table in the sender system. As these data might occupy a considerable amount of table space in the sender system, it is desirable to clear the cluster table again after the data transfer is completed.
This can be done using this report which runs in the central system and calls function module DMC_DEL_CLUSTER_DATA in the sender system to delete the cluster data.
Per mass transfer and access plan ID, only one batch job should be scheduled, as this report will process all cluster data referring to these IDs. Parallel processing is not supported.
Integration
Usually the report is called by API function module DTL_MT_RT_GEN which itself is called from the process control layer (PCL). In this case, the no-display parameters P_PACKID and P_SESSID are used to maintain an activity records which allows the API function module to return the current status of this report to PCL.
Prerequisites
This report must only invoked after, for the specified mass transfer and access plan, all data have been successfully transferred to the receiver system.
Selection
Input parameters:
- P_MT_ID
- Processing is restricted to the conversion objects of the specified mass transfer ID
- P_ACP_ID
- Processing is restricted to the access plans with the specified ID (in case of an access plan split, this is the ID of the original (unsplit) access plan, and of the “precalculation” which then is created. Thus it is ensured that all access plans resulting from the split are considered)
- P_SESSID
- PCL session ID
- S_TABLE
- Processing can optionally be restricted to the conversion objects with the table names specified by this table
Output
No list output; an application log is created.
