Ansicht
Dokumentation

SAPLBDRC - ALE: Determination of Recovery Objects

General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Description

This transaction should only be started in the system that has been reset and restarted.

Enter the date and time when the system was restarted.

Choose a sufficiently large safety margin, to cover the possible time difference between when the IDocs were created in the sending system and when they were received in the receiving system.

• Example:

IDocs were created in the sending system at 14.00. They were dispatched in batch at 16.00. They were written to the database in the receiving system at 16.05. So a margin of 2 hours and 10 minutes is sufficient. (the larger the margin, the surer you can be that all IDocs will be included).

The transaction can only be continued once you have selected the systems to be recovered (@0A@->@08@) and you have checked the system settings (@0A@->@08@).

Requirements

Before you start this transaction, the message types RCYFET, RCYRSP and RCYLST must have been entered in the distribution model, for example, with a new model view (Maintain distribution model). This model view must have been distributed to all the systems.

The partner profiles have been generated in all the systems in accordance with this model view. (Generate partner profiles) or have been maintained manually (Define partner profiles).

Example

System S1 was recovered and reset to the status on 31.01.1997 at the time 00:00:00. System S2 is a partner system that exchanged data with system S1 after the 31.01.1997 and time 00:00:00. The exchanged data is ascertained when the transaction is started.

Before the transaction is started the following message flows into the distribution model, for example, SUBSYSTEMS are defined

S1 - RCYFET -> S2
S1 <- RCYRSP - S2
S1 - RCYLST -> S2

The model maintained in system S1, for example SUBSYSTEMS, is sent to system S2.

The partner profiles are generated in both systems S1 and S2.

The transaction is started in system 1. Here you enter in separate fields the values for the date (31.01.1997), time (00:00:00) and safety margin (02:10:00) between the systems, as all batch jobs in systems S1 and S2 were started every two hours (allowing 10 minutes for the transfer time).

System S2 is selected. The system settings are checked in S1 and S2. If the check is OK, the objects for recovery are determined (F8).

Finally, the system reports that one IDoc for message type RCYFET has been created.

As soon as the IDocs for the message types RCYFET, RCYRSP and RCYLST have been successfully posted in systems S1 and S2, the next step Processing Recovery Objects can be started.

We recommend you use the ALE Audit technology from the partner system for the message type RCYFET, so that the recovered system is notified when the process has been succsssfully completed in this partner system.

CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3764 Date: 20240531 Time: 015852     sap01-206 ( 75 ms )