Show TOC

 Planning ImportsLocate this document in the navigation structure

Use

As already explained in The Route of a Request into the Target System, there is no automatic procedure for importing a request immediately after the export. You therefore need to plan the time of the import yourself in order to coordinate the actions required after the import (such as testing functions in the target system).

Procedure
Note

SAP recommends scheduling regular periods for complete imports into the target system (such as daily, weekly or monthly). Shorter periods between imports are not advisable.

After the import into the target system, tests can be carried out there. You can correct errors by repeating transports from the source system.

Wherever possible, correct errors in the source system only. When the corresponding requests are released, they can be reimported using command tp import all <sapsid> and are thus registered for import into follow-on systems.

If you have defined further systems for the import, the requests are registered for import into these other systems once the main import has completed (see Performing Imports).

If the follow-on systems do not receive a complete import until after the test phase, the original request and the request containing corrections are imported in the correct order. This ensures that the error in question does not arise in the target system.

Tip

In this example, the following steps should be carried out in the following order during a development phase:

1. 

Development in E11

(Monday - Thursday)

2. 

Import into T11

(Thursday evening)

3. 

Test in T11, correction in E11

(Friday)

 

Repeated transport to T11

 

4. 

Import into P11

(Friday evening)

The time given between brackets is a suggestion for a development period lasting one week. The production system will then be in a new, tested state at the beginning of the following week.

Note

It is often not possible perform an import immediately. To maintain performance and stability and to avoid conflicts with the online SAP System, it is advisable to perform the import during the night.

We recommend performing the imports when there is a low system load.

If this is not possible, use command tp impsync for the import. Note however the following restrictions that apply when using this command:

  • You can only import single transport requests.
  • You can only import changes that do not require execution of DDL statements.

For more detailed information, see SAP Note 102069, and the BC - SAP High Availability documentation under Transports.