How To Fix CVP_DP_ILM155 - Bus. activities for contact &1 with CoCd &2 not complete in appl. &3

CVP_DP_ILM155 - Overview

• Message type: E = Error

• Message class: CVP_DP_ILM - CVP_DP_ILM

• Message number: 155

• Message text: Bus. activities for contact &1 with CoCd &2 not complete in appl. &3

What causes this issue?

The end of purpose (EoP) check determined that master data of contact
person &V1& with company code &V2& is still required for
business activities in application &V3&. Therefore, the data cannot
be blocked.

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?

Applications that report ongoing business for a contact person must send
a next EoP check date that is later than the current date. If no Next
Check Date value is returned, the central blocking report defaults the
next check date based on settings made in Customizing for
Cross-Application Components > Data Protection.
The next EoP check date calculated for contact person &V1& with
company code &V2& is &V4&.

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 CVP_DP_ILM155 - Bus. activities for contact &1 with CoCd &2 not complete in appl. &3 ?

  The SAP error message CVP_DP_ILM155 indicates that there are business activities related to a contact (identified by &1) in a specific company code (CoCd &2) that have not been completed in the application (identified by &3). This error typically arises in the context of SAP Customer Relationship Management (CRM) or SAP Data Protection and Privacy (DPP) scenarios, particularly when dealing with data privacy and compliance processes.
  
  Cause:
  
  Incomplete Business Activities: The primary cause of this error is that there are pending or incomplete business activities associated with the specified contact. This could include tasks such as data processing, consent management, or other compliance-related activities that have not been finalized.
  Data Consistency Issues: There may be inconsistencies in the data related to the contact or the company code, which can prevent the application from processing the request.
  
  Configuration Issues: Incorrect configuration settings in the application or the underlying data model may lead to this error.
  
  
  Solution:
  
  Complete