How To Fix RMOR021 - Selection of positions was called up with empty object table

SAP Error Message - Details

• Message type: E = Error

• Message class: RMOR - OR: Open Reporting

• Message number: 021

• Message text: Selection of positions was called up with empty object table

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 RMOR021 - Selection of positions was called up with empty object table ?

  The SAP error message RMOR021, which states "Selection of positions was called up with empty object table," typically occurs in the context of the SAP Real Estate Management (RE-FX) module. This error indicates that the system attempted to execute a selection for positions (such as contracts, leases, or other objects) but found that the object table it was supposed to work with was empty.
  Causes:
  
  No Data Available: The most common cause is that there are no entries in the relevant object table for the selection criteria specified. This could be due to data not being created or existing data being deleted.
  Incorrect Selection Criteria: The selection criteria used in the report or transaction may not match any existing records, leading to an empty result set.
  Authorization Issues: The user may not have the necessary authorizations to view the data, which can result in the system not being able to retrieve any records.
  Configuration Issues: There may be configuration issues in the RE-FX module that prevent the system from accessing the necessary data.
  
  Solutions:
  
  Check Data Availability: Verify that there are entries in the relevant object table. You can do this by checking the database directly or using transaction codes related to the specific object type (e.g., contracts, leases).
  Review Selection Criteria: Ensure that the selection criteria you are using are correct and that they match existing records. Adjust the criteria if necessary.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the data. You can check this in the user roles and authorizations settings.
  Review Configuration: If the issue persists, review the configuration settings in the RE-FX module to ensure that everything is set up correctly. This may involve checking the settings for object types, status management, and other related configurations.
  Debugging: If you have access to technical resources, consider debugging the program or transaction that is generating the error to identify where the empty object table is being called.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in the RE-FX module, such as RECN (Contract Management), REIS (Investment Management), or RE80 (Real Estate Management).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review the official SAP documentation for the RE-FX module to understand the data model and how object tables are structured.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.