Do you have any question about this error?
Message type: E = Error
Message class: OO - Class Builder/API
Message number: 670
Message text: Persistent classes are currently not supported by this editor
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
OO670
- Persistent classes are currently not supported by this editor ?The SAP error message OO670, which states "Persistent classes are currently not supported by this editor," typically occurs when you are trying to edit or work with a persistent class in the ABAP Development Tools (ADT) or the ABAP Workbench, and the editor you are using does not support the specific features or functionalities required for persistent classes.
Cause:
- Editor Limitation: The editor you are using (such as the ABAP Editor or a specific version of ADT) does not support editing persistent classes, which are typically used in the context of ABAP Objects and database interactions.
- Incorrect Context: You may be trying to open a persistent class in a context that does not support it, such as a non-ABAP context or a different type of editor.
- Version Compatibility: The version of the tools you are using may not fully support the features related to persistent classes.
Solution:
- Use the Correct Editor: Ensure that you are using the appropriate editor for editing persistent classes. For example, use the ABAP Class Builder (transaction SE24) or the ABAP Development Tools in Eclipse.
- Check for Updates: Make sure that your SAP system and development tools are up to date. Sometimes, newer versions of the tools provide better support for persistent classes.
- Switch to a Different Tool: If you are using a specific editor that does not support persistent classes, switch to a different tool that does. For example, use the ABAP Class Builder instead of the standard ABAP Editor.
- Consult Documentation: Refer to the SAP Help Portal or relevant documentation for guidance on working with persistent classes and the supported editors.
Related Information:
If the problem persists after trying the above solutions, consider reaching out to your SAP Basis or development team for further assistance, as they may have additional insights or access to system logs that can help diagnose the issue.
Get instant SAP help. Start your 7-day free trial now.
OO669
Test environment not supported for Test Classes!
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
OO668
Implementation added for the method &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
OO671
Message class &1 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...
OO672
The class include structure cannot be changed by transaction SNOTE/SCWB.
What causes this issue? You have tried to change the class Include structure (local class types) using the Note Assistant or the Correction Workbench...
Click on this link to search all SAP messages.