Imports Using TMS

Objectives

After completing this lesson, you will be able to:
  • Compare the different queue-based options to import transport requests
  • Explain how to time imports and to define maintenance periods
  • Describe the different transport strategies
  • Outline the use of Transport of Copies and Relocations

Importing Transport Requests Using TMS

The most important tools used to perform imports using TMS are the import queues that reflect the SAP system-specific import buffers at file system level. The import queues display the transport requests that are to be imported, in the correct order. The import queues of all SAP systems are displayed in each SAP system of the transport domain. You can perform imports to all the SAP systems from any SAP system in the domain.

Note

When importing a transport request into a different SAP system than the one you are logged on to, you may need to provide credentials for the SAP system to be imported in.

To access the TMS import overview, use transaction STMS and choose Overview → Imports from the menu. The import overview shows the current status of the import queue of each SAP system of the transport domain. If you navigate into an import queue of one SAP system, you can see all transport requests that are to be imported.

Screen shot was taken from transaction STMS, Import Overview section by double-clicking the overview of the S4Q system (after performing all exercises and instructor demos of this class up to here) and then choosing Display More.

By choosing Display More in the application toolbar, additional columns will be displayed.

The column CV (Version Check) indicates whether or not the transport request fits the release and SAP Support Package level of all software components of the target system. If the transport request doesn't fit, it should not be imported. It can be imported at your own risk after analyzing its contents carefully.

Note

SAP Note 1090842 – Composite SAP Note: Cross-release transports lists some technical problems that may occur during a transport between systems with different SAP BASIS releases.

Hint

The version check would show a wrong release or SAP Support Package level if there is an additional software component, for example an additional plug in, in the export or import system. If this different set of software components is intended, and can't be resolved otherwise, there is a way to exclude a specific software component from the version check. For details, see SAP Note 1742547 – Information about component version check in TMS.

With the extended transport control, you could have multiple target clients for one target system. You can choose to see either one row for each target client or only one row per transport request.

To improve performance, data is read from the transport directory only the first time you start TMS. After that, the information shown is buffered in the database. The time stamp in the import overview indicates how recent the data is. The internal buffers of TMS become invalid at midnight. To refresh the data, from with any import queue choose Edit → Refresh. It may be more convenient to have the refresh performed periodically in the background. To do this, choose the menu path Extras → Update All Import Queues from the Import Overview screen. SAP recommends running this refresh on an hourly basis.

Note

If it takes a long time to finish refreshing the import queue, SAP Note 1924741 –  It takes a long time to refresh a system's import queue may help. For an automating manual process of deleting imported requests from the import buffer, see SAP Note 2461665 – Automating manual process of deleting imported requests from import queue.

The terms transport buffer and import queues are related. The import queue in the SAP system represents the transport buffer file located in the transport directory. The import queue highlights the requests that will be imported during the next complete import (import all). Because of end marks, there may be more transport requests in the transport buffer than those highlighted in the import queue.

The end mark and stopmark are the corresponding markers in the import queue and transport buffer. They indicate that only those transport requests before the mark will be imported by an import all. Regardless of how the end mark or stopmark is created, the mark is set both in the transport buffer and in the import queue. In an import queue, an end mark is indicated through the statement "End of import queue". In a transport buffer, the term stopmark is visible. There can only be one end mark or stopmark in each import queue or transport buffer.

To set an end mark/stopmark by closing an import queue, in the import queue choose Queue → Close from the menu. This is analogous to the operating system command tp setstopmark. The status bar shows the action performed.

To remove an end mark/stopmark (by opening an import queue manually, normally not needed) in the import queue screen, choose the menu path Queue → Open. Opening an import queue is analogous to the operating system command tp delstopmark.

Using TMS, you can move end marks to any position in the import queue in front of a transport request (by choosing Queue → Move End Mark from the menu). This is analogous to the operating system command tp mvstopmark.

Screenshot part was taken from transaction STMS, Import Overview section by double-clicking on the overview of the S4Q system and then choosing Display More.

You can use the import queue to:

  • View the status of transport requests.
  • Access object lists, documentation, and transport logs.
  • Close and open the queue, and move the end mark.
  • Import all transport requests, complete projects, preliminary transport requests, and selected transport requests according to filter settings.
  • Add, delete, and forward requests.

