How To Fix /SAPAPO/CURTO_PPE036 - PDS was generated again in FORCE mode (time stamp was ignored)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/CURTO_PPE -

• Message number: 036

• Message text: PDS was generated again in FORCE mode (time stamp was 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_PPE036 - PDS was generated again in FORCE mode (time stamp was ignored) ?

  The SAP error message /SAPAPO/CURTO_PPE036 indicates that a Production Data Structure (PDS) was regenerated in FORCE mode, and the time stamp of the existing PDS was ignored. This typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there are changes in the planning data that necessitate the regeneration of the PDS.
  Cause:
  
  Changes in Master Data: The most common cause is that there have been changes in the master data (e.g., changes in resources, production versions, or other relevant data) that require the PDS to be updated.
  Manual Regeneration: The PDS may have been manually regenerated by a user or through a batch job, which forces the regeneration regardless of the existing timestamp.
  Configuration Settings: Certain settings in the system may be configured to always regenerate PDS in FORCE mode under specific conditions.
  
  Solution:
  
  Review Changes: Check the changes made to the master data that triggered the regeneration. Ensure that these changes are necessary and correct.
  Check PDS Settings: Review the settings related to PDS generation in the APO system. Ensure that the settings align with your business processes and requirements.
  Regenerate PDS: If the regeneration was unintentional, you may want to regenerate the PDS again without using FORCE mode, allowing the system to consider the existing timestamp.
  Monitor for Recurrence: After addressing the immediate issue, monitor the system for any further occurrences of this error to ensure that it does not happen again.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like /SAPAPO/PDS to view and manage PDS in the APO system.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or fixes related to this error message.
  Documentation: Refer to the SAP APO documentation for detailed information on PDS management and regeneration processes.
  
  If the issue persists or if you need further assistance, consider reaching out to your SAP support team or consulting with an SAP expert who specializes in APO.