SAP Note 26526 - Conversion of SAPscript texts, Release 3.0

Symptom:

Which conversion programs (both directions) are available for SAPscript texts? How are these conversions built into the R/3 system?

Other terms

SAPscript, Conversion, Format conversion, ITF, RTF, ASCII

Reason and Prerequisites

This note is not an error note, but merely an overview of the filters available in SAPscript and how they are built into Release 3.0 and higher.

Solution

SAPscript texts are stored in Interchange Text Format (ITF). SAPscript also provides conversion programs for the text file formats Rich Text (RTF) and ASCII.
RTF files contain the entire formatting information of a text and can be both interpreted and also generated by all the common word processing packages.
In ASCII files, the text is stored without any formatting information. The only layout element available is the line break. However, different character sets are supported.
The SAPscript editors offer the following functionality:

Transfer of texts in different formats

You can execute the following from within the SAPscript editor:

• export SAPscript texts into a local file in ITF, RTF or ASCII format

• import local files in ITF, RTF or ASCII format and insert them as an ITF text at the cursor position.
  

You can find this function in the editors under:
Text -> Upload... / Text -> Download..., Documentation -> Upload... /Documentation ->Download...
or
Folder -> Upload... / Folder -> Download.....

The result of the individual transfers is as follows:

1. ITF export (SAPscript text -> local ITF file)

A leader with the text header information is prefixed to the output file. A text header is also constructed from this leader should the file be imported again. Following this is the text just as it is displayed in the editor that is, with all character and paragraph marks, symbols, commands and so on.

2. ITF import (local ITF file -> SAPscript text):

Both ITF files with a leader (see itm 1.) and those without a leader can be imported. If a header with specifications for style and layout set exists, then the style and the layout set in the text and folder editor are given these values (this does not apply to the documentation editor!).

3. RTF export (SAPscript text -> local RTF file):

In this case, an RTF file is created where the character and paragraph formatting from the style or the layout set of the original text are (to a large extent) retained.
Variable symbols in the ITF text are replaced. INCLUDEs and control structures are broken up, comments ignored.
If a document template is specified, then a format conversion into this document template is started from the SAPscript format (style or layout set) relevant to the character and paragraph formatting. This format conversion is described in Note 26528.
RTF files can be imported easily into modern word processing packages; in the case of older DOS programs, you will have to carry out some preliminary work first:
For Microsoft Word (as of Version 5.0), the RTF file (plus style sheet) must, for example, be converted into a Word text file using the following command:
For MS-DOS: rtf_dos file1.rtf file2.txt file3.dfv /o/c
or - " - /o/m
For OS/2: rtf_os2 file1.rtf file2.txt file3.dfv /o/c
or - " - /o/m
(/o if file2.txt already exists, then it is overwritten without the user being asked to confirm this
/c style sheet file3.dfv is created again
/m style sheet file3.dfv already exists and might be modified)

4. RTF import (local RTF file -> SAPscript text):

NB: the source text must have been created with a document template and stored as an RTF file. On the R/3 side, a style or layout set should exist whose character and paragraph formats correspond to those of the document template. The keys of both should be the same. If this is not the case, or if this is not possible because the descriptions in the document reference are different, it is still possible to specify a Format conversion (see Note 26528)
If "style" or "layout set" are specified in the second dialog box, then style and/or layout are set to these values (either with or without format conversion) in the text editor and folder editor.

5. ASCII export (SAPscript text -> local ASCII file):

All the formatting in the ITF text (with the exception of line feeds and tabs) is removed. The pure ASCII text is transferred exactly as it would appear in printed form (only content of text!). The only formatting possible is provided by the parameter "Line width". Variable symbols are replaced, INCLUDEs and control structures removed.

The ITF text can be converted into any character set that is maintained in spool management (SPAD).

6. ASCII import (local ASCII file --> SAPscript text):

Any ASCII file can be uploaded into the SAPscript editor. The character set of this file (i.e. its number in spool management (SPAD)) should be specified; data is then converted into the character set of the system.



Function modules for this environment

The following function modules are documented:

• IMPORT_TEXT:
  Upload of local file + conversion

• EXPORT_TEXT:
  Conversion + download to local file

• TRANSFER_TEXT:
  IMPORT_TEXT + EXPORT_TEXT + dynpros, that is exactly what is shown in the editors

• CONVERT_TEXT (up to Basis Release 4.6D; afterwards, the function module must be replaced by one of the following):
  Mere conversion of text formats; not ITF-->ITF!

• CONVERT_ITF_TO_ASCII (as of Basis Release 6.10):
  Conversion from ITF to ASCII

• CONVERT_ITF_TO_RTF (as of Basis Release 6.10):
  Conversion from ITF to RTF

• CONVERT_ASCII_TO_ITF (as of Basis Release 6.10):
  Conversion from ASCII to ITF

CONVERT_RTF_TO_ITF (as of Basis Release 6.10):
Conversion from RTF to ITF