How To Fix RMSRCPMIG035 - RESET could not be executed; status PP_OLD_DATA_DELETION = &1

SAP Error Message - Details

• Message type: E = Error

• Message class: RMSRCPMIG -

• Message number: 035

• Message text: RESET could not be executed; status PP_OLD_DATA_DELETION = &1

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 RMSRCPMIG035 - RESET could not be executed; status PP_OLD_DATA_DELETION = &1 ?

  The SAP error message RMSRCPMIG035 indicates that a reset operation could not be executed due to the status of the parameter PP_OLD_DATA_DELETION. This error typically arises in the context of data migration or data management processes within SAP, particularly when dealing with the Retail Management System (RMS) or similar modules.
  Cause:
  The error message suggests that the system is trying to perform a reset operation, but it is being blocked by the status of the PP_OLD_DATA_DELETION parameter. This parameter is likely related to the deletion of old data, and its status may indicate that the system is not in a state that allows for the reset to occur. Possible causes include:
  
  Incorrect Configuration: The parameter PP_OLD_DATA_DELETION may not be set correctly in the system configuration.
  Data Integrity Issues: There may be existing data that prevents the reset from being executed.
  System Lock: The system might be locked or in a state where certain operations cannot be performed.
  Migration Process: If this error occurs during a data migration process, it may indicate that the migration has not been completed successfully.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Parameter Status: Review the status of the PP_OLD_DATA_DELETION parameter. You can do this by navigating to the relevant configuration settings in SAP. Ensure that it is set to a value that allows for the reset operation.
  
  
  Review Logs: Check the system logs for any additional error messages or warnings that may provide more context about why the reset could not be executed.
  
  
  Data Cleanup: If the issue is related to old data, consider performing a cleanup of the data that may be causing the conflict. This may involve deleting or archiving old records that are no longer needed.
  
  
  System Status: Ensure that the system is not in a locked state. If necessary, consult with your SAP Basis team to check for any locks or ongoing processes that may be affecting the system.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the RMS or the specific module you are working with. There may be specific instructions or known issues related to this error.
  
  
  Contact SAP Support: If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. Provide them with the error message and any relevant details about the context in which it occurred.
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to the error message RMSRCPMIG035. SAP frequently publishes notes that address specific issues and provide solutions or workarounds.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help you navigate to the configuration settings or logs (e.g., SE11 for data dictionary, SM37 for job monitoring).
  User Forums: Consider searching or posting in SAP community forums where other users may have encountered similar issues.
  
  By following these steps, you should be able to diagnose and resolve the error message RMSRCPMIG035 effectively.