How To Fix SDDIC_DDLA_ANNOCHECK079 - Class '&1' for '&2' not found

SAP Error Message - Details

• Message type: E = Error

• Message class: SDDIC_DDLA_ANNOCHECK - Messages for annotation usage check

• Message number: 079

• Message text: Class '&1' for '&2' not found

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 SDDIC_DDLA_ANNOCHECK079 - Class '&1' for '&2' not found ?

  The SAP error message SDDIC_DDLA_ANNOCHECK079 indicates that a specific class (denoted as &1) for a particular object (denoted as &2) could not be found in the system. This error typically arises during the activation or generation of ABAP objects, particularly when there are issues with class definitions or dependencies.
  Cause:
  
  Missing Class Definition: The class specified in the error message does not exist in the system. This could be due to a missing transport, deletion, or an incomplete installation.
  Namespace Issues: The class might be in a different namespace that is not accessible or not properly defined in the current context.
  Transport Issues: If the class was supposed to be transported from another system, it might not have been included in the transport request or the transport might not have been imported correctly.
  Authorization Issues: The user might not have the necessary authorizations to access the class or its components.
  
  Solution:
  
  Check Class Existence: Use transaction code SE24 (Class Builder) to check if the class exists. If it does not, you may need to create it or restore it from a transport.
  Check Transport Requests: If the class is missing, check the transport requests to ensure that the class was included and that the transport was successfully imported.
  Namespace Verification: Ensure that the class is in the correct namespace and that your current user context has access to it.
  Rebuild or Activate: If the class exists but is not activated, try to activate it. Sometimes, reactivating the class can resolve dependency issues.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the class and its components.
  Debugging: If the issue persists, consider debugging the program or transaction that triggered the error to identify the exact point of failure.
  
  Related Information:
  
  Transaction Codes: 
  
  SE24: Class Builder
  SE80: Object Navigator
  SE11: Data Dictionary
  
  
  SAP Notes: Check SAP Notes for any known issues related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  Documentation: Review the documentation for the specific classes or objects involved to understand their dependencies and requirements.
  
  If the problem continues after trying the above solutions, it may be beneficial to consult with your SAP Basis or development team for further assistance.