How To Fix 60558 - Comp.group to which apartment belongs is being processed by &

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 558

• Message text: Comp.group to which apartment belongs is being processed by &

What causes this issue?

You want to delete a comparative apartment which is already assigned to
a comparative portfolio. The system also deletes the apartment from the
portfolio. This action cannot be carried out at present, since another
user is processing the portfolio.

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?

Contact the user or call up the function "Delete comparative apartment"
again if the portfolio is no longer being processed.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 60558 - Comp.group to which apartment belongs is being processed by & ?

  The SAP error message 60558 typically indicates that there is a problem related to the processing of a particular component group or apartment in the SAP system. This error often arises in the context of SAP's handling of parallel processing or when multiple users or processes are trying to access the same resource simultaneously.
  Cause:
  
  Concurrency Issues: The error usually occurs when a component group is being accessed or modified by another user or process. This can happen in scenarios where multiple transactions are trying to work on the same data simultaneously.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If one transaction has locked a resource, other transactions trying to access it may encounter this error.
  Configuration Issues: There may be configuration settings that are not properly set up, leading to conflicts in processing.
  
  Solution:
  
  Wait and Retry: If the error is due to a temporary lock, waiting for a few moments and then retrying the operation may resolve the issue.
  Check Locks: Use transaction codes like SM12 to check for existing locks on the relevant tables or objects. If you find a lock that is no longer needed, you can release it (with caution).
  Review Background Jobs: If the error is occurring in a background job, check the job logs for any issues. You may need to adjust the job scheduling or the logic within the job.
  Transaction Isolation: If possible, try to isolate the transactions that are causing the conflict. This may involve changing the way transactions are processed or modifying the application logic.
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or patches that may address this specific error. There may be updates or fixes available that can resolve the issue.
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. Provide them with detailed information about the error, including transaction codes, user IDs, and any relevant logs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM21 (System Log), SM37 (Job Monitoring), and SM12 (Lock Entries) to help diagnose and troubleshoot the issue.
  SAP Documentation: Review SAP documentation related to concurrency control and locking mechanisms to better understand how SAP handles these scenarios.
  User Training: Ensure that users are trained on best practices for using the system to minimize the chances of encountering such errors.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.