Ansicht
Dokumentation
RN2UTDTS3 - System Transport of Document Categories (Customer) (Obsolete)
CL_GUI_FRONTEND_SERVICES - Frontend Services Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Title
Transport of Parameterized Document Categories (PMDs) Between Systems
Purpose
Using this program you can transport all the objects of a PMD between systems. Implement the program on the client from which transport is to occur (source client). The result of this program is a transport request.
You can find additional information on transporting document categories in the component i.s.h.medunder Enhanced Basic Data -> Parameterized Document Categories -> Transport of Document Categories.
Integration
Prerequisites
Features
Selection
The program writes all parameterization data for a document category in a transport request. You can also transport the development objects table, function groupand form for this document category, if you have not yet placed these objects in a transport request.
Transport Variants
1. Document Category with Element List and Abstract Design (Definition Data)
This variant transports all document category data, which has been entered in the system administration of the parameterizable documentation for this document category. This includes the table contents (customizing data). The complete document category definition is transported to the productive system. Here you cannot select any transport objects.
2. Development Objects for Document Category (Without Definition Data)
The tables, function groups and forms created during the generation of document categories are not automatically assigned to a transport request. You have to make this assignment yourself by changing the object catalog entry for these objects. If you have not made this assignment or wish to re-transport the objects, select this transport variant.
Before executing the transport program, we recommend a test run, in particular with the transport variant with development objects. You receive a list of all objects which are written in the transport request. In the case of table content, you additionally see the key, and, if applicable, a comment in the case of development objects.
You should note that development objects cannot be locked in other correction or repair requests 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 be local/private objects.
The program doesn't create a transport request, if even one object to be transported is locked or is local/private. If such objects exist, they are displayed in the (test) log as Non-Transportable Objects. You can then either unlock the objects concerned 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 the generated SAPscript applications are always originally local/private objects, which you must assign to a development class which can be transported before the transport. You can then transport the correction orders created for this separately, so that not you do not need to add the SAPscript application to your system transport.
Standard Variants
Output
The document categories which can be placed in the transport request are listed.
You 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 definite design
- Document category not transported: Error in abstract design
- No authorization to transport 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
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 4526 Date: 20240531 Time: 020341 sap01-206 ( 101 ms )
