Ansicht
Dokumentation

RDRF_MESSAGE_REOUT - Repeat Data Replication

rdisp/max_wprun_time - Maximum work process run time   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Purpose

You use this report to repeat data replication that you have already performed. For example, if errors occured during a previous replication run.

The report creates one or multiple outbound messages to be sent to a target system based on an outbound implementation that you have defined to be used for a particular replication model. You can create the outbound messages directly or in the background.

Integration

The system takes into account the implicit filters and implicit checks that you defined and activated in Customizing, as well as the explicit filters that you defined on the SAP Easy Access screen under Processes and Tools for Enterprise Applications -> Master Data Governance -> Data Replication -> Define Filter Criteria. If required, you can override the explicit filters during manualrequests.

Prerequisites

• You have defined the required replication model and assigned appropriate outbound implementations to it. In addition, when using Manual replication mode, you have activated explicit filters for the outbound implementation.

• You have authorization to execute this report.

The system also performs an authorization check for the Replication Model and Outbound Implementation fields. This check determines whether you are authorized to change a message. This check is controlled via the DRF_ADM authorization check.

Features

You can use this report to repeat the data replication for the following data:

• All
  Data replication is repeated for all data that matches the specified criteria and the specified run.

• Erroneous
  Data replication is repeated for data where an error ocurred previously in the specified run.

To increase the performance during mass data processing, you have the option of running processes using a logon/server group.

Selection

You can select multiple outbound implementations. This enables different outbound messages to be processed together.

Standard Variants

Output

The report creates the corresponding XML outbound message for the local Integration Engine. You can monitor the connection status of the Integration Engine via transaction SXMB_MONI. An application log informs you about the data processing status. You can subsequently call up this application log on the SAP Easy Access screen under Processes and Tools for Enterprise Applications -> Master Data Governance -> Data Replication -> Analyze Replication Log.

Activities

Example

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

Length: 3371 Date: 20240520 Time: 110008     sap01-206 ( 63 ms )