Do you have any question about this error?
Message type: E = Error
Message class: CRD_CUST - Credentialing: Messages for Editing Customizing
Message number: 321
Message text: Description &1: Referenced description &2 is unknown
Credential description &v1& should reference description &v2&. However
description &v2& is not defined for the period from &v3& to &v4& .
The referenced description for credential description &v1& will <ZH>not
</>be changed.
Check the following:
Description &v2& is defined.
Description &v2& is valid for the period from &v3& to &v4&.
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.
CRD_CUST321
- Description &1: Referenced description &2 is unknown ?The SAP error message CRD_CUST321 typically indicates that there is a problem with a referenced description in the system. This error often arises in the context of customizing or configuration settings, particularly when dealing with customer-specific data or descriptions that are expected to be present but are not found in the system.
Cause:
- Missing Data: The referenced description (&2) is not defined in the system. This could be due to data not being created or deleted inadvertently.
- Incorrect Configuration: There may be a misconfiguration in the customizing settings where the system is looking for a description that does not exist.
- Transport Issues: If the data was transported from one system to another (e.g., from development to production), it may not have been included in the transport request.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the referenced description.
Solution:
- Check Data Existence: Verify if the referenced description (&2) exists in the relevant customizing tables. You can do this by using transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to look up the relevant tables.
- Create Missing Descriptions: If the description is indeed missing, you will need to create it in the appropriate customizing area. This may involve going to the relevant transaction (e.g., SPRO for customizing) and adding the necessary entries.
- Review Transport Requests: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and successfully imported.
- Check Authorizations: Ensure that the user has the necessary authorizations to access the data. This can be checked with the help of your security team or by using transaction SU53 to analyze authorization issues.
- Consult Documentation: Review any relevant SAP documentation or notes that may provide additional context or solutions for this specific error message.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
CRD_CUST320
Customizing error: Requirement cannot be a combined requirement
What causes this issue? The <DS:GLOS.44B0359646864888E10000000A1553FE>combined requirement</> &V1&contains an item for a <DS:G...
CRD_CUST314
Description &1/&2 is not defined for required period
What causes this issue? Either there is no credential description &v1&/&v2& or the mininum validity of the description does not cover...
CRD_CUST329
Error while calling search help &1
What causes this issue? While calling search help &v1&, the system detected an error that prevents the search help from being executed furthe...
CRD_CUST330
Generation of data structures for credential type &1 failed
What causes this issue? A storage area of data type &v2&is to be reserved for a description of <DS:GLOS.44B20C2B4AE64888E10000000A1553FE&g...
Click on this link to search all SAP messages.