To keep target SAP systems consistent, you need deadlines to coordinate the release of transport requests by developers. To prevent transport requests released after the deadline from being imported, the import queue of the quality assurance system can be closed. As a consequence, transport requests released after deadline are positioned after an end mark in the queue for the next import. Only the requests before the end mark are imported in the next import. The same is valid for the production system correspondingly.

In exceptional cases, you can forward a transport request to another SAP system before being imported into the defined target system. For example, before being imported into the quality assurance system, a request may need to be rushed to a training system. To prepare the import to a target system outside the predefined transport routes, in the Import Queue screen, choose the menu path Request → Forward → System.

You can also delete transport requests from or add them to an import queue. But then, object dependencies may cause inconsistencies in the target system after the next import. For example, if you delete a request containing a new data element, the import of all other transport requests containing tables that depend on that data element will fail.

Caution

To avoid these inconsistencies, you are strongly advised not to delete individual transport requests from the import queue. Make your corrections in the development system and release a new transport request.

Hint

Always import all transport requests into the production system, even those with errors, together with their corrections.

Note

If you wish to simulate the import of a transport request, you can perform a  test import. For more information, see SAP Note 2510475 – Simulate Transport.

Import Strategy

There are different strategies for how to import transport requests. These will be discussed in the following pages:

Import All Transport Requests

To import all transport requests in the queue (performing what is known as an import all), choose the Import All Requests button (the "fully loaded truck" icon, see the figure above). The Start Import dialog box appears.

If you have configured the Extended Transport Control, the target client is fixed. Otherwise you can either choose a target client or keep the default. The number of the default target client is identical to the number of the source client (this is one reason why you should use the same numbers for related "major" clients in all SAP systems).

Hint

If you start the import from an SAP system different from the target system, a logon window of the target system may be displayed and you need to enter credentials for the target system.

In the Start Import dialog box, you have several options to control the import:

  • In the Date tab, you can schedule the import.
  • In the Execution tab, you can select whether TMS starts tp synchronously or asynchronously. Selecting asynchronously means tp works in the background so that your user session is not blocked for the duration of the import.
  • In the Options tab, you can select "expert options", the so-called unconditional modes. The options and their defaults vary according to the selected import method and the configured transport strategy.

The Import Overview screen indicates whether the import is running. After the import, the end mark is removed and the queue is opened again automatically. After transport requests have been imported successfully, they are automatically added to the import queue of further target systems (systems that are connected with the help of a delivery route). The configured transport routes therefore specify which transport requests are automatically forwarded to which target systems.

When using the QA approval procedure function in this SAP system, all transport requests in the import queue of the subsequent SAP systems are set to inactive. If an import containing one or more inactive requests is triggered, the TMS will not perform the import.

Note

When using the QA approval procedure, you can only import all transport requests into the delivery systems if all the transport requests that are ready for import have been checked for all the applicable approval steps (approved or rejected).

If all the transport requests for one CTS project have been approved, you can import them into the delivery system even if there are still unprocessed or rejected requests for other CTS projects in the work list.

If you perform an import through an import all, objects are imported in the correct sequence in which they are listed in the import buffer file on file system. This means that if transport requests near the start of the list and those near the end of the list affect the same objects, the final versions of the objects after import will represent the latest changes. As a result, the incorrect objects do not affect your production environment, they are not really imported at all.

Note

You can deactivate the ability to perform a complete import (import all) for each SAP system using the tp parameter NO_IMPORT_ALL or by changing the transport strategy (see the "Transport Strategies" section, later in this lesson).

Import Complete Project

Before performing the import, SAP recommends setting the end mark to close the import queue. This avoids unintentionally importing other transport requests that may appear in the import queue.

You can set a filter on the import queue to limit the displayed transport requests to transport requests with specific properties so that you can see only those transport requests that belong to a specific project. To set a filter, place the cursor in a row of the import queue and press the Filters button in the application toolbar.

To prevent transport requests being imported from unapproved projects, use the filter for column Project to import only the transport requests belonging to approved projects.

Import Single Transport Requests (Preliminary Import)

In contrast to standard imports, preliminary imports are imports of selected single transport requests. SAP strongly recommends only using project-specific imports or full imports because of object dependencies and the risk of inconsistencies when importing individual transport requests. For example, an ABAP program in one transport request can be successfully imported, but the table that it refers to can be in another transport request that has not yet been imported. Until the table is imported, executing the program generates short dumps. Therefore, use preliminary imports only in exceptional cases.

