Show TOC

Function documentationPreliminary Import of Normal Changes

 

You can request the preliminary import of a normal change into a follow-on system by executing an action. This means that the import of the transport requests associated with the normal change is carried out at once, independent of any project import into the follow-on system. Thus, the import process for normal changes can be accelerated.

Note Note

  • The preliminary import of a normal change (or the import of an urgent change) does not remove the transport request(s) from the import buffer of the systems where the transport requests are imported, waiting for being imported again from a project import. The downgrade protection conflict of transport requests (cross-system object lock and release check) is also not removed. For details, refer to SAP Note 1826789Information published on SAP site.

  • The preliminary import action can be carried out despite a lock in the task list. In the standard normal change process, if the development system is locked in the task list, you cannot create a transport request. However, with the preliminary import function, you can trigger a preliminary import even when the whole task list is locked.

End of the note.

Prerequisites

You have configured the preliminary import function. For more information, see Configuring the Preliminary Import Function.

The status of the change transaction is “Successfully Tested”, that is, all transports were released.

Activities

  1. The tester chooses Start of the navigation path Action Next navigation step Request Preliminary Import End of the navigation path.

    The status of the document changes to “Preliminary Import Requested”.

  2. The change manager approves the preliminary import.

    Note Note

    The change manager who approves the preliminary import request should not be the user who sets the status to “Successfully tested”.

    End of the note.

  3. The transport request for the change document is automatically imported into the assigned follow-on system.

  4. If the import was successful, the status of the change document changes to “Testing for Preliminary Import”.

  5. Once the tester has finished the testing, he triggers the action “Confirm successful test”.

    The transport request of the normal change is automatically imported into the next system in the landscape. When the transport request is in the import queue of the production system, the status changes to “Tested for Production Import”. Otherwise, it is reset to “Testing for Preliminary Import”.

  6. In status “Tested for Production Import”, the change manager authorizes the transport for import to production. The status changes to “Authorized for Import”.

  7. Finally, the IT operator chooses the action “Import Normal Change into Production”. In the back-end system, the transport requests are imported into the production system.

  8. The status of the normal change changes to “Imported into Production”.

The following graphic provides an overview of the preliminary import process.

More Information

Downgrade Protection