How To Fix CRM_DPP079 - Start of Retention date could not be det. due to inconsistent field name

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_DPP - CRM Data Privacy

• Message number: 079

• Message text: Start of Retention date could not be det. due to inconsistent field name

What causes this issue?

The Start of Retention date (also referred to as end of business date)
cannot be determined. Object name &V1& leads to working structure with
name &V2& but this working structure does not have a component called
&V3&. However, the field name &V3& is used in the customizing.

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?

Either the object name &V1& in the customizing needs to be corrected or
the working structure and/or working table for object name &V1& not
suitable or the field name &V3& needs to be changed.

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 CRM_DPP079 - Start of Retention date could not be det. due to inconsistent field name ?

  The SAP error message CRM_DPP079 indicates that the system is unable to determine the start of the retention date due to an inconsistency in the field name. This error typically arises in the context of SAP Customer Relationship Management (CRM) when dealing with data retention policies or related processes.
  
  Cause:
  
  
  Inconsistent Field Names: The error suggests that there is a mismatch or inconsistency in the field names that are expected by the system. This could be due to:
  
  Customizations or modifications in the CRM system that have not been properly aligned with standard field definitions.
  Missing or incorrectly configured fields in the relevant data model.
  Issues with data migration or integration processes that have led to discrepancies in field names.
  
  
  
  Data Integrity Issues: There may be issues with the underlying data that prevent the system from correctly interpreting the retention date.
  
  
  Configuration Errors: Incorrect configuration settings in the CRM system related to data retention policies or related