Ansicht
Dokumentation

RN2UTDTM - (Obsolete) Client Collective Transport of Doc. Categories

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Description

For calling the collective transport between systems, the Report RN2UTDTM is now available. The client can always call the report, from which the transport is to take place. This is usually the import client of the production system.

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.

For the target entries, you need to indicate in which Clients the document categories are to be transported and, if necessary, whether a change should be executed for document categories of the Institution.
Please you note that the target client may not be identical to the current, since with the transport it does not concern a copy function for document categories.

There are three 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 on one development system are transported from one import client into the test development client.

The transport variant Document category complete with all applications and the table is required to transport complete, executable applications like the supplied i.s.h.med application "OR" from the import client of the system into a target client.
These applications may not be generated, rather, they are supplied complete with generated dialog and printing applications as well as a blank document table. Since all i.s.h.med "OR" applications for the imaginary institution "1" are supplied. For example, it is important here to enter another institution.

As an Additional option you can indicate, if necessary, whether pre-existing document categories in the target client are to be overwritten. In this case, please consider that by following this option, you will overwrite document categories already in the productive system, which could cause damage to the system.

Output

A list will appear of document categories that could be successfully transported.

You also see the following error messages and info messages:

• Document category in the target client is overwritten

• Document category already exists in the target client

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

• Document category does not exist in the source client

• Document category does not contain a concrete design.

Example

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4020 Date: 20240520 Time: 044223     sap01-206 ( 71 ms )