How To Fix UD035 - Log & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: UD - EDM - Enterprise Data Model

• Message number: 035

• Message text: Log & 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 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 UD035 - Log & does not exist ?

  The SAP error message UD035, which states "Log & does not exist," typically occurs in the context of the SAP system when a user attempts to access a log that is either missing or has not been created. This error can arise in various scenarios, such as during the execution of certain transactions or reports that rely on logs for tracking changes or processes.
  Causes of UD035 Error
  
  Log Not Created: The log may not have been generated due to the process not being executed correctly or completely.
  Incorrect Log Reference: The log identifier or reference number provided may be incorrect or does not match any existing logs in the system.
  Log Deletion: The log may have been deleted or purged from the system due to retention policies or manual deletion.
  Authorization Issues: The user may not have the necessary authorizations to view the log, leading to the perception that it does not exist.
  System Configuration: There may be configuration issues in the system that prevent logs from being created or stored properly.
  
  Solutions to UD035 Error
  
  Verify Log Reference: Check the log reference number you are using to ensure it is correct. If you are unsure, consult with your team or check the relevant transaction history.
  Check Log Creation: Ensure that the process that should generate the log was executed successfully. If it was not, try to rerun the process.
  Review Deletion Policies: Check if there are any retention policies in place that might have led to the log being deleted. If necessary, consult with your system administrator.
  Authorization Check: Ensure that you have the necessary authorizations to access the log. If not, contact your SAP security team to request the appropriate access.
  Consult SAP Notes: Look for any relevant SAP Notes or documentation that might address this specific error. SAP frequently updates its knowledge base with solutions for common issues.
  System Configuration Review: If the issue persists, it may be necessary to review the system configuration related to logging. This may require assistance from a technical consultant or SAP Basis team.
  
  Related Information
  
  Transaction Codes: Depending on the context of the error, you may be using specific transaction codes that are relevant to the logs you are trying to access (e.g., SLG1 for application logs).
  SAP Support: If you are unable to resolve the issue, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error, including the transaction code and any steps leading up to the error.
  Documentation: Review SAP documentation related to the specific module or process you are working with, as it may provide insights into log management and troubleshooting.
  
  By following these steps, you should be able to identify the cause of the UD035 error and take appropriate action to resolve it.