How To Fix /PRA/RD035 - Log not found.

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/RD -

• Message number: 035

• Message text: Log 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 /PRA/RD035 - Log not found. ?

  The SAP error message /PRA/RD035 Log not found typically indicates that the system is unable to find a specific log file that is required for a particular process or transaction. This error is often associated with the SAP Revenue Accounting and Reporting (RAR) module, but it can occur in other contexts as well.
  Causes:
  
  Missing Log File: The log file that the system is trying to access does not exist. This could be due to deletion, archiving, or it was never created in the first place.
  Incorrect Configuration: The system may not be configured correctly to generate or store logs.
  Authorization Issues: The user may not have the necessary permissions to access the log files.
  Data Consistency Issues: There may be inconsistencies in the data that prevent the log from being generated or accessed.
  
  Solutions:
  
  Check Log File Existence: Verify if the log file exists in the expected location. If it has been deleted or moved, you may need to restore it from a backup or recreate it.
  Review Configuration Settings: Ensure that the configuration settings for logging in the relevant module are correctly set up. This may involve checking transaction codes related to logging and ensuring that logging is enabled.
  User Authorizations: Check the user roles and authorizations to ensure that the user has the necessary permissions to access the logs.
  Re-run the Process: If the log was not created due to an error in a previous process, try re-running the process that should generate the log.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that can resolve known issues.
  Check for Data Consistency: Use transaction codes like SLG1 (Application Log) to check for any related errors or inconsistencies in the data that may be causing the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to logging and error handling, such as SLG1 (Application Log) and SLG2 (Log Management).
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance. They can provide more detailed insights based on the specific context of your system.
  Documentation: Review the official SAP documentation for the module you are working with, as it may provide additional troubleshooting steps or configuration guidelines.
  
  By following these steps, you should be able to identify the cause of the /PRA/RD035 Log not found error and implement a suitable solution.