hi use
RSTXSCRP to upload into application server
SAPscript Export to Dataset / SAPscript Import from Dataset
Description
Report RSTXSCRP allows SAPscript objects (standard texts, styles, forms) or device types to be transported between R/3 and a local or central file.
Note: Texts, styles, and forms are client-specific! For export they are always read from the current client and for import they are always read to the current client. Device types are not client-specific so the current client is not significant in the export/import of printer definitions.
Important note: For language-dependent objects (that is, texts, styles, and forms) only those languages (or translations, foreign languages) are imported in the target system which are contained in the system's "language vector". This is the profile parameter "zcsa/installed_languages" of the application server. The report parameter "language vector" allows you to replace the standard language vector with your own vector when it is called.
The transport log of RSTXSCRP outputs the language vector used for the export or import. If objects cannot be exported or imported because their language is not contained in the language vector of the source or target system, a corresponding message appears in the transport log.
Requirements
Styles and forms are made up of maintenance versions and active versions as well as foreign language versions (translations). When a style/form is exported only the active version of the style/form is exported. Maintenance versions are not transported. All existing translations of a style/form are also transported if their language is contained in the language vector.
If a style/form is flagged as "Translation not applicable", only its original language will be exported. Importing a style or form such as this, which is not to be translated, automatically deletes any existing translations 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 this device type in the target system.
Parameters to be specified:
The radio buttons Device type/Form/Style/Standard text select the transport object to be imported or exported.
Object name: Name of the standard text, style, form, or device type.
Mode: Export means download to file, IMPORT means upload from file.
File system: Allows you to choose whether the file is read/written locally (GUI file system) or on the application server (default setting).
File name: Path and file name of the file to be generated or read in the file system of the application server. The name selected here must fulfill any requirements specified by the R/3 platform (UNIX, Windows NT, AS/400). "/tmp/*******&&&&" appears as a default value. It is only a template and not the actual file name! If the default value is not overwritten, "*******" is replaced by the first eight letters of the object name, and "&&&&" by the file extensions ".TXT", ".STY", ".FOR" or ".PRI".
This parameter is not significant for local files and an input template appears for the local file name.
Binary file format: If this parameter is selected, a binary file format with a fixed record length is written or required for reading. This file format is not compatible with a "non-binary format", that is files for which the parameter was set during writing can only be read with a set parameter. The binary files generated by RSTXSCRP are identified by the string "RSTX@" (ASCII code) at the beginning of the file.
In binary format, the file contains an identifier indicating in which system character set the data was written. RSTXSCRP then performs a character set conversion from the file character set to the system character set of the current system when the file is imported. It is therefore possible to exchange files generated by RSTXSCRP between systems with different system character sets.
Important restriction: You are advised to only use the character set conversion when exchanging files between two systems with an identical number of characters. If objects in the source system contain characters which are not contained in the system character set of the target system, they are represented by a substitute character when converted and their contents are therefore changed. The objects are imported under a modified key if non-translatable characters are part of the object key (for example, a text name with East European special characters).
Display file contents: If this parameter is selected, the contents of the generated or read file are listed together with the transport log. Otherwise only the transport log is output.
Language vector: If this parameter has a value (that is, one or more language keys), this report parameter is used as a language vector for exporting or importing the language-specific objects. The profile parameter "zcsa/installed_languages" is used as the default language vector.
Only export original language: If this parameter is selected, only the original language for layout sets and styles is transported when 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: <no entry, use default value>
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
reward if u find use ful
regards
Nagesh.Paruchuri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.