To import single transport requests choose the Import Request button on the application toolbar (related to the "partly loaded truck", see the figure above).

To minimize the risks associated with preliminary imports, the transport request remains in the import queue after the import and is re-imported the next time the entire import queue or the corresponding CTS project is imported. This guarantees the correct import sequences and is defined by the import option Leave Transport Request in Queue for Later Import, which, depending on the transport strategy, may be automatically selected.

By default, the TMS will check if transport requests in the import queue depend on transport requests in other projects. The import will only be possible if the predecessor's relationships is not violated. It may be necessary to specify additional options when performing a preliminary import:

  • Leave Transport Request in Queue for Later Import – this is the default when using transport strategy mass transports
  • Import Transport Request Again – ignore that the transport request has already been imported
  • Overwrite Originals
  • Overwrite Objects in Unconfirmed Repairs
  • Ignore invalid transport type
  • Ignore invalid table class
  • Skip predecessor relationships
  • Ignore Invalid Component Version (a wrong SAP Support Package level or a wrong release)

Sequence of Import of Objects in Transport Requests

The objects from the transport requests marked for import will be imported as follows:

  • All objects of all selected transport requests are merged together.
  • Objects are sorted first according to their level (for example, table definitions before programs).
  • If an object is included in more than one transport request, only the version in the last transport request is kept after import (according to the sequence in the import queue).

    Hint

    This sequence is used for import all, import project and import single.

    Note

    In a three-system landscape:

    • The import queue of QAS reflects the order of export from DEV
    • The import queue of PRD reflects the order of import into QAS

    This is not identical in all cases, but it is the correct sequence.

Import Using TMS

Business Example

The project team leader has confirmed and released all required transport requests from the development system. The transport administrator can now import the transport requests into the target systems. The transport administrator has to follow the guidelines established for the transport strategy and the transport schedule. In this way, the transport administrator can ensure that changes are distributed consistently to all SAP systems in the transport landscape.

Task 1: Review Import Queues

Hint

Before proceeding, check whether all of your transport requests have been released from the development system S4D, development client 100. If not, release them.

Log on to the quality assurance system S4Q, quality assurance client 100. Review the import queues for all SAP systems.

Steps

  1. Are there any transport requests waiting to be imported into the quality assurance system S4Q?

    1. Log on to the quality assurance system, client 100 with the credentials provided by your instructor.

    2. Start transaction STMS. To see the import overview of all SAP systems in the transport domain from the initial TMS screen menu, choose the menu path Overview → Imports.

    3. On the Import Overview screen, the Requests column displays how many transport requests are ready to be imported into a specific SAP system. At this point, there are some transport requests ready to be imported into the quality assurance system S4Q.

      Hint

      Remember to Refresh the Import Overview to see the latest status.

      Note

      The number of transport requests ready to be imported for a particular SAP system may differ from the actual number of transport requests in the import queue of that SAP system. This number can be different, for example, if there are non-standard transport requests in the queue or if there are additional transport requests after an end mark.

  2. Are there any transport requests to be imported into the pre-production system S4P?

    1. Following the previous step, check the entry in the Requests column for system S4P.

    2. The only transport requests waiting to be imported into the pre-production system are those requests that have already successfully been imported into the quality assurance system and approved; there should be none.

  3. Review the current status of the import queues of all SAP systems. Is the import queue of the quality assurance system open or closed?

    1. From the Import Overview screen, the Status column displays the current state of each SAP system's import queue. To see the meaning of the icons associated with the SAP systems, display the legend using the menu path Extras → Legend.

    2. Check the status for the line for the S4Q system.

Task 2: Display the Object Lists

Review the import queue of the quality assurance system.

Steps

  1. Display the transport requests that are to be imported into the quality assurance system. Which SAP users are owner of the transport requests?

    1. In your quality assurance system S4Q, use transaction STMS to access the initial TMS screen. From this screen, choose the menu path Overview → Imports to see the import overview of all SAP systems in the transport domain. Double-click the quality assurance system import queue.

    2. Choose the Refresh button to see the latest status. All transport requests to be imported into the quality assurance system are listed. The Owner column gives information about the user who is the owner of the specific transport request.

  2. Display the objects to be imported with one of the transport requests that has been released with your account.

    1. To display the object list of a transport request owned by your user, from the Import Queue: System S4Q screen, either double click the transport request (in column Request) or select the transport request and choose the menu path Request → Display → Object List.

    2. The object list can be expanded to see all objects that are included in this transport request.

    3. Choose Back to get back to the Import Queue: System S4Q screen.

