How To Fix ADW035 - No entries were recorded

SAP Error Message - Details

• Message type: E = Error

• Message class: ADW - Advanced Developer Workplace

• Message number: 035

• Message text: No entries were recorded

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 ADW035 - No entries were recorded ?

  The SAP error message ADW035 ("No entries were recorded") typically occurs in the context of data extraction or reporting, particularly when using the SAP Data Warehousing (SAP BW) or SAP BusinessObjects tools. This message indicates that the system did not find any data entries that match the criteria specified in the query or report.
  Causes:
  
  No Data Available: The most straightforward cause is that there are simply no records in the database that meet the selection criteria defined in the query.
  Incorrect Selection Criteria: The filters or parameters set in the query may be too restrictive, leading to no matching records.
  Data Load Issues: There may have been issues during the data loading process, resulting in no data being available in the target InfoProvider or data source.
  Time Period Selection: If the query is set to a specific time period, and there are no records for that period, this error can occur.
  Authorization Issues: The user may not have the necessary authorizations to view the data, leading to an empty result set.
  
  Solutions:
  
  Check Data Availability: Verify that there is data in the underlying tables or InfoProviders that should be returned by the query. You can do this by running a direct SQL query or checking the data in the relevant InfoProvider.
  Review Selection Criteria: Examine the filters and parameters used in the query. Adjust them to be less restrictive if necessary.
  Data Load Verification: Ensure that the data load processes (e.g., ETL jobs) have completed successfully and that data is present in the target InfoProviders. Check for any errors in the data load logs.
  Adjust Time Period: If applicable, modify the time period selection to include a broader range or check for data in the specified period.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the data. This may involve checking roles and permissions in the SAP system.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like RSA1 (Data Warehousing Workbench) to check InfoProviders and data loads.
  Logs and Monitoring: Check the logs for data load processes in the SAP BW system to identify any issues that may have occurred during data extraction or loading.
  Documentation: Refer to SAP documentation or help resources for specific details on the query or reporting tool you are using, as the context may vary.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP Basis or BW team for further investigation.