How To Fix OO628 - You can only instance non-abstract persistent classes in the protected s.

SAP Error Message - Details

• Message type: E = Error

• Message class: OO - Class Builder/API

• Message number: 628

• Message text: You can only instance non-abstract persistent classes in the protected s.

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message OO628 - You can only instance non-abstract persistent classes in the protected s. ?

  The SAP error message OO628, "You can only instance non-abstract persistent classes in the protected s," typically occurs in the context of ABAP Object-Oriented programming when you attempt to create an instance of an abstract class or when there is an issue with the class definition in the context of persistence.
  Cause:
  
  
  Abstract Class Instantiation: The most common cause of this error is trying to instantiate an abstract class. In ABAP, abstract classes cannot be instantiated directly; they are meant to be subclassed, and only concrete (non-abstract) classes can be instantiated.
  
  
  Incorrect Class Definition: If the class you are trying to instantiate is defined as abstract or if it does not meet the requirements for persistence (e.g., it lacks the necessary attributes or methods), this error can occur.
  
  
  Protected Constructor: If the constructor of the class is declared as protected, it means that the class cannot be instantiated outside of its own class or its subclasses. If you are trying to instantiate it from outside, this will lead to the error.
  
  
  Solution:
  
  
  Check Class Definition: Ensure that the class you are trying to instantiate is not abstract. If it is abstract, you need to create a subclass that implements the abstract methods and instantiate that subclass instead.
  
  
  Use Concrete Classes: If you need to create an instance, make sure you are using a concrete class that is not abstract and has a public constructor.
  
  
  Review Access Modifiers: If the constructor is protected, consider changing it to public if you need to instantiate the class from outside. Alternatively, ensure that you are instantiating it from within a subclass.
  
  
  Check for Persistence: Ensure that the class is defined correctly for persistence if you are working with persistent objects. This includes having the necessary attributes and methods defined.
  
  
  Related Information:
  
  
  Abstract Classes: In ABAP, abstract classes are defined using the ABSTRACT keyword and cannot be instantiated directly. They are used to define a common interface or base functionality for subclasses.
  
  
  Persistence in ABAP: For a class to be persistent, it must be defined in a way that allows it to be stored in the database. This typically involves defining attributes that correspond to database fields and implementing methods for data retrieval and storage.
  
  
  Debugging: If you encounter this error, you can use the ABAP debugger to trace where the instantiation is happening and check the class definitions involved.
  
  
  By following these guidelines, you should be able to resolve the OO628 error and successfully instantiate the desired class.