Kontakt

Ansicht
Dokumentation

RN2UTDTS_EUOBJ - Obsolete >>>>>>>>>>

RN2UTDTS_EUOBJ - Obsolete >>>>>>>>>>

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Transport of Parameterized Document Categories (PMDs) Between Systems

Purpose

This program enables experts to copy selected generated objects of the logon system’s parameterized document categories onto another system. Execute the program in the client from which you wish transport to occur (source client). The result of this program is a transport request.

See further information on the transport of document categories in the component i.s.h.medunder Enhanced Basic Data -> Clinical Document Categories -> Parameterized Document Categories -> Transport of Document Categories.

Integration

Prerequisites

Features

Selection

The program enables you to transport selected development objects to the document category. This is mainly necessary, if you deliver standard documents and so have to transport generated objects, such as tables, function groups/reports and forms.

Data on the source

Enter which document categories from which institution you wish to place into a transport request.

If you transport several document categories at the same time, the report places the current versions of each category into the transport request. The document category can be entered in a generic form.

Transport variants

1. Every development object for the document category (without any definition data)

This transport variant enables you to transport repository objects (client-independent development objects) that form part of the document category definition:

  • Tables
  • Function group
  • Print application
  • Forms - either with your own, or with generated SAPscript form, or with smart form.

When you create these repository objects in the test/development system the SAP Change and Transport System (CTS) normally intervenes. Therefore transport requests are created automatically, which are transported into the production system separately.

Before you execute the transport program, we recommend that you perform a test run, especially with the transport variant with development objects. As a result you obtain a list of all the objects written into the transport request. In the table contents you can also see the keys in this list, in the development objects a comment, if applicable.

2. Additional objects for the document category

Here you can also select which development objects you wish to transport:

  • Data elements and domains
  • User exits for the document category
  • User exits for documentation elements
  • External data modules with associated DDIC structures

When you call the system transport, please note that no development objects may be locked in other correction or repair orders and that all the objects to be transported have to be assigned to a transportable development class. Therefore local/private objects must not be involved.

The system does not create a transport request, if one of the objects to be transported is locked or local/private. If there are objects of this type, they are displayed in the log as Untransportable objects or in the test run log. Then, you either have to unlock the objects involved or assign them to transportable development classes. You can call system transport again afterwards.

Please also note that with generated SAPscript applications it initially always involves local/private objects which you have to assign to a transportable development class prior to transport. Then, you can also make a separate transport of the correction orders created for this, which means that you generally do not have to include the SAPscript application in your system transport.

SAPscript forms always have to be imported into the target system’s import clients.

Standard Variants

Output

The system lists the document categories that were set in the transport request.

You also obtain the following error or information messages:

  • Document category is not transportable (status?)
  • Document category is not defined in the source client
  • Document category does not have a definite design
  • Document category not transported: error in the abstract design
  • No authorization to transport the document category

Activities

If the message 'Unauthorized call sequence of change recording interfaces (message number TK425)' is displayed, delete the form from this transport order, include it in another transport order and restart the program.

Example






rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5457 Date: 20240531 Time: 080908     sap01-206 ( 94 ms )