Show TOC

Process documentationProcessing Urgent Changes Locate this document in the navigation structure

 

This process makes urgent changes in your production system. This transaction is only permitted within a maintenance cycle. The urgent change is mainly used for fast implementation, for example, if you want to fix an error in existing functionality. The change is transported into the production system faster than a normal change.

Prerequisites

  • A request for change has been created and approved, and a change document of the category Urgent Change has been generated by the system. The request for change has been released for development.

  • The request for change is linked to a maintenance project. Urgent changes can only be used in maintenance projects.

  • If you have been using SAP Solution Manager before, you have configured the dialog window to create transport requests. For more information, see Configuring the Dialog Window for Creating Transport Requests in Urgent Changes.

Process

  1. The change document is forwarded to the designated developer, who calls it up in the Change Management work center, and sets the status to In Development in the WebClient UI when he starts making the change. To do so, he chooses   Action   Set To In Development  , and saves the change document.

  2. Triggered by the action, the system displays a dialog box and asks the developer to create a transport request and a task. He can assign the relevant system and client and change the request owner from his user to another user, if required.

    Note Note

    Various options are available in this dialog box:

    • Create several tasks at once

    • Create tasks for other users

    • Create Customizing or Workbench requests

    End of the note.
  3. Via a link provided in the Landscape assignment block, the developer logs on to the development system directly.

  4. The developer makes the urgent change in the assigned development system, saves the change to the assigned task, tests the change, and releases his task in the transport request, in the development system.

  5. The developer releases the transport request manually in the Transport Management assignment block. The original transport is exported from the development system. No Transport of copies transport request is created, as in the Normal Change process. For more information, see Processing Normal Changes.

    When releasing the transport request, a code inspector check is run. For more information, see Using the Code Inspector in Urgent Changes.

  6. The developer forwards the urgent change to testing, by choosing   Actions   Pass Urgent Change To Test  . He then saves the change document.

  7. The change document is now in status To be Tested and the original transport is imported into the test system.

  8. The IT operator calls up the document from the Change Management work center, or from his worklist in the WebClient UI. He assigns the document to a tester, who in turn can see it in his work center or worklist.

    Note Note

    If the tester is maintained as a business partner in the system, he is automatically entered as the current processor.

    End of the note.
  9. The tester (or another user to whom the tester role is assigned) logs on to the designated test system via the Landscape assignment block, to check the urgent change.

    If the change contains no errors, the tester chooses   Actions   Confirm Successful Test   in the change document, which is then in status Successfully Tested. The change manager can now change the status of the urgent change to Authorized for Production.

    If errors occurred during testing, the tester returns the change document to the developer, by choosing   Action   Reset Status to In Development  , so that the urgent change can be corrected. This new change has to be tested, and the process is repeated, that is, a new transport request needs to be created and the problem can be solved.

  10. The change manager approves the urgent change for import into the production system, by choosing   Action   Release Urgent Change for Production  , and forwards the change document to an IT operator. The status of the document is now Authorized for Import.

  11. The operator calls up the document via the work center or his worklist in the WebClient UI. He triggers the import of the urgent change into the production system, by choosing   Action   Import Urgent Change into Production System  . The status of the urgent change is now Productive.

  12. The requester (or the change manager) confirms that the change has been made by choosing   Action   Confirm Urgent Change  .

    The system updates the status of the request for change to Implemented. This is only true if all follow-on change documents related to the request for change are in final status. The last change document related to a request for change that has the status Completed updates the request for change.

  13. The Change Manager chooses   Action   Complete Urgent Change   which sets the document in the final status Completed. The change document is now locked for editing.

    Note Note

    To import a transport request for urgent changes into parallel systems, use the report /TMWFLOW/SCMA_BTCH_SYNC_TEST. For more information, see SAP Note 817289.

    End of the note.

    After the transport request of the urgent change document is imported into the QA and production systems, the transport request remains in the import buffer, so that the changes are not overwritten by other transport requests in the normal change cycle.

    Note Note

    You can choose between two tasks list variants, with different transport sequences into the production system: Use SAP0 if you want to use urgent and normal changes in your landscape, and SAP1 if you use urgent changes only (in a maintenance system landscape in which no project development takes place). You make these settings in the project administration, on the Change Management tab page.

    End of the note.

    Note Note

    If you want to set multiple change documents to the next status (from Approved for Import to Productive, for example), execute the batch job CRM_SOCM_SERVICE_REPORT. You can also use this report to import all changes at a scheduled time, into the follow-on systems.

    End of the note.

More Information