How To Fix /RPM/MIGRATION359 - Could not read MPP; max. doc. size limit may be less than file size

SAP Error Message - Details

• Message type: E = Error

• Message class: /RPM/MIGRATION -

• Message number: 359

• Message text: Could not read MPP; max. doc. size limit may be less than file size

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/MIGRATION359 - Could not read MPP; max. doc. size limit may be less than file size ?

  The SAP error message /RPM/MIGRATION359 indicates that the system is unable to read a Migration Package (MPP) because the maximum document size limit set in the system is less than the size of the file you are trying to process. This typically occurs during data migration or when importing large files into the SAP system.
  Cause:
  
  File Size Exceeds Limit: The size of the Migration Package (MPP) you are trying to upload exceeds the maximum document size limit configured in the SAP system.
  Configuration Settings: The system settings for maximum document size may not be configured to accommodate larger files, which can be a common issue when dealing with large datasets.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check Current Document Size Limit:
  
  You can check the current maximum document size limit in the SAP system by navigating to the relevant configuration settings. This is usually found in the transaction code RZ10 or RZ11 where you can view and modify profile parameters.
  
  
  
  Increase the Maximum Document Size:
  
  If the current limit is too low, you can increase it. The parameter you need to look for is typically max_file_size or similar, depending on your SAP version. 
  You can set a higher value for this parameter to accommodate larger files. For example, you might set it to a value that is larger than the size of your MPP file.
  
  
  
  Restart the System:
  
  After making changes to the configuration, you may need to restart the SAP system for the changes to take effect.
  
  
  
  Split the Migration Package:
  
  If increasing the limit is not feasible or if you prefer not to change system settings, consider splitting the Migration Package into smaller files that are within the current size limit.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation or help portal for specific instructions related to your version of SAP, as the parameters and their settings may vary.
  
  
  
  Contact SAP Support:
  
  If you continue to experience issues after trying the above solutions, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like RZ10, RZ11, and SCC4 for system configuration and settings.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error message.
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to resolve the error and successfully read the Migration Package.