How To Fix FB359 - No data was selected

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 359

• Message text: No data was selected

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 FB359 - No data was selected ?

  The SAP error message FB359 ("No data was selected") typically occurs when you are trying to execute a transaction or report in the Financial Accounting (FI) module, particularly when dealing with document postings, clearing, or reporting. This error indicates that the system did not find any data that meets the selection criteria you provided.
  Causes:
  
  Selection Criteria: The most common cause is that the selection criteria you entered do not match any existing data in the system. This could be due to incorrect date ranges, document numbers, or other filters.
  Data Availability: There may be no data available in the specified period or for the specified accounts.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view certain data, leading to no data being displayed.
  Posting Period: The posting period may be closed, preventing any data from being selected for that period.
  Filters: Additional filters or settings in the report or transaction may be too restrictive.
  
  Solutions:
  
  Check Selection Criteria: Review and adjust the selection criteria you are using. Ensure that the date ranges, document types, and other filters are correct and relevant.
  Verify Data Availability: Check if there is data available for the specified criteria. You can do this by running a broader report or checking the relevant tables directly.
  Authorization Check: Ensure that you have the necessary authorizations to access the data. You may need to contact your SAP security team if you suspect authorization issues.
  Open Posting Period: Verify that the posting period is open. If it is closed, you may need to open it or select a different period.
  Remove Filters: Temporarily remove any filters to see if data appears. If it does, gradually reapply filters to identify which one is causing the issue.
  
  Related Information:
  
  Transaction Codes: The error may occur in various transaction codes such as FB50 (Enter G/L Account Document), FB01 (Post Document), or when running reports like FBL1N (Vendor Line Item Display).
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific transaction or report you are using.
  Documentation: Refer to SAP documentation or help files for guidance on the specific transaction or report to understand the expected input and output.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a functional consultant who can provide more in-depth analysis and assistance.