How To Fix CURTO1044 - PDS for material &1, plant &2, application &3, alternative &4 not deleted

CURTO1044 - Overview

• Message type: E = Error

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

• Message number: 044

• Message text: PDS for material &1, plant &2, application &3, alternative &4 not deleted

What causes this issue?

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

System Response

The production data structures could not be deleted, because orders or
quota arrangements exist in APO or the authorization check for object
C_APO_RTO was not successful.

How to fix this error?

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

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 CURTO1044 - PDS for material &1, plant &2, application &3, alternative &4 not deleted ?

  The SAP error message CURTO1044 indicates that a Process Data Structure (PDS) for a specific material, plant, application, and alternative could not be deleted. This error typically arises in the context of SAP Advanced Planning and Optimization (APO) or SAP Integrated Business Planning (IBP) when there are issues related to the PDS.
  
  Cause:
  
  Dependencies: The PDS may be linked to other objects or processes that prevent its deletion. For example, if there are active planning runs or dependencies on the PDS, it cannot be deleted.
  Authorization Issues: The user may not have the necessary authorizations to delete the PDS.
  Data Integrity: There may be data integrity issues or inconsistencies in the database that prevent the deletion.
  Active Usage: The PDS might be actively used in planning scenarios, which can lock it from being deleted.
  
  
  Solution:
  
  Check Dependencies: Review any dependencies or references to the PDS. Ensure that there are no active planning runs or other objects that