Here you can create a transport request which lets you transport objects to a target system.

Once you have made your CO-PA settings, you can collect the objects which are linked to these settings (table entries, data elements, domains, tables, and so on) in a transport request.

With this function, the system collects all the dependent objects in the source system and places them in a transport request. After importing the objects to the target system, it automatically activates the necessary objects in the ABAP Dictionary (the data structures of the operating concern).

Note: You must regenerate the environment of the operating concern following the import, even though the operating concern's status is "active" and no other actions are necessary.


The source and target systems must be of the same release and update level.


With this function you create a transport request based on the current settings. Consequently, no new CO-PA objects should be added and no settings changed while the transaction is running. Furthermore, in R/3 you can create a transport request (what you want to transfer) and carry out the actual transfer at different points in time. If you change any settings between the time when you create the transport request and when you carry out the transport, the system recognizes some of the changes but does not add any new objects to the transport request. This can lead to inconsistencies in the target system following the transport.

It is therefore recommended that you make no further settings in CO-PA between the time when you create the request and when you export the settings.

When you create the transport request, the system is not able to check which of the objects to be transported already exist in the target system. If objects already exist there, the system may import these objects and overwrite the ones which were created in that system. To avoid this, you should set up one source system first, and then transfer the settings to your other system(s). Do not create any new CO-PA objects (operating concern, characteristic, value field, and so on) in the target system.


Further notes

Note that when you transport reports, the operating concern itself is treated as a dependent object. Normally you should only select the flags "Report" and, if desired, "Form".

For technical reasons, the system cannot transport any reports whose names contain special characters. To get around this problem, you need to create a new report without special characters, and copy the old report.

To ensure that your entire system is consistent, the system transports all the tables and table entries which CO-PA references. The system transports only those ABAP Development Workbench objects which are generated by CO-PA, and the table entries which are managed by CO-PA and those changed by the user. Those settings which you can make in CO-PA, but which also affect other applications outside of CO-PA, are not transported. This ensures consistency in the target system.

Below is a list of the objects which are not transported:

When you create authorization objects using transaction KE17 or KE37, you can assign these to a customer-defined development class. This makes it possible to transport the authorization objects. When you create the objects, fields may be created in the structure ZAUTHCUST. This structure belongs to development class $TMP. If you want to transport authorization objects creating using KE17 or KE37, check whether the structure ZAUTHCUST contains any fields. You can display the fields using transaction SE12.

If the structure contains fields, it must also exist in the target system. If it does not, create it there first.

If structure ZAUTHCUST already exists in the target system, you need to adjust it manually. Use transaction SU20 to enter the fields that are missing in the structure. Then save the structure. It will then be activated automatically.

In addition, no transaction data is transported.

Transported objects in the individual object classes

The following transport objects are available (listed with their dependent object classes):

1. Transporting reports

Note: The dependent object class "Report" must be selected.

The following are transported:

1. Transporting forms

The following are transported:

1. Transporting operating concerns

The following object classes are available:

To find out which objects are transported for these object classes, see the F1 Help for the respective object class.

Note: Large master data tables may lead to performance problems. If this is the case, transport the master data tables separately - manually - using the Workbench Organizer instead of using the transport program.

a) Object class "Key figure scheme"

The following are transported:

1. Transporting line item layouts

The following are transported:

1. Transporting planning layouts

The following are transported: