Show TOC

Procedure documentationScheduling the Automatic Import of Urgent Changes Locate this document in the navigation structure

 

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

Prerequisites

  • A maintenance cycle exists whose status is Active. Only those urgent changes that are assigned to this maintenance 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

Execute the report /TMWFLOW/SCMA_BTCH_SYNC_UC as follows:

  1. As mandatory import parameters, specify the following:

    1. System ID and the client of the system into which you want to import the urgent changes

    2. Name of the SAP Solution Manager project that is assigned to the active maintenance project

  2. Using the Job Wizard (transaction SM36), schedule the report /TMWFLOW/SCMA_BTCH_SYNC_UC as a background job.

    Note Note

    If the report ends in an error, check the batch log file (transaction SM37).

    End of the note.

Result

After every run of the batch job, 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.