Show TOC

Procedure documentationSynchronizing Urgent Changes in Parallel Systems

 

You want to schedule the import of transport requests created from urgent changes into your parallel test and production systems by using periodic background processes. In doing so, you ensure that the state of each system is consistent.

Prerequisites

  • A change cycle with the status “Active” exists. Only those urgent changes that are assigned to this change cycle are included in the automatic import.

  • For one development system, you have defined and activated multiple, parallel follow-on systems (test systems).

  • For one development system, you have defined and activated multiple, parallel production systems.

  • The urgent change has been imported into the production system where the request for change originated.

    Note Note

    Urgent changes that are imported into the production system where the request for change originated are not imported into other parallel production systems.

    End of the note.
  • The corresponding change document has been completed.

  • The tracking process of the central system knows that the urgent change has been imported into the first production system.

Procedure

In the task list, select the Synchronize Urgent Changes from Other Test Systems task for the test system or the Synchronize Urgent Change task for the production system, and execute it.

Result

After the task has been executed, a message is written to the application log. You can view this log in transaction SLG1. In the Object field, enter /TMWFLOW/CMSCV and in the Subobject field, enter SCHEDMAN.