Task 3: Perform the Import into the Quality Assurance System

Import all transport requests of your CTS project into the quality assurance system S4Q.

Hint

For importing transport requests into the quality assurance system, you should log on to the quality assurance system, quality assurance client 100. If you started the imports from within any other SAP system of the transport landscape, you would be prompted for credentials to the quality assurance system when you start the import.

Steps

  1. Display more information about the transport requests now waiting in the import queue of the quality assurance system.

    1. Following the previous task, to see more technical information for the transport requests in the import queue of the quality assurance system, choose the menu path Edit → Display More from the Import Queues: System S4Q screen.

    2. This displays more columns, including T (Type) and UMO (Unconditional Modes).

      • The column T displays the type of transport request, for example W for customizing requests or K for workbench requests.

      • The column UMO indicates what unconditional modes are associated with the transport requests. All preliminary imports should have the unconditional mode I after being imported preliminarily. This indicates the transport request can be re-imported into the target system without manually setting any special options.

  2. Set a filter so that the import queue displays only the transport requests belonging to the CTS project assigned to you. Import all your transport requests into the quality assurance system by performing a project import of your project.

    1. Mark the Project column and choose Edit → Filters from the menu. Select your CTS project name in the Set Filter dialog box and confirm the dialog box with Copy.

    2. To perform a project import, choose Queue → Start Import, or choose Import All Requests from the application toolbar (this button may look like a fully loaded truck). Choose Continue and Yes.

    3. After the import has finished, check the return code for the transport requests from your project. For this, you may need to switch to the Import History (by choosing Goto → Import History from the menu and then scrolling down to the end of the list) and look at the entries in column RC.

Timing Imports and Maintenance Mode

Timing Imports

Depending on both the import strategy (import project, individual import, import all, or special transport workflow) and the SAP release / SAP Support Package level, the available options may vary. When starting an import, you can select the following options in the Date tab:

Immediate

Selecting this option immediately starts the import.

At Start Time

Selecting this option starts the import at the specified time. The import is scheduled as a background job in the target system. If you also enter a date and time in the No Start After field, the import is started in the time frame between the times entered in Planned Start and No Start After. If there is no background process available during this time, an import does not occur. If you want the import to be performed regularly, you must select a period in the Period field.

After Event

Selecting this option starts the import only after a specified event is triggered. If you select Execute Import Periodically, the import is started each time the specified event is triggered. Otherwise, the import is started only the first time the event occurs.

Note

Note that the Period field and the Execute Import Periodically check box don't exist for individual transports and the special transport workflow.

From the import queue of each SAP system, you can monitor and maintain all planned imports by choosing Goto → Job Monitor from the menu.

After the export, a transport request is not automatically imported. It must be manually imported. When planning imports, include enough time to accommodate post-import tasks such as the quality assurance testing. SAP recommends planning imports at regular intervals, such as monthly, weekly, or daily, using import all or import project into the target system. Frequent imports "on demand" are not recommended.

The following actions have to be considered:

  1. Copy the contents of the transport requests into a client in the same SAP system using transaction SCC1 or, as of SAP S/4HANA 2020, SCC1N (unit testing).
  2. Release of transport requests.
  3. Imports into clients in subsequent SAP systems.

The timing of transport requests is based on the following factors:

  • Clients and their roles in your SAP system landscape
  • Synchronization requirements, that is, when changes are required in different SAP systems
  • Backup prior to the import
  • Code freezing requirements

Change management includes creating, releasing, distributing, and verifying transport requests for all SAP systems in the SAP system landscape. Ensure that your distribution procedures are supported by the TMS setup. Determine release, import, and verification requirements for all transport points in your SAP system landscape. For each transport point, define the following:

  • When will transports take place?
  • Who is responsible for a transport request during its various transport phases?
  • How will transports be reviewed before being distributed or redistributed?
  • What happens if a transport is successful, but testing proves that its contents are incorrect?
  • Are sign-offs required for transporting?

Assign persons to be responsible for all transport steps. Use authorizations to restrict access to transport management tasks and to operating system level.

SAP provides techniques for the distribution and management of changes using transport buffers. These transport buffers indicate the changes to be transported to the target system and the transport order. You must control the transport buffers and the distribution or redistribution process. To verify all imports, review transport logs, establish testing standards and quality assurance procedures, and define sign-off procedures.

Maintenance Mode

With SAP S/4HANA, transaction SMAINTENANCE allows you to define a maintenance period. During this maintenance period, normal users will not be able to log on. Only system administrators with a special security policy can connect (transaction SECPOL, attribute TENANT_RUNLEVEL_LOGON_PRIVILEGE). In addition, only admin batch jobs will be executed (all other jobs will be on hold).

  • The action Switch to Maintenance starts a workflow which sets the system to mode In Maintenance. The workflow consists of the following modes: Running → Web dispatcher closed → Cool down → In Maintenance as follows:
    • Running: The system is fully operational for business end users and administrator.
    • Web dispatcher Closed: The system is fully operational for business end users and administrators but connections to the Web dispatcher from outside are blocked. That is users connected via the Web dispatcher cannot work any longer.
    • Cool down: The system is fully operational for administrators only. Business users are expected to finish their work and log out. At the end of the cool down phase business end users' sessions are terminated.
    • In Maintenance: The system is fully operational for administrators only (users who have a special security policy assigned as described above). There are no business end users logged onto the system.
    The current duration of the whole workflow is 10 minutes. Switching back to Running in this period may lead to errors.
  • The action Switch to Running starts a workflow which sets the system to mode Running. The workflow consists of the modes In Maintenance → Running. The switch to Running is performed immediately.

For more information, see the blog ABAP Platform – Part 3 – what’s new for the basis administrators (https://blogs.sap.com/2020/06/18/abap-platform-part-3-whats-new-for-the-basis-administrators/) and SAP Online Documentation for SAP S/4HANA (Product Assistance), area Enterprise Technology → ABAP Platform → Administrating the ABAP Platform → Administration Concepts and Tools → Administration of Application Server ABAP → Maintenance Mode.

Transport Strategies

There are three different transport strategies available:

Transport Strategies

  • Queue-Driven Transports, Mass transports
  • Queue-Driven Transports, Single transports
  • Workflow-driven transports

    Hint

    By default, the transport strategy is set to Queue-Driven Transports, Mass transports.

Queue-Driven Transports, Mass Transports

Mass transports are a good solution if you have a large number of transport requests to administrate and want to automate the process as much as possible. The continuous use of mass transports is the most secure way of keeping your SAP systems synchronized and consistent. Before you perform a mass transport into your production system, you must check all transport requests in the quality assurance system and confirm their transport into other SAP systems. Use the Quality Assurance approval procedure when doing this.

You define mass transports as the import method for the relevant SAP systems by choosing the transport strategy Queue-Driven Transports, Mass transports.

The administrator can schedule the imports periodically in TMS, or start each import manually. Only import single transport requests (single imports) before others in the import queue in special cases.

Transport requests that are imported in advance by the TMS will be imported again during the regular import. You can also use the transport workflow to import single imports in advance.

Queue-Driven Transports, Single Transports

If you want to maintain a production system with only a small amount of specific transport requests, it is best to import single transport requests rather than importing all transport requests waiting for import. Use single transport requests if you have fewer changes to transport and your organization prevents you from having a fixed transport schedule.

This method usually entails extra work for the administrators compared to periodic imports. Developers need to pay extra attention to the consistency and the import order of their transport requests. If a small number of developers are working on a project, or if the developers work very closely with the administrator, they often perform their own single transports.

Note

You can use this import strategy as well if you use project import:

  • By removing the import all option, you prevent the administrator from accidentally importing all transport request independent of the CTS project.
  • You can filter with respect to the CTS project to use import all transport requests belonging to one specific CTS project together.
Workflow-driven Transports

If you want to perform specific single transports into your SAP systems, but would rather have this done by the SAP system administrator, you may want to use the transport workflow. This method automatically triggers a workflow when you release a transport request. The workflow ensures close communication between development and administration.

Hint

As prerequisite for this, you need to have configured the transport workflow for your SAP system (see lesson "QA Approval Procedure and Transport Proposals").

Maintain Transport Strategy

If you want to work with queue driven single transports or workflow-driven transports instead, you will need to change the configuration as follows:

Screen shot was taken from Transport Routes editor of transaction STMS on the transport domain controller system.

Procedure

  1. Start transaction STMS on the Transport Domain Controller system and choose Overview → Transport Routes from the menu. The screen Display Transport Routes appears displaying the existing transport routes in the transport domain.
  2. Switch to the change mode.
  3. Double-click one of the SAP systems of the system landscape. The Change System Attributes dialog box appears.
  4. Select the System Attributes tab and choose your transport strategy.
  5. Choose Transfer.
  6. Save your settings and confirm to activate and distribute the configuration across all systems (if necessary).

Settings in TMS Depending on the Transport Strategy

Some settings in the Transport Management System depend on the import strategy you have chosen:

Queue-Driven Transports, Mass Transports

By default, the import option Leave Transport Request in Queue for Later Import is activated, when doing an import single.

Hint

The import option Leave Transport Request in Queue for Later Import causes transport requests that have been imported as single transport requests to be imported in the correct order in the next import of all transport requests. This option is useful if you have to make preliminary imports for individual transport requests as it prevents older objects from being imported at the next regular import of all the transport requests (overtaker problem).
Queue-Driven Transports, Single Transports

By default, the import option Leave Transport Request in Queue for Later Import is deactivated.

Hint

If you supply an SAP system only with single transport requests (without using the project import), this option would not be useful since the transport requests would remain in the queue after the import with status Request is ready for import again and would have to be manually deleted from the import queue.

The buttons in the application toolbar on the Import Queue screen change according to the requirements of the single import strategy.

In the Import All Requests function ("fully loaded truck") is only available if you have selected one or more CTS projects using the Filter function. This prevents you from accidentally importing all transport requests in the queue.

Workflow-Driven Transports

Transport proposals are created automatically when transport requests are exported.

The import options correspond to those for single transport requests.

Imports become linked to the processing of transport proposals in the TMS Worklist.

A warning appears in the import queue if you try to import transport requests without using the transport workflow.

The following parameters for the transport control program tp and the Change and Transport System (CTS) are set according to the chosen transport strategy:

tp Parameters of Transport Strategies

ParameterValue for Queue-Driven Mass TransportsValue for Queue-Driven Single TransportsValue for Workflow-Driven Transports
IMPORT_SINGLE_ONLY011
NO_IMPORT_ALL011
IMPORT_SINGLE_STRATEGY010
WORKFLOW_STRATEGY001
REPEATONERROR988
STOPONERROR999

The tp parameter STOPONERROR defines from which return code on the import immediately stops. REPEATONERROR defines from which return code on the import is not classified as successful and has to be repeated (therefore, the transport request remains in the import queue). For example, with Single Transports, return code 8 is classified as an unsuccessful import and has to be repeated. With Mass Transports, the same return code 8 would be a successful import and the transport request is deleted from the import queue.

Hint

Don't manually change the parameters that are relevant to the transport strategy. TMS generates these parameters each time the transport route configuration is changed.

Transport of Copies and Relocation

Create a transport request in transaction SE09.

You can use transport of copies to transport objects to another SAP system of your choice, especially, if there is no consolidation route pointing from the SAP system, you created the transport request to the SAP system you want to import the transport request. The objects are transported in the version they have in the SAP system, the transport request was exported from. The original location of the objects is not changed. In contrast to workbench requests or customizing requests, transports of copies will not be added to the import queue of a subsequent delivery system.

Note

The term copies in Transport of copies is not related to the word "copying" but to the fixed term "copy" as opposite of "original".

You can use Relocations of objects w/o package change if development work on objects is to take place in another SAP system temporarily. Special developments may be carried out in a separate SAP system, for example, so as not to interfere with the development process. This transport request type allows you to move the original location of objects to the target system. It also can be used, if an object was created, for example, in the quality assurance system, and the original system entry should now be moved to the development system.

Use Relocations of objects with package change when the development system of individual objects is to be changed on a permanent basis. This request type allows you to change the original location of objects to the target system and to change the package assignment of the objects at the same time. Due to the package being changed automatically, the objects have the desired transport attributes immediately after being imported into the target system of the transport request.

Use Move Complete Package when the development system of a complete package is to be changed on a permanent basis.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn