How To Fix /RPM/MIGRATION390 - No documents found for review &1; migration skipped

SAP Error Message - Details

• Message type: E = Error

• Message class: /RPM/MIGRATION -

• Message number: 390

• Message text: No documents found for review &1; migration skipped

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 /RPM/MIGRATION390 - No documents found for review &1; migration skipped ?

  The SAP error message /RPM/MIGRATION390 No documents found for review &1; migration skipped typically occurs during the migration process in SAP, particularly when using the SAP Real Estate Management (RE-FX) module or similar migration tools. This error indicates that the system did not find any documents that meet the criteria for migration, which leads to the migration process being skipped.
  Causes:
  
  No Documents Available: The most straightforward cause is that there are indeed no documents available in the specified category or selection criteria for migration.
  Incorrect Selection Criteria: The selection criteria set for the migration process may be too restrictive or incorrect, leading to no documents being selected.
  Data Not Prepared: The data may not have been properly prepared or uploaded into the system prior to the migration attempt.
  Authorization Issues: The user executing the migration may not have the necessary authorizations to view or access the documents.
  Configuration Issues: There may be configuration issues in the migration settings or parameters that prevent documents from being recognized.
  
  Solutions:
  
  Check Document Availability: Verify that there are indeed documents available for migration in the specified category. You can do this by running a report or query to list the documents.
  Review Selection Criteria: Reassess the selection criteria used for the migration. Ensure that they are set correctly to include the documents you wish to migrate.
  Data Preparation: Ensure that all necessary data has been prepared and is available in the system. This may involve checking data uploads or previous migration steps.
  User Authorizations: Check the user authorizations to ensure that the user has the necessary permissions to access the documents for migration.
  Configuration Review: Review the migration configuration settings to ensure they are set up correctly. This may involve consulting with your SAP Basis or technical team.
  Logs and Traces: Check the migration logs and traces for any additional error messages or warnings that could provide more context on why no documents were found.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review the official SAP documentation for the migration process you are using, as it may provide insights into common issues and their resolutions.
  Community Forums: Consider searching or posting in SAP community forums or support channels, as other users may have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.