Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SY - ABAP/4 system messages
Message number: 420
Message text: Breakpoints and settings made were saved
The system saved the selected settings <ZK>System debugging</> and
<ZK>Always create an exception object when debugging</> as well as the
breakpoints.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
SY420
- Breakpoints and settings made were saved ?The SAP error message SY420 typically indicates that there is an issue related to breakpoints and settings in the ABAP debugger. This message is often encountered when a user tries to execute a program or transaction that has breakpoints set, and the system is informing the user that these breakpoints and settings have been saved.
Cause:
- Active Breakpoints: The most common cause of this message is that there are active breakpoints in the code that the user is trying to execute. This can happen if the user has previously set breakpoints in the ABAP debugger and has not removed them.
- Debugging Session: If a debugging session was interrupted or not properly closed, the breakpoints may still be active.
- User-Specific Settings: The message may also appear if there are user-specific settings or configurations that are causing the debugger to behave unexpectedly.
Solution:
Remove Breakpoints:
- Open the ABAP debugger by executing the program or transaction that is causing the error.
- In the debugger, navigate to the "Breakpoints" tab.
- Remove any active breakpoints by selecting them and choosing the option to delete or deactivate them.
Reset Debugger Settings:
- If you want to reset all your debugger settings, you can do this by going to the menu and selecting
Utilities
>Settings
>Reset
.Check User-Specific Settings:
- If the issue persists, check if there are any user-specific settings that might be affecting the debugger. You can do this by going to
Utilities
>Settings
in the debugger and reviewing the options.Log Off and Log Back In:
- Sometimes, simply logging off from the SAP system and logging back in can clear any temporary issues related to the debugger.
Consult with Basis Team:
- If the problem continues, it may be necessary to consult with your SAP Basis team to check for any system-wide issues or configurations that might be affecting the debugger.
Related Information:
By following these steps, you should be able to resolve the SY420 error and continue working with your SAP system effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
SY419
Memory monitoring switched off
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SY418
Memory monitoring switched on
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SY421
Specified comparison operator is not permitted
What causes this issue? You may only use one of the following comparison operators with conditional watchpoints: The system issues an error message a...
SY422
Program & does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.