How To Fix /SAPAPO/CURTO_PPE035 - PDS was generated again (maintenance time stamp ignored)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/CURTO_PPE -

• Message number: 035

• Message text: PDS was generated again (maintenance time stamp ignored)

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 /SAPAPO/CURTO_PPE035 - PDS was generated again (maintenance time stamp ignored) ?

  The SAP error message /SAPAPO/CURTO_PPE035 PDS was generated again (maintenance time stamp ignored) typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there is an issue with the Production Data Structure (PDS) being regenerated. This can happen for various reasons, and understanding the cause and potential solutions is essential for resolving the issue.
  Cause:
  
  PDS Regeneration: The error indicates that the PDS has been regenerated, and the maintenance timestamp is being ignored. This can happen if there are changes in the master data or if the PDS is being updated due to changes in the planning environment.
  Master Data Changes: Changes in the master data (like changes in resources, products, or production processes) can trigger the regeneration of the PDS.
  Configuration Issues: There may be configuration issues in the APO system that lead to unnecessary regeneration of the PDS.
  Data Consistency: Inconsistencies in the data or issues with the data model can also lead to this error.
  
  Solution:
  
  Check Master Data: Review any recent changes made to the master data that could have triggered the PDS regeneration. Ensure that all necessary data is consistent and correctly maintained.
  Review PDS Settings: Check the settings and configurations related to the PDS in the APO system. Ensure that the PDS is set up correctly and that there are no conflicting settings.
  Rebuild PDS: If the PDS is corrupted or not functioning as expected, consider rebuilding it. This can be done through the relevant transaction codes in SAP APO.
  Check for Notes and Patches: Look for any SAP Notes or patches that may address this specific error. Sometimes, SAP releases updates that fix known issues.
  Consult Documentation: Review the SAP documentation related to PDS and APO to ensure that you are following best practices for maintaining and updating PDS.
  System Logs: Check the system logs for any additional error messages or warnings that could provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/PDS for managing PDS and /SAPAPO/MC62 for checking the consistency of master data.
  SAP Community: Engage with the SAP Community or forums where other users may have encountered similar issues and can provide insights or solutions.
  SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.