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

/RPM/MIGRATION390 - Overview

• 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