PMD Transport Workbench: Pack + Export Tab Page
The functions on the “Pack + Export“ tab page are used to pack document category definitions into installation packages and place the installation packages in a transport.
A distinction is made between the following use cases:
Entire export procedure for a transport
Transport an existing installation package
Transport of objects of development environment
Download installation package into file system
The Pack + Export
tab page is divided into three areas which are organized as tables.
Document Categories area
Development Environment Objects area
Installation Packages area
The tab page contains the following function keys for the further processing of the table content:
Display Repository Objects (Dev. Env. Objects)
Move Development Environment Objects to Transportable Package (in Dev. Env. Objects area)
Create Installation Packages
Transport BC Set (Texts)
Transport Development Environment Objects
Transport via Key (TABU)
Transport via BC Set (this is implemented as a pushbutton in the Installation Packages area)
In this area you list the document categories which exist in your client. Each table row displays information on the status and on generation.
In addition to the standard table functions Detail
, Sort Ascending/Descending
, Print
, Empty Display
, Select All
, Deselect All
the following functions are also available in the Document Categories area:
Icon |
Description |
|---|---|
|
Creates a list of all document categories which exist in your client |
|
Opens the |
If you use the selection function multiple times in a row the determined document categories are added to those currently displayed.
The list contains the following information on the displayed document categories:
Select: Here you choose the document categories from the list which you wish to further process for pack + export. To select or deselect the entire list use the corresponding pushbuttons in the menu bar of the area.
Status: The status information refers to the status of the definition data, specifically to the relationship between the abstract and definite design. An installation package can be created in any case.
|
Abstract and definite design are identical |
|
Abstract and definite design are not identical |
|
No abstract design exists |
|
Only header data exists |
Generated?
Institution
Document Category ID
The list in the development environment objects area is created by the system when you execute the Dev. Env.Objects
(Display Repository Objects
) function from the Documents Categories
area.
It contains the development environment objects (workbench objects) which belong to the selected document categories. Objects which are used in several document categories only appear in the list once.
In addition to the standard table functions Detail
, Sort Ascending/Descending
, Print
, Empty Display
, Select All
, Deselect All
the following function are also available in the development environment objects area:
Icon |
Description |
Description |
|---|---|---|
|
Move Local Objects |
Opens a dialog with which objects from local, non-transportable packages can be moved into a transportable package. |
The list contains the following information on the displayed document categories:
Select: Here you choose the document categories from the list which you wish to further process for pack + export. To select or deselect the entire list use the corresponding pushbuttons in the menu bar of the area.
Program ID
Object Type
Object Name
Package
Transportable; If the object is in a non-transportable, local package, you can select it here and use the Move Local Objects function key to assign it to a transportable package.
In the Installation Packages
table you compile the installation packages which you wish to export. The table can be created in two ways.
By creating installation packages for the document categories selected in the Document Categories list. To do this you select the InstallPackages
function key. An installation package is created for each document category and displayed in the table.
By loading all installation packages which exist in the client into the list. To do this you select the
(Load InstallPackages
) pushbutton. To restrict the display you use the selection function.
In addition to the standard table functions Detail
, Sort Ascending/Descending
, Print
, Empty Display
, Select All
, Deselect All
the following functions are also available in the Document Categories area:
Icon |
Description |
|---|---|
|
Creates a list of all installation packages which exist in your client |
|
Opens the Select Installation Package dialog. You can enter selection criteria to restrict the quantity of installation packages to be displayed. |
|
Use this key for the special case that you are in an SAP system |
The list contains the following information on the displayed document categories:
Select: Here you choose the document categories from the list which you wish to export. To select or deselect the entire list use the corresponding pushbuttons in the menu bar of the area.
Short Name
Creation Date of Package
Creation Time of Package
Export to File System
How did it get in the system?
Icon |
Meaning |
|---|---|
|
Via transport |
|
Via BC set activation |
|
Via upload |
|
Via installation |
You wish to transport the document category definition of one or more document categories from one system to another system.
In the Document Categories area you create a list with document categories and select those which you wish to transport.
Select the Development Environment Objects function key. In the Development Environment Objects area the system displays the development environment objects which belong to the selected document categories. If necessary, move the local objects to a transportable package.
Select the Install. Packages function key to create installation packets. An installation package is created for each document category which is selected in the Document Categories area.
Select the installation packages intended for the transport in the list and select Via Key (TABU). You are prompted to enter a transport request. Use an existing request to transport the PMD or create a new request. Release the request in order to trigger the transport to the stored target systems.
Note
Recommendation: Use the transport in which the development environment objects are placed (directly from the document category generation or via the special selection in the development environment objects table). In this way you can keep a better overview over all elements of the document category.
Upon receipt in the target system the installation packages are immediately available on the target system, providing you have selected transport via TABU. For the special case that you wish to use the Transport via BC Set function, note that you must first activate the BC sets on the target system.
You wish to transport an existing installation package.
In the Installation Packages area select
(Load Installation Packages
) to create a list of all installation packages which exist on your client.
Select the installation packages intended for the transport in the list and select Via Key (TABU). Allocate a transport request and release it, in order to trigger the transport to the stored target systems.
Upon receipt in the target system the installation packages are immediately available on the target system.
You wish to transport individual development environment objects of one or more document categories.
In the Document Categories area you create a list with document categories and select those which you wish to transport.
Select the Development Environment Objects function key. In the Development Environment Objects area the system displays the development environment objects which belong to the selected document categories. If necessary, move the local objects to a transportable package.
Select the development environment objects which you wish to transport and select Dev.Env. Objects. Allocate a transport request and release it.
The objects are transported to the target system and are available there.
You wish to transfer the document category definition of a document category as an XML file into the file system.
Note that you can only download one installation package per procedure.
If the installation package does not yet exist, create it (see steps 1 to 3 under "Entire Export Procedure for Transport to Other System Landscape"). If the installation package already exists, it can be displayed (see step 1 under “Transport an Existing Installation Package”). Select the installation package that you wish to download.
Choose
(Download
)). A dialog opens where you can specify the storage location. Via data carrier you can transfer the XML file to another system and import it again there.