How To Fix /SAPCND/GENERATOR356 - Deletion of additional objects &1 failed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/GENERATOR -

• Message number: 356

• Message text: Deletion of additional objects &1 failed

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 /SAPCND/GENERATOR356 - Deletion of additional objects &1 failed ?

  The SAP error message /SAPCND/GENERATOR356 indicates that there was a failure in the deletion of additional objects in the context of SAP's condition management or similar functionalities. This error typically arises during the process of managing condition records, where the system attempts to delete certain objects but encounters issues.
  Cause:
  The error can be caused by several factors, including:
  
  Dependencies: The object you are trying to delete may have dependencies or references in other areas of the system, preventing its deletion.
  Authorization Issues: The user may not have the necessary authorizations to delete the specified object.
  Data Integrity: There may be data integrity issues or inconsistencies in the database that prevent the deletion.
  System Locking: The object might be locked by another process or user, which can prevent deletion.
  Custom Code: If there are custom enhancements or modifications in the system, they might interfere with the standard deletion process.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Check Dependencies: Investigate if the object has any dependencies. You can use transaction codes like SE11 (Data Dictionary) or SE80 (Object Navigator) to check for references.
  Review Authorizations: Ensure that the user attempting the deletion has the necessary authorizations. You can check this in transaction SU53 (Authorization Check) after the error occurs.
  Data Consistency Check: Run consistency checks on the relevant tables or objects to identify any data integrity issues. You can use transaction codes like SE14 (Database Utility) to check and repair inconsistencies.
  Unlock Objects: If the object is locked, identify the locking process using transaction SM12 (Display and Delete Locks) and unlock it if appropriate.
  Check Custom Code: If there are custom developments, review the code to ensure it is not interfering with the deletion process. You may need to consult with your ABAP developers.
  Consult Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide additional context on why the deletion failed.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review the official SAP documentation related to condition management and object deletion for best practices and guidelines.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the issue persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.