How To Fix CURTO1041 - PDS for material &1, plant &2, version &3 was deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: CURTO1 - PDS Generation (ERP system)

• Message number: 041

• Message text: PDS for material &1, plant &2, version &3 was deleted

What causes this issue?

A production version has been deleted in ERP. The system writes a change
pointer for the deletion. When transaction CURTO_CREATE is executed, the
change pointers are read and the related production data structures are
deleted in APO.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CURTO1041 - PDS for material &1, plant &2, version &3 was deleted ?

  The SAP error message CURTO1041 indicates that a Production Data Structure (PDS) for a specific material, plant, and version has been deleted. This error typically arises in the context of SAP Advanced Planning and Optimization (APO) or SAP Integrated Business Planning (IBP) when the system is trying to access a PDS that no longer exists.
  Cause:
  
  Deletion of PDS: The most straightforward cause is that the PDS for the specified material, plant, and version has been intentionally deleted by a user or through a batch job.
  Data Consistency Issues: There may be inconsistencies in the master data or planning data, leading to the system not being able to find the required PDS.
  Transport Issues: If the PDS was transported from one system to another (e.g., from development to production), it might not have been included in the transport request.
  Versioning Issues: The version specified may not be active or may have been deleted.
  
  Solution:
  
  Recreate the PDS: If the PDS was deleted unintentionally, you can recreate it using the relevant transaction codes (e.g., /SAPAPO/PDS for APO) or through the appropriate planning interface.
  Check Data Consistency: Use transaction codes like /SAPAPO/MDP to check for inconsistencies in master data and correct them as necessary.
  Review Transport Requests: If the PDS was supposed to be transported, check the transport logs to ensure it was included and successfully transported.
  Verify Version: Ensure that the version specified in the error message is valid and active. You can check this in the PDS maintenance transaction.
  Consult Documentation: Review SAP documentation or notes related to PDS management for any specific guidelines or troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/PDS, /SAPAPO/MDP, and /SAPAPO/CTM for managing PDS and checking planning data.
  SAP Notes: Check SAP Notes for any known issues or patches related to PDS management.
  User Authorization: Ensure that the user has the necessary authorizations to view or modify PDS data.
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or functional team for further investigation.