Ansicht
Dokumentation

RN2UTDTS - System Collective Transport - Doc.Categories (Obsolete)

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Description

For calling the collective transport between systems, the Report RN2UTDTS is now available. The client can always call the report, from which the transport is to take place.

You can find a detailed description for transporting document categories in the section Transport document categories into the production environment.
Please read this section completely before you transport document categories.

Selection screen

Data about the source are required for the collective transport document categories.

As source information, you should enter which Document categoriesfrom which Institutionsare to be transported into the target area.

A version is to be indicated if individual document categories are to be transported by using this function.
If multiple document categories are to be transported (generic information for document category is possible), the current versions are transported for each one.

There are two transport variants for the transport of the document categories:

The transport variant Document category with concrete design is the standard case for individual developments by the user. Development objects remain in the test/development system. Only the executable document category is to be transported on to the production client.

The transport variant Document category with concrete and abstract design is intended for the case where sample document categories are transported from one development system into another development system. This can be necessary for consultant companies who want to make samples available to their customers.

Optionally, the user has so-called repository objects (client-dependent development objects), belonging to the document definition to also be stored in the transport job (task).
Storing this object is intentionally optional, since when creating these repository objects in the test/development system, the change and transport system is normally activated. This automatically creates transport tasks, which are transported separately into the production system.

This option is then important if sample document categories for an external target system that is not networked with the source system are to be "unloaded".

For transporting development objects, the user can select which type of development objectis to be transported.

Variations are the following:

• Data elements and domains

• User exits for the document category

• User exits for documentation elements

• External data modules with related DDIC structures

• SAPscript application.

Please note that none of these objects may be blocked in other correction or repair requests when calling the system transport, and that it is required that all objects to be transported are assigned to a transportable development class (e.g., that the objects are not private/local).
Independent of whether this is a production transport or a composite transport, it holds that no transport task is created if a single one of the objects to be transported is blocked or are local/private. If there are objects of this type, they appear in the dialog window "Non-transportable objects". You can therefore unblock the objects concerned and/or assign transportable development classes to them. You can additionally call the system transport again.

Please also note that with the generated SAPscript applications,usually local/private objects are involved, to which you must assign a transportable development class. After you have done this, you can also separately transport the correction functions created for this, so that you do not have to optionally upload the SAPscript application into your system transport.
Please also consider that special rules apply for the transport of SAPscript applications, which are described in various OSS notes. The most important rule is those that SAPscript forms must be always be imported into the client zero of the target system. This holds also for the procedure (the work steps) of the system transport of document categories.

If you transport development objects, there is additionally the Option, to exclude objects of certain sources from the transport.

Principally, there can be three sources of development objects on your system:

• Individual objects that you created on your system.

• External objects that were not created on the current system. These would be those development objects on your production system transported from the test/development system.

• SAP objects that SAP supplied to all customer systems. This includes all development objects of the i.s.h.med sample document categories.

You can exclude either external development objects or SAP development objects from the transport.

Log display

A list will appear of document categories that could be set in the transport task.

You also see the following error messages and info messages:

• Document category is not ready for transport (status?)

• Document category does not exist in the source clients

• Document category does not contain a concrete design.

Requirements

Output

Example

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 6155 Date: 20240531 Time: 113835     sap01-206 ( 105 ms )