How To Fix DMCLG353 - &1 &2 marked for deletion; calculation not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: DMCLG - DMC Tool Development

• Message number: 353

• Message text: &1 &2 marked for deletion; calculation not possible

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 DMCLG353 - &1 &2 marked for deletion; calculation not possible ?

  The SAP error message DMCLG353 indicates that a certain object (like a master data record or a transaction) is marked for deletion, which prevents any calculations or operations from being performed on it. This error typically arises in the context of data management, particularly in modules related to data processing, such as SAP Data Management or SAP BW (Business Warehouse).
  Cause:
  
  Marked for Deletion: The primary cause of this error is that the object you are trying to process has been flagged as "marked for deletion." This could happen due to data cleansing activities, user actions, or system processes that identify certain records as obsolete or no longer needed.
  Data Integrity Issues: Sometimes, data integrity checks may lead to certain records being marked for deletion if they do not meet specific criteria or if they are found to be inconsistent with other data.
  
  Solution:
  
  Check the Object Status: Verify the status of the object in question. You can do this by navigating to the relevant transaction or data management screen and checking if the object is indeed marked for deletion.
  Unmark for Deletion: If the object should not be marked for deletion, you can unmark it. This typically involves:
  
  Accessing the relevant transaction or data management tool.
  Finding the record and changing its status to active or valid.
  
  
  Data Reprocessing: If the object is marked for deletion due to data integrity issues, you may need to correct the underlying data issues before reprocessing the object.
  Consult Documentation: Refer to SAP documentation or help resources for specific instructions related to the module you are working with, as the steps may vary based on the context.
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting SAP Notes for any known issues or patches related to this error.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use specific transaction codes to view or modify the status of the object (e.g., SE11 for data dictionary, SE16 for table display).
  SAP Notes: Check SAP Notes for any updates or patches that may address this error.
  Data Management Best Practices: Implementing best practices for data management can help prevent such issues in the future, including regular data audits and validation checks.
  
  By following these steps, you should be able to address the DMCLG353 error and ensure that your calculations can proceed without issues.