How To Fix CRM_LEASING_CANCEL053 - Cannot cancel migrated document &1

CRM_LEASING_CANCEL053 - Overview

• Message type: E = Error

• Message class: CRM_LEASING_CANCEL - Leasing: Cancellation

• Message number: 053

• Message text: Cannot cancel migrated document &1

What causes this issue?

Item &V1& was migrated and therefore cannot be cancelled in the standard
system.

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

The check on migration occurs in the default implementation of method
END_CHK_CANCEL in the Business Add-In <ZK>Final Check of Selected Items
to be Cancelled</>. If you want to switch off this standard check, you
can deactivate the default implementation and create your own
implementation.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_LEASING_CANCEL053 - Cannot cancel migrated document &1 ?

  The SAP error message CRM_LEASING_CANCEL053 indicates that there is an issue with canceling a migrated leasing document in the SAP Customer Relationship Management (CRM) system. This error typically arises when trying to cancel a document that has been migrated from an older system or version and is not in a state that allows for cancellation.
  
  Cause:
  
  Document Status: The document you are trying to cancel may not be in a cancellable status. For example, it might be already completed or in a state that does not allow for further modifications.
  Migration Issues: If the document was migrated from another system, there may be inconsistencies or missing data that prevent the cancellation process.
  Business Rules: There may be specific business rules or configurations in your SAP system that restrict the cancellation of certain types of documents.
  Dependencies: The document may have dependencies or linked transactions that need to be addressed before cancellation can occur.
  
  
  Solution:
  
  Check Document Status: