Working with Long Text

Some SAP transaction offers Text to be maintained in newer script text editor.  Here's one such example in Transaction VA01/VA02.

This script editor does not record and playback well with traditional transaction methods. If you change/add text during the recording, it will not be updated during normal run.

Please note that this behavior is also true for ABAP and any other program. It is not specific to Process Runner. However, Process Runner offers following workaround to this issue:

a. Switch to traditional text editor:

Switch to traditional editor during recording. In above example, if you click on "Detail" icon, it will switch to traditional text editor and all your recording will work fine.

Once you are in traditional text editor, enter/edit/change/delete your text here and click save to go back to the main transaction.

Once you are back to main transaction, you may have to save again so your recording takes you back to Process Runner.

Notes:

1. If you still do not see traditional editor as above, click on Go to->Change Editor to bring up correct editor as above.

2. You may also  be able to set preference, so SAP always offers traditional editor. To set this preference click Goto->Configure Editor.  (If you configured the editor during recording, you may want to do another clean recording)

3. Some transactions have different button/method to switch to traditional editor. So look for alternate ways on how to switch to traditional text editor before you start recording.  Example of ME21/22N is below. You will have to select "3 SAPscript editor" to go to traditional editor.

b. Use BAPI.

Many of these object have BAPI that allows to maintain text.

c. Use GUI Scripting

Use GUI Scripting recording/playback instead of Transaction. GUI Scripting will not offer as many features as regular Transaction method, it will record and playback new script editor control correctly without any changes.