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

SDDIC_DDLA_ANNOCHECK079 - Overview

• 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.

SDDIC_DDLA_ANNOCHECK079 - Details

• 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