You can use this function to adjust the user-specific settings in the ABAP Workbench.
Your personal settings are accessible from the Object Navigator or any other tool in the ABAP Workbench. To display the settings, choose Utilities ® Settings.
Tool |
Setting |
Description |
Workbench |
Display background picture |
If you set this option, a background picture is displayed in the Object Navigator. |
No picture |
If you set this option, no background picture is displayed. |
|
ABAP Editor |
Front-End Editor (New) |
Enables the new Front-End Editor mode of the ABAP Editor. See also: Front-End Editor (Source Code Mode).
The Front-End Editor is available with SAP GUI for Windows 6.40 Patch Level 10 or higher. In order to have the editor integrated into the ABAP Workbench and use all related transactions, you need the appropriate SAP system version. The first version supporting the new editor is SAP NetWeaver 2004s. |
Front-End Editor (Old) |
Enables the old Front-End Editor. When you work in this mode, the source code of your program is loaded at the frontend and can be edited locally. See also: Front-End Editor (Plain Text Mode). |
|
Back-End Editor |
The conventional
line-based Back-End Editor. |
|
Numbering |
The options With and Without line numbering apply only to the old Front-End Editor. |
|
Compression |
You can use the option With compression logic to compress logical blocks of ABAP coding. For more information, see Using Compression Logic. |
|
Path for local editing |
This is the place where the program is downloaded or stored temporarily. From there you can also start a local editor. This option applies only to the Front-End Editor (Plain Text Mode). |
|
Upper-/lowercase conversion in display mode
|
This option is based on the Convert upper/lowercase settings of the Pretty Printer. The Keyword uppercase option is not supported for performance reasons. There is no special formatting in display mode if this option is not selected. |
|
Pretty Printer |
Indent |
Indents lines in the ABAP source code. For example, all statements belonging to an event are indented by two characters. See also: Improving the Layout. |
Convert upper-/lowercase
|
This option allows you to standardize the source code display. ● Lowercase (for the entire program apart from literals and comments). ● Uppercase (for the entire program apart from literals and comments). ● Keyword uppercase (highlights ABAP keywords). |
|
Split-Screen Editor |
Window arrangement |
You can arrange the programs either next to each other or one above the other in the Split-Screen Editor. |
Comparison operations |
If you choose Ignore indentations, the system
recognizes the program lines as identical as long as they have the same
contents, even if they are indented differently. For more information, see Special Split-Screen Functions. |
|
Class Builder
|
Display filter |
Options for displaying the components of global classes or interfaces in the Class Builder. They allow you to extend or restrict the standard display. |
Scope Filter |
Restricts the display of class components to instances or static components. |
|
Screen Painter |
Graphical layout editor |
If you set this option, the system uses the graphical layout editor in the Screen Painter. If the option is not set, the system starts the alphanumeric editor. |
Menu Painter |
Output length in status maintenance
|
Function code: The function code field in the Menu Painter can be set to allow input length between 4 and 20 characters. Text length: The text field for function texts in the Menu Painter can be set to allow input length between 10 and 40 characters. Note that these user-defined settings are only valid in the status maintenance screen of the Menu Painter. |
Front-end platform
|
Front-End: All function codes maintained in the Menu Painter are platform-independent but the function key names are not. By selecting a platform, you ensure that the function keys are labeled using the convention of the selected platform. |
|
Function Builder |
Check syntax in test
|
When you test a
function module, the system can check the syntax of the function group to
which the function module belongs. |