How To Fix FMITPOMC072 - Doc. overview does not contain data; choose different selection criteria

SAP Error Message - Details

• Message type: E = Error

• Message class: FMITPOMC - Tranfer Transaction for Subledger Account

• Message number: 072

• Message text: Doc. overview does not contain data; choose different selection criteria

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 FMITPOMC072 - Doc. overview does not contain data; choose different selection criteria ?

  The SAP error message FMITPOMC072, which states "Doc. overview does not contain data; choose different selection criteria," typically occurs when you are trying to access a document overview in the SAP system, but the selection criteria you have provided do not return any results. This can happen in various SAP modules, particularly in Financial Management (FM) or Controlling (CO).
  Causes:
  
  Incorrect Selection Criteria: The most common cause is that the selection criteria (such as date range, document type, or other filters) do not match any existing records in the database.
  Data Not Yet Posted: If you are looking for documents that have not yet been posted or are in a different status, they will not appear in the overview.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view certain documents, leading to an empty overview.
  Data Archiving: If the data has been archived, it may not be available in the current view.
  System Configuration: There may be configuration settings that limit the visibility of certain documents based on user roles or other criteria.
  
  Solutions:
  
  Review Selection Criteria: Double-check the selection criteria you are using. Ensure that the date range, document type, and other filters are set correctly.
  Broaden Criteria: Try broadening the selection criteria to see if any documents appear. For example, if you are filtering by a specific date, try removing the date filter or expanding the date range.
  Check Document Status: Ensure that the documents you are looking for are in the correct status and have been posted.
  User Authorizations: Verify that you have the necessary authorizations to view the documents. You may need to contact your SAP security administrator for assistance.
  Consult with IT: If you suspect that data archiving or system configuration is affecting your ability to view documents, consult with your IT department or SAP Basis team for further investigation.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the relevant transaction codes that may be used to access document overviews, such as FMAVCR01 for budget consumption or other related transactions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Refer to SAP documentation or user manuals for guidance on how to properly use the document overview features in the specific module you are working with.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.