Title
Collective Transport of Parameterized Document Categories

Purpose
We have provided the Report RN2UTDTS2 for calling the collectivetransport between systems. The report should always be called from thesystem from which the transport should be performed.
You can find a detailed description of how to transport documentcategories in the online documentation under "Transporting DocumentCategories in the Production Environment".
You should read this section completely, before you transport documentcategories.

Features

Selection
To collectively transport document categories, you must enter sourcedata.
This source data includes, which document categoriesshould be transported from which institution into the targetenvironment.
You only enter a version if you wish to transport individualdocument categories with this function.
If you wish to transport several document categories (a generic documentcategory entry is allowed), the system will always transport the currentversion.
There are three transport variants for transporting document categories.
1. Document Category with Element List
This transport variant is usually used for the user's own developments.Development objects remain in the test/ development system. Only theexecutable document category will be transported to the productionclient.
2. Document Category with Element List and Abstract Design
We suggest you use this transport variant if you wish to transportsample document categories from one development system to another.Consultant companies would require this, for example, if they wish to toprovide their customers with samples.
3. Transport Without Document Category Data (Only DevelopmentObjects)
Using this transport variant the user can transport so-called repositoryobjects (client-independent development objects), which belong to thedocument definition.
When you create these repository objects in the test/development systemSAP's Change and Transport System (CTS) is normally used. Thisautomatically creates transport orders which are then separatelytransported into the production system.
This option is only sensible if you wish to 'download' sample documentcategories for an external destination system which is not networkedwith the source system.
When you transport development objects you can select whichtypes of development objects should be transported.
You can select the following types:

• Data elements and domains


• User exits for the document category


• User exits for documentation elements


• External data modules with relevant DDIC structures


• SAPscript application.

You should note that objects to be transported cannot be locked in othercorrection or repair orders when the system transport is called and allobjects to be transported must be assigned to a development class whichcan be transported. They cannot, therefore, be local or private objects.
Regardless of whether you wish to perform a production or a collectivetransport, no transport order will be created if even one of the objectsto be transported is locked or is local/private. The system will displayany objects of this type in the 'Non-Transportable Objects' dialog box.You can then either unlock the objects concerned and/or assign them to adevelopment class which can be transported. You can then call the systemtransport once again.
You should also note that generated SAPscript applications areoriginally always local/private objects which you must assign to adevelopment class which can be transported before the transport. You canthen also separately transport the correction orders created for this sothat you do not need to include the SAPscript application in your systemtransport.
Special rules apply to the transport of SAPscript applications: theseare described in various OSS notes. The most important rule is thatSAPscript forms must always be imported to client zero of thedestination system. This procedure (the process steps) also apply to thesystem transport of document categories.
When you transport development objects, you also have the option ofplacing only objects from a specific origin, in the transport.
By checking the corresponding field, you can determine whether thefollowing development objects should be transported:

• your own objects which you created on your system, and


• SAP objects which SAP delivers on all customer systems. This includes,
for example, all development objects of i.s.h.med sample documentcategories.

Output
The system will list the document categories which could be placed inthe transport order.
You will also receive the following error or information messages:


• Document category cannot be transported (Status?)


• Document category does not exist in source client


• Document category has no concrete design


• Document category could not be transported: Error in abstract design


• No authorization for transporting document categories