How To Fix /ACCGO/DGR171 - No records found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/DGR -

• Message number: 171

• Message text: No records 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 /ACCGO/DGR171 - No records found ?

  The SAP error message /ACCGO/DGR171 No records found typically occurs in the context of the SAP General Ledger (G/L) accounting module, particularly when dealing with data retrieval or reporting functions. This error indicates that the system could not find any records that match the criteria specified in the request.
  Causes:
  
  Incorrect Selection Criteria: The parameters or filters applied in the report or transaction may not match any existing records in the database.
  Data Not Yet Posted: If the transaction or data entries have not been posted to the G/L, there will be no records to retrieve.
  Data Deletion: Records may have been deleted or archived, leading to the absence of data for the specified criteria.
  Authorization Issues: The user may not have the necessary authorizations to view the records, which can sometimes lead to misleading error messages.
  Incorrect Company Code or Period: The company code or the fiscal period specified may not have any transactions recorded.
  
  Solutions:
  
  Check Selection Criteria: Review the selection criteria used in the report or transaction. Ensure that the parameters (such as date range, company code, etc.) are correct and relevant.
  Verify Data Posting: Confirm that the relevant transactions have been posted to the G/L. If not, ensure that the necessary entries are made.
  Review Data Deletion/Archiving: Check if the records have been deleted or archived. If they have been archived, you may need to retrieve them from the archive.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the data. This can be done by checking the user roles and permissions.
  Adjust Company Code/Period: Make sure that the correct company code and fiscal period are selected. If you are unsure, consult with your finance team or SAP administrator.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as FB03 (Display Document), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP's support portal can provide valuable insights.
  Consult Documentation: Review SAP documentation or user manuals related to the specific module you are working with for additional context and troubleshooting steps.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or a technical consultant for further assistance.