Do you have any question about this error?
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
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.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
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.
Error message extract from SAP system. Copyright SAP SE.
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 modules.
Solution:
Check Field Definitions: Review the field definitions in the relevant data model to ensure that all required fields are present and correctly named. This may involve:
- Accessing the data model in the SAP system and verifying the field names.
- Ensuring that any custom fields are correctly defined and mapped.
Data Consistency Check: Perform a data consistency check to identify any discrepancies in the data that may be causing the issue. This can involve:
- Running standard SAP reports or transaction codes that check for data integrity.
- Reviewing logs for any data migration or integration processes that may have failed.
Configuration Review: Review the configuration settings related to data retention policies in the CRM system. Ensure that all settings are correctly configured and aligned with the business requirements.
Consult Documentation: Refer to SAP documentation or notes related to the CRM_DPP079 error for any specific guidance or patches that may address the issue.
SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version of your SAP system and any known issues.
Related Information:
By following these steps, you should be able to identify and resolve the underlying cause of the CRM_DPP079 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
CRM_DPP078
Business Function ILM not active
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_DPP077
Start of Retention date could not be determined as customizing is missing
What causes this issue? The Start of Retention date (SoRT, also referred to as end of business (EoB)) could not be determined for the item of Busines...
CRM_DPP080
Data belonging to this document is blocked
What causes this issue? You want to display archived data whereas your authorizations to access this data are not sufficient.System Response The sys...
CRM_DPP081
Search results do not include blocked data; see long text
What causes this issue? You searched business transactions within archives. Some of the found data is blocked by an authorization checks for accessin...
Click on this link to search all SAP messages.