CL_WORD_SAPSCRIPT_EDITOR

[MarkusHertach]

Hi Folks

In SAP GUI 7.40 Patchlevel 5 SAP remove the component SAPScript Legacy Text Editor. This means, that reports using the control CL_GUI_SAPSCRIPT_EDITOR no longer work. I use this control in a number of reports for inputting long formatted text and therefore need to replace it with what I think would be CL_WORD_SAPSCRIPT_EDITOR (the workaround of installing an Addon to get the legacy textedit control back into SAP Gui is no option as it is not getting installed).

I am having issues with CL_WORD_SAPSCRIPT_EDITOR especially concerning Smartform-Styles. There seems to be no decent way of passing a smartforms style to the class. I tried reverse engineering on the SMARTFORMS-Transaction without much success. Does anybody have an example or tutorial on how to use CL_WORD_SAPSCRIPT_EDITOR?

Thanks

Markus

[rosenberg_eitan]

Hi,

Have you checked the where the use for this class ?

On my system (740) it is mention once .

Have you consider using CL_GUI_TEXTEDIT or EDIT_TEXT function ?

Regards.

[MarkusHertach]

Hi Eitan

CL_GUI_TEXTEDIT is only suitable for unformatted text. EDIT_TEXT only for existing textmodules oder documentation. That's not what I am doing.

Regards

[RaymondGiuseppi]

Did you look for/find/read 2221815 - SAPscript Legacy Text Editor controls are not packed in SAP Windows GUI Installation?

(SAP Frontend Components" SAPSCRIPT LEGACY TEXT EDITOR" SAPSCRIPT LEGACY TEXT EDITOR)

Solution

The Installer for SAPscript Legacy Text Editor can be downloaded from SAP Software
(...)
-> SAPSCRIPT LEGACY TEXT EDITOR
(...)
The downloaded 'SAPSCRIPT LEGACY TEXT EDITOR' should be installed additionally on SAP Windows GUI 7.40 Patch 5 Compilation 2 and higher.
(...)

Hint: For sample, look for string  "word_editor" in function group STXB.

Regards,

Raymond

[MarkusHertach]

Hi Raymond

The mentioned Addon is not going to be installed. That's something I cannot control. So I need to get along without this component.

Yes I did look into function group STBX. that's what I meant with "transaction SMARTFORMS"

I guess that many dev's are going to struggle with the same problem over the coming weeks and months when more and more clients upgrade to Patchleven 5 or above. If you have a custom application using this editor you will probably face this issue.

Regards