Ansicht
Dokumentation

RN2UTDTS2 - System Transport of Document Categories (Obsolete)

Fill RESBD Structure from EBP Component Structure   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Title

Collective Transport of Parameterized Document Categories

Purpose

We have provided the Report RN2UTDTS2 for calling the collective transport between systems. The report should always be called from the system from which the transport should be performed.

You can find a detailed description of how to transport document categories in the online documentation under "Transporting Document Categories in the Production Environment".
You should read this section completely, before you transport document categories.

Integration

Prerequisites

Features

Selection

To collectively transport document categories, you must enter source data.

This source data includes, which document categories should be transported from which institution into the target environment.

You only enter a version if you wish to transport individual document categories with this function.
If you wish to transport several document categories (a generic document category entry is allowed), the system will always transport the current version.

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 the executable document category will be transported to the production client.

2. Document Category with Element List and Abstract Design

We suggest you use this transport variant if you wish to transport sample document categories from one development system to another. Consultant companies would require this, for example, if they wish to to provide their customers with samples.

3. Transport Without Document Category Data (Only Development Objects)

Using this transport variant the user can transport so-called repository objects (client-independent development objects), which belong to the document definition.
When you create these repository objects in the test/development system SAP's Change and Transport System (CTS) is normally used. This automatically creates transport orders which are then separately transported into the production system.

This option is only sensible if you wish to 'download' sample document categories for an external destination system which is not networked with the source system.

When you transport development objects you can select which types 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 other correction or repair orders when the system transport is called and all objects to be transported must be assigned to a development class which can be transported. They cannot, therefore, be local or private objects.

Regardless of whether you wish to perform a production or a collective transport, no transport order will be created if even one of the objects to be transported is locked or is local/private. The system will display any objects of this type in the 'Non-Transportable Objects' dialog box. You can then either unlock the objects concerned and/or assign them to a development class which can be transported. You can then call the system transport once again.

You should also note that generated SAPscript applications are originally always local/private objects which you must assign to a development class which can be transported before the transport. You can then also separately transport the correction orders created for this so that you do not need to include the SAPscript application in your system transport.
Special rules apply to the transport of SAPscript applications: these are described in various OSS notes. The most important rule is that SAPscript forms must always be imported to client zero of the destination system. This procedure (the process steps) also apply to the system transport of document categories.

When you transport development objects, you also have the option of placing only objects from a specific origin, in the transport.

By checking the corresponding field, you can determine whether the following 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 document categories.

Standard Variants

Output

The system will list the document categories which could be placed in the 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

Activities

Example

CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6189 Date: 20240520 Time: 083248     sap01-206 ( 200 ms )