How To Fix PPDS_PB035 - Simulation version was not overwritten

SAP Error Message - Details

• Message type: E = Error

• Message class: PPDS_PB - Messages for New Fiori OData Planning Board

• Message number: 035

• Message text: Simulation version was not overwritten

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 PPDS_PB035 - Simulation version was not overwritten ?

  The SAP error message PPDS_PB035 indicates that the simulation version in the Production Planning and Detailed Scheduling (PP/DS) module was not overwritten as expected. This error typically arises during the planning process when there is an attempt to overwrite an existing simulation version, but the system prevents this action due to certain conditions.
  Causes:
  
  Version Locking: The simulation version may be locked by another user or process, preventing it from being overwritten.
  Authorization Issues: The user may not have the necessary authorizations to overwrite the simulation version.
  Configuration Settings: The system configuration may restrict overwriting of simulation versions under certain conditions.
  Data Integrity Issues: There may be data integrity issues or inconsistencies that prevent the simulation version from being updated.
  Incorrect Version Selection: The version being targeted for overwriting may not be correctly specified or may not exist.
  
  Solutions:
  
  Check Locks: Verify if the simulation version is locked by another user or process. If so, wait for the lock to be released or contact the user who has locked it.
  Review Authorizations: Ensure that the user has the necessary authorizations to perform the overwrite operation. This may involve checking roles and permissions in the SAP system.
  Configuration Review: Review the configuration settings in the PP/DS module to ensure that overwriting of simulation versions is allowed. This may involve consulting with a system administrator or SAP consultant.
  Data Consistency Check: Perform a data consistency check to identify and resolve any issues that may be preventing the overwrite. This may involve running specific SAP reports or transactions designed for data validation.
  Correct Version Identification: Double-check that the correct simulation version is being targeted for the overwrite. Ensure that the version exists and is correctly referenced in the process.
  
  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 PP/DS to understand the functionality and limitations regarding simulation versions.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after trying the above solutions, it may be beneficial to escalate the matter to your SAP support team or consult with an SAP expert for further assistance.