Description
Report RSTXSCRP allows SAPscript objects (standard texts, styles,forms) or device types to be transported between R/3 and a local orcentral file.
Note: Texts, styles, and forms are client-specific! For exportthey are always read from the current client and for import theyare always read to the current client. Device types are notclient-specific so the current client is not significant in theexport/import of printer definitions.
Important note: For language-dependent objects (that is, texts,styles, and forms) only those languages (or translations, foreignlanguages) are imported in the target system which are contained in thesystem's "language vector". This is the profile parameter"zcsa/installed_languages" of the application server. The reportparameter "language vector" allows you to replace the standard languagevector with your own vector when it is called.
The transport log of RSTXSCRP outputs the language vector used for theexport or import. If objects cannot be exported or imported becausetheir language is not contained in the language vector of the source ortarget system, a corresponding message appears in the transport log.

Precondition
Styles and forms are made up of maintenance versions and activeversions as well as foreign language versions (translations). When astyle/form is exported only the active version of the style/formis exported. Maintenance versions are not transported. All existingtranslations of a style/form are also transported if their language iscontained in the language vector.
If a style/form is flagged as "Translation not applicable", only itsoriginal language will be exported. Importing a style or form such asthis, which is not to be translated, automatically deletes any existingtranslations in the target system.
In the case of text objects RSTXSCRP can transfer only standard texts(with text object key = TEXT) with text ID = ST and language key =logon language to or from the current client.
Transporting a non-existent device type deletes the definition of thisdevice type in the target system.
Parameters to be specified:
The radio buttons Device type/Form/Style/Standard text selectthe transport object to be imported or exported.
Object name: Name of the standard text, style, form, or devicetype.
Mode: Export means download to file, IMPORT means upload fromfile.
File system: Allows you to choose whether the file isread/written locally (GUI file system) or on the application server(default setting).
File name: Path and file name of the file to be generated orread in the file system of the application server. The name selectedhere must fulfill any requirements specified by the R/3 platform (UNIX,Windows NT, AS/400). "/tmp/********&&&&" appears as a default value. Itis only a template and not the actual file name! If the default valueis not overwritten, "********" is replaced by the first eight lettersof the object name, and "&&&&" by the file extensions ".TXT", ".STY",".FOR" or ".PRI".
This parameter is not significant for local files and an input templateappears for the local file name.
Binary file format: If this parameter is selected, a binary fileformat with a fixed record length is written or required for reading.This file format is not compatible with a "non-binary format", that isfiles for which the parameter was set during writing can only be readwith a set parameter. The binary files generated by RSTXSCRP areidentified by the string "RSTX@" (ASCII code) at the beginning of thefile.
In binary format, the file contains an identifier indicating in whichsystem character set the data was written. RSTXSCRP then performs acharacter set conversion from the file character set to the systemcharacter set of the current system when the file is imported. It istherefore possible to exchange files generated by RSTXSCRP betweensystems with different system character sets.
Important restriction: You are advised to only use the character setconversion when exchanging files between two systems with an identicalnumber of characters. If objects in the source system containcharacters which are not contained in the system character set of thetarget system, they are represented by a substitute character whenconverted and their contents are therefore changed. The objects areimported under a modified key if non-translatable characters are partof the object key (for example, a text name with East European specialcharacters).
Display file contents: If this parameter is selected, thecontents of the generated or read file are listed together with thetransport log. Otherwise only the transport log is output.
Language vector: If this parameter has a value (that is, one ormore language keys), this report parameter is used as a language vectorfor exporting or importing the language-specific objects. The profileparameter "zcsa/installed_languages" is used as the default languagevector.
Only export original language: If this parameter is selected,only the original language for layout sets and styles is transportedwhen exporting, and no translations.

Output
The report generates an action log of the import/export.

Example
In order to download the device type HPLJIIID from R/3 into the file"/tmp/HPLJIIID.PRI", enter the following parameters:
Device type selected
Object name: HPLJIIID
File name:
Mode: EXPORT
(Other report parameters have default value)
In order to upload the form TESTFORM from the file"/usr/test/TESTFORM.FOR", enter the following parameters:
Form selected
Object name: TESTFORM
File name: /usr/test/TESTFORM.FOR
Mode: IMPORT
(Other report parameters have default value)