PMD Transport Workbench
The PMD Transport Workbench provides four tab pages with all functions which an administrator requires in order to complete the complex tasks for copying, distributing and transporting parameterizable documents (PMD). The tab pages are titled as follows:
Pack + Export
Import + Install
Distribute
Copy
The use of the TWB requires detailed knowledge of PMDs. You should note that, depending on the specific application case only some of the provided functions are used or the functions are executed in a different combination to the standard procedure.
Note
The PMD Transport Workbench comprises and enhances the function possible in the N1IMSU
for processing PMD installation packages. N1IMSU
will therefore become obsolete as far as PMD is concerned.
PMD: Overview of Transport-Relevant Components
A PMD consists of definition data and objects of the development environment.
Definition Data
Definition data comprises table entries in customizing tables which are filled when document categories are designed and developed. We differentiate between header data and documentation element data.
The header data (also: document category data) has a direct reference to the document category. Header data includes the document category ID, document category version, description, reference level, INCLUDE name for USER EXITs, document-related USER EXIT form routine names, function group names, table names, form names and others.
The documentation element data contains information on the documentation element contained. This includes information on data elements, structures, layouts, connections to UEs, external data modules, printouts etc. This data is used to generate the dialog application, the print application, the tables and the data structure. It is also required to further develop PMDs.
Development Environment Objects
Development environment objects are divided into generated objects and non-generated objects. In general these are client and institution-independent.
Generated objects are tables, data structures, function groups and, where applicable, SAPScript forms.
Non-generated objects include DDIC objects for the documentation elements, USER EXIT includes and self-programmed forms.
PMDs are developed and generated on a client of a development system and must then be transported to other clients on the system for testing and for use and/or distributed to other systems. Depending on the use case, not all definition data, but only the header data should be distributed within a system. It can be necessary to transport only selected objects of the development environment. It is possible to copy PMDs to support the development of new document categories, e.g. when transferring sample documents.
PMD: Explanation of Terms
Term | Description |
|---|---|
Customer Own Document Category | As the customer you define and generate these on your development system, transport them to your productive system and distribute them there to the clients/institutions on which they should be used. |
Sample Document Category | This is part of the delivery and serves as a copy template for a customer’s own document category; the sample itself may not be changed or productively used. |
Standard Document Category | This is part of the delivery and can be used productively, but may not be changed. |
Transport | A document category is brought completely from one system to another system, whereby the name of the document category remains the same. The transport of definition data is implemented via installation packages, for SAP objects the usual transport procedure for workbench objects. |
Copy | Within a system a copy of the ORIGINAL document category is created completely and stored under the name KOPIE on the current client. The KOPIE document category can be revised and must be generated. |
Distribute | In a system only the document category header is copied under the same name to another institution. The document category can be used there, but not processed. |
Call
You access the PMD Transport Workbench on the SAP Easy Access screen under 
Clinical System
Basic Clinical Data
Clinical Documentation
Document Definition
Document Category
PMD: Transport Workbench
or using the transaction N2PMD_TWB
.
Activities
The following is an overview table with use cases and a link to the corresponding documentation.
Task | Task Variant | Tab Page |
|---|---|---|
You have a sample document or other template and wish to use this as the basis for a new document category. | Use the function on the | |
You have developed, generated and tested a document category and wish to make it available on other clients. | Use the function on the | |
You have a document category on a client of your system which you wish to make available on other clients. | Use the function on the | |
You wish to transport one or more document categories (definition data and also development objects) from one system to another. | Export for a transport within a system landscape Export for a transport to another system landscape Transport an existing installation package Transport of objects of development environment | Use the functions on the |
You wish to store PMD definition data in a file. | Use the functions on the | |
You have received BC sets which contain installation packages and wish to activate and install the contained installation packages. | Use the functions on the | |
You have stored installation packages on your file system and wish to install these. | Use the functions on the |