Skip to end of metadata
Go to start of metadata

Purpose

The purpose here is to describe the various editors available for SAPscript texts.

Overview

There are some text editors available for SAPscript inSAP systems. The is the line editor, which uses the internal ITF sapscript format. There is the MS Word text editor, which is now the default graphical editor. There is an old non-Unicode graphical PC editor which has been retired but is still available to customers if needed from the SAP Software Download Center. The graphical editors use the width of the MAIN window in the assicaited SAPscript form as the line length. Also the paragraph formats and character formats of the asssociated SAPscript form are available while editing this text. 

SAPscript Line Editor

The SAPscript Line Editor is the oldest editor and the text uses the internal SAPscript ITF format. This ITF format is an internal SAPscript format for storing and displaying SAPscript texts. Here you can have simple text characters or symbols passed from the application print program. To signify the beginning of a symbol, the special character & is used. So a symbol in the line editor would be entered as &Symbol_name&. If you want to print an actual '&' character, then it must be masked in the SAPscript Line Editor. i.e. It must be entered like this: <(>&<)>. So  the character '<' is also a special character used for the masking of characters that could be interpreted as special characters rather than normal text.

MS Word SAPscript Editor

The MS Word SAPscript Editor was introduced largely to deal with editing characters from multiple languages in Unicode systems.  In todays global environment is often necessary to process characters from multiple languages in SAP systems. The Unicode MS Word editor accomodates this and it is possible e.g. to copy and paste exotic characters from other applications into this editor. There are some restrictions with the MS Word Editor described in note 742662. Not all of the features of MS Word are available within the editor. e.g. Only the paragraph and character formats from the SAPscript form or the style of a Smart Form are possible. The MS Word Editor is the default graphical SAPscript editor.

SAPscript Legacy Text Editor

The old SAPscript Graphical PC Editor like the MS Word editor is WYSIWYG(What you see is what you get) editor. Texts are asssigned to SAPscript forms. By default this is the standard SAPscript form SYSTEM unless it is changed. 

Since SAPGUI for Windows Release 7.40 Compilation 2 (Patch 05) and higher, the controls for SAPscript Leagacy Text Editor are o longer available as standard. As per note: 2221815, the SAPscript Legacy Text Editor patch SAPSLTESP00_0-70001053.EXE can be downloaded from:

http://support.sap.com/swdc
-> Support Packages and Patches
-> Browse Download Catalog
-> SAP Frontend Components
-> SAPSCRIPT LEGACY TEXT EDITOR
-> SAPSCRIPT LEGACY TEXT EDITOR (Support Packages and Patches)
-> Win32

If you would like to include SAPscript legacy editor in a SAPGUI server build, please see the BC-FES-GUI note 2192210 for steps.

  • No labels

7 Comments

  1. Dear Aidan,

    isn't it strange that SAP is posting following sentence in SAP Note 2221815 ?

    • [ SAPscript Legacy Text Editor is an obsolete component, it was replaced by "MS Word as SAPScript Text Editor". You can find more information in the note 742662. ]

    Install or not Install? That is the question...!

     

    btw. I have opened an OSS Ticket as MS Word does not work in SE71 (SAP Gui 7.40 '2-05) ... Error 'TD 245'  (tongue)

     

    kind regards
    Jörg Sauterleute

  2. Hi Jörg,

    it is true that the old SAPscript Graphical PC Editor is obsolete and was replaced by the MS Word Editor some time ago. MS WOrd Editor is Unicode and supports multiple languages etc. However, some customers still prefer to use the old graphical editor even though it is obsolete. So it is available this way only if you want to use it rather thant he MS Word editor. If you already use the MS Word as SAPscript Editor, then it is not necessary to install the legact graphical editor.

    Regards,
    Aidan

  3. Hi Jörg,

    If you run report RSCPSETEDITOR from SE38 and acticvate the MS Word editor from there for SAPscript and Smart Forms, are you able to edit your forms via the MS Word Editor ok?

    Regards,
    Aidan

    1. Hi Aidan,

      I got answer from SAP OSS:
      even if you have activated MS Word as Standard graphical Editor (RSCPSETEDITOR) you still have to implement SAPscript Legacy Text Editor if you want to use graphical Form Painter. This means SAP is distinguishing between "PC-Editor" and "Form Painter" (SE71 > settings > Form Painter)

      This was not highlighted in SAP note 2221815, but you can find if you read carefully: (smile)

      For using of Graphical Painter by development of SAPscript Forms (Transaction SE71), the SAPscript Legacy Text Editor controls component should be installed additionally to SAP Windows GUI.

       

      So if you upgrade to SAP GUI 7.40 '2-05 you Basis team will have fun as developers will miss graphical Text Editor instantly.
      Will say, it's not a "like have" but a "must have" ...!

      Regards, Jörg S.

      1. Thanks Jörg, good point.

        1. MS Word as Standard graphical Editor is NOT the same as graphical Form Painter.
        2. The latter is an absolute MUST to have an overview of the windows layout, as it's painful to reconstruct it in one's mind based on the offsets specified in number of characters or even millimeters.
        3. Another thing to keep in mind: some companies (like the one I work in) go away from MS products, so MS Word is not available. So, instead of re-running printing programs to check changes in formatting, it's much easier to use a legacy graphical PC editor.

        Regards,

        Vlad S.

  4. Hi

    Do you know how to check, on an existing SAP GUI, if this "SAPscript Legacy Text Editor" package is installed?

    1. You can prove this by opening any SapScript Form (with SE71 > settings > Form Painter > graphical Form Painter = X ) If it's NOT installed you get error message that is described in snote 2221815 I mentioned above (wink)

      If you want to dig through SAP Gui ... DLLs you will find a hint in this SCN-thread http://scn.sap.com/thread/3810970