Show TOC

 Synchronization Report: Process Flow

Use

The systems carry out the following steps when the synchronization report is run.

Features

Preparatory Steps in the Decentralized System

  1. Check the configuration.

    The local parameters are determined.

  2. Open the synchronization log.

    If this is not possible, the synchronization report is terminated.

  3. Check the connection to the partner system.

  4. Determine the synchronization report.

    If a report is already running, the second one is terminated.

  5. Determine the mode.

    If the mode is offline , the counter for the transient transition is reset and the administrator is informed.

  6. Check the tRFC queue.

    If IDocs are available, the transient transition is started.

Preparatory Steps in Both Systems

  1. Perform the connection test.

  2. Create the application log remotely in the partner system.

    From now on, all messages are entered simultaneously in both systems.

  3. Retrieve the transports, if required.

    If new transport files are available, they are copied from the central system to the decentralized system. The administrator is informed.

    If the system is offline, the synchronization report ends immediately.

  4. The synchronization report is started, first in the decentralized system, then a shadow copy is started in the central system in the opposite direction.

  5. Set the partner profile to Collect.

  6. Evaluate the change pointers, the message types, and the ALE status. If required, IDocs are created.

  7. Evaluate the ALE status.

Communication Steps

The following steps are carried out depending on whether transports are available or not.

  • If transports are not available, the IDocs are processed according to their priority in the decentralized system (this process is initiated by the central system).

  • If transports are available:

    1. The IDocs are transferred (initiated by the decentralized system).

    2. The transports are retrieved and imported.

Final Steps

  1. Status check to determine whether the systems are still online.

  2. Reset the counters for the transient transition.

  3. Set the partner profiles to Send Immediately.

  4. CCMS monitoring evaluated in both systems and entries made in the application log.

  5. If the synchronization report is terminated, it is restarted immediately and the partner profiles are reset to Send Immediately.

  6. The application log is completed in both systems, table GS_REMOTE:SYSTEM_LOGSYS is unlocked, and the application log is displayed.

The synchronization log can be displayed using the Analyze Application Log application (transaction /ISDFPS/SLG1).

Once the synchronization report has been run, the synchronization log is displayed. If errors occurred during the synchronization run, work items are generated automatically and forwarded to the defined users. The synchronization log generated by the report is assigned to these work items.

Steps that have been carried out successfully are identified as such and are also recorded in the synchronization log.