Do you have any question about this error?
Message type: E = Error
Message class: CRM_DPP - CRM Data Privacy
Message number: 066
Message text: Start of Retention date could not be determined as customizing is missing
The Start of Retention date (SoRT, also referred to as end of business
(EoB)) could not be determined for the header of Business Transaction
&V1& as the customizing
<DS:TRAN.S_AG3_75000475>Define Start of Retention Date</> does not
contain an entry for transaction type &V2& nor transaction category &V3&
nor a generic entry for transaction category BUS20001.
The calculation of end of business data is not possible. Mandatory
customizing is missing.
Maintain customizing
<DS:TRAN.S_AG3_75000475>Define Start of Retention Date</> so that there
is an entry for transaction type &V2& or transaction category &V3& or a
combination of both. In order to use the last change date of a Business
Transaction as end of business date (or rather Start of Retention)
maintain the key fields as mentioned an the following values:
Object Name: ORDERADM_H
Field Name: CHANGED_AT
Technical Key Name: <empty>
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
CRM_DPP066
- Start of Retention date could not be determined as customizing is missing ?The SAP error message CRM_DPP066 indicates that the system is unable to determine the start of the retention date due to missing customizing settings. This error typically occurs in the context of SAP Customer Relationship Management (CRM) when dealing with document retention management or similar functionalities.
Cause:
The primary cause of this error is that the necessary customizing settings for retention periods or retention rules have not been defined in the system. This can happen if:
- The retention periods have not been configured in the system.
- The relevant customizing settings for the document type or business process are missing.
- There may be inconsistencies in the configuration that prevent the system from determining the retention date.
Solution:
To resolve the error, you can follow these steps:
Check Customizing Settings:
- Go to the SAP Customizing Implementation Guide (IMG) by using transaction code
SPRO
.- Navigate to the relevant section for Document Retention Management or the specific area related to your business process.
- Ensure that the retention periods and rules are properly defined for the document types you are working with.
Define Retention Periods:
- If retention periods are not defined, create them by specifying the necessary parameters such as duration, start date, and any other relevant criteria.
Assign Retention Periods to Document Types:
- Make sure that the retention periods are assigned to the appropriate document types or business objects that are generating the error.
Check for Missing Entries:
- Review the configuration for any missing entries or inconsistencies that could lead to the inability to determine the retention date.
Test the Configuration:
- After making the necessary changes, test the functionality to ensure that the error no longer occurs and that the retention date is correctly determined.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on configuring retention management in your version of SAP CRM.
Related Information:
SPRO
for customizing, SCC4
for client settings, or SCDO
for document object management.If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation or to reach out to SAP support for assistance.
Get instant SAP help. Start your 7-day free trial now.
CRM_DPP065
Purpose not completed for Bus.Part. &1 and end of business &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_DPP064
Purpose completed for Bus.Part. &1 and end of business &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_DPP067
Start of Retention date det. with obj.name &1, field name &2, tech.key &3
What causes this issue? The Start of Retention date (also referred to as end of business date) will be determined using object name &V1& fiel...
CRM_DPP068
Field name &1 for object name &2 is technically invalid
What causes this issue? The field name &V1& for object name &V2& is technically not valid. I.e. it contains at least one invalid char...
Click on this link to search all SAP messages.