Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

difference between rstxscrp and rstxr3tr

Former Member
0 Kudos

difference between rstxscrp and rstxr3tr


Former Member
0 Kudos


You can transport a device type definition with the R/3 organizer or by downloading and uploading the definition with report RSTXSCRP.

This topic explains how to use report RSTXSCRP to transport a definition. RSTXSCRP works by downloading an R/3 device type in ASCII file format to the file system of the host system on which the report is run. To complete the transport, you can then use the report to upload any such file into another R/3 System.

Transporting a device type from one R/3 System to another copies all of the following components:

the device type

all components belonging to the device type, such as print control definitions, device formats, and SAPscript fonts.

RSTXSCRP transports only device type definitions. It does not transport the printer name definitions of individual printers or other devices. To transport a printer name definition, or printer identification, see Transporting Printers (Device Definitions).

To transport device type definitions with RSTXSCRP, do the following:

Download the definition from the "source" R/3 System.

Start RSTXSCRP with the following arguments:

– Mode: Export

– Object: prin

– Object name: <device type name>

Example: Entering HPLJIIID would download the device type definition for Hewlett-Packard LaserJet IIID printers, HPLJIIID.

– Dataset: <path name>

Path and file name for the download file. Omit the file name extension. The download file is automatically given the extension.pri. The R/3 System must have write access to the directory that you specify.

Upload the definition into the "destination" R/3 System. If the "destination" application server is on another host system than the "source" server, then the download directory must be accessible from the host system of the "destination" server.

Start RSTXSCRP with the following arguments:

Mode: Import

Object: prin

Object name: <device type name>

Example: Entering HPLJIIID would upload the device type definition stored in <path name> as device type definition HPLJIIID for Hewlett-Packard LaserJet IIID printers.

Dataset: <path name>

Path and file name of the RSTXSCRP file that is to be uploaded. The R/3 System must have write access to the directory that you specify.

RSTXSCRP in IMPORT mode overwrites existing device type definitions. Data loss (overwriting an R/3 standard printer definition or a definition of your own) is possible.


As of Release 3.0, only those languages which are installed in the source or target system are transported with the help of the online reports RSTXR3TR or RSTXSCRP when transporting SAPscript texts, styles and layout sets (transport objects R3TR TEXT, R3TR STYL, R3TR FORM). The languages installed in the system are stored in the so-called language vector, this is the R/3 profile parameter "zcsa/installed_languages". Texts, styles and layout sets whose source language is not contained in the language vector of the source or target system can no longer be exported or imported. If a translation in the language vector is not contained for styles/forms, only this translation is excluded from the export or import.

Also, the "normal" transport of texts, styles and layout sets via transport requests of the transport system no longer allows the export/import of languages not installed in the system.

If texts, styles and layout sets were not exported or imported due to the language vector, this is noted in the corresponding transport log. However, these events are not treated as errors but only as warnings during the transport!

When RSTXR3TR or RSTXSCRP is called directly, a language vector used for exporting/importing can be specified, which has priority over the standard language vector "zsca/installed_languages". See also the report documentation for RSTXR3TR and RSTXSCRP.

Damage caused to data by errors

Existing data is not changed.


Nikhil Moghe

Former Member
0 Kudos


<b>RSTXR3TR - To transport form with transport request

RSTXSCRP - To transport form without transport request</b>



Former Member
0 Kudos


RSTXSCRP Save a SAPScript layout set to disk, and load it back into SAP.

Transport SAPscript files across systems

SAPscript Export to Dataset / SAPscript Import from Dataset (Upload and download SAPScript layout sets)

1) How do you backup script layout sets?

1) Use this Std program RSTXSCRP.

1) First Export to Presentation file(.doc).

2) Whenever you need that Export into SAP

Report RSTXR3TR allows SAPscript objects (texts, styles, forms) and device types to be transported between R/3 and a local or central file. Which objects are to be transferred is taken from a transport request created in the transport system.

The entries in the transport request appear as follows:

Forms are transported using R3TR FORM NAME, where NAME stands for the name of the form.

Styles are transported using R3TR STYL NAME, where NAME stands for the name of the style.

Texts are transported using R3TR TEXT OBJECT,NAME,ID,L, where OBJECT stands for the text object (from table TTXOB), NAME for the text name, ID for the text ID (from table TTXID), and L for the language key of the text.

Device types are transported using R3TR PRIN NAME, where NAME stands for the name of the device type.

Note: Texts, styles, and forms are client-specific! They are always read from the current client when exported and to thecurrent client when imported. Printer definitions are not client-specific. The current client is therefore not significant when exporting/importing device types.

Important note: In the case of language-specific objects (that is texts, styles, and forms), only those languages (or translations, foreign languages) will be imported in the target system which are contained in the 'language vector' of the system. This is the profile parameter "zcsa/installed_languages" of the application server. The report parameter "Language vector" allows the standard language vector to be replaced with a specific one when called.

The transport log of RSTXR3TR outputs the language vector used in the export or import. If objects cannot be exported or imported because their language is not in the language vector of the source or target system, a message to this effect is displayed in the transport log.

The file to be written or read can be located either locally in the file system of the frontend server (GUI) or in the central file system of the application server (default setting).

<b>Reward points</b>