Do you have any question about this error?
Message type: E = Error
Message class: SADL_GEN_DRFT_MSG - Message for Draft generation
Message number: 064
Message text: UUID-based models are not yet supported by runtime.
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
SADL_GEN_DRFT_MSG064
- UUID-based models are not yet supported by runtime. ?The error message "SADL_GEN_DRFT_MSG064 UUID-based models are not yet supported by runtime" in SAP typically indicates that you are trying to use a UUID-based model in a context where it is not supported. This can occur in scenarios involving the SAP ABAP programming model, particularly when working with the SAP Data Layer (SADL) or when using certain features of the SAP Cloud Application Programming (CAP) model.
Cause:
- UUID-based Models: The error suggests that the model you are trying to use is based on UUIDs (Universally Unique Identifiers), which are not supported in the current runtime environment you are working with.
- Incompatibility: The specific version of the SAP system or the runtime environment may not support UUID-based models, or the feature may not be fully implemented yet.
- Configuration Issues: There may be configuration issues in your project or application that lead to the use of unsupported features.
Solution:
- Check Model Type: Review the model you are using and ensure that it is not based on UUIDs. If possible, switch to a supported key type (like integer or string) that is compatible with the runtime.
- Update SAP System: Ensure that your SAP system is updated to the latest version, as newer versions may include support for UUID-based models.
- Consult Documentation: Refer to the official SAP documentation for the specific version you are using to check for any limitations or requirements regarding UUID-based models.
- Use Alternative Approaches: If UUIDs are necessary for your application, consider using alternative approaches or workarounds that do not rely on UUIDs in the runtime context.
- Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if you believe this is a bug or a missing feature in your current version.
Related Information:
By following these steps, you should be able to address the error and find a suitable workaround or solution for your specific use case.
Get instant SAP help. Start your 7-day free trial now.
SADL_GEN_DRFT_MSG063
CDS-View &1 must not contain draft specific fields
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SADL_GEN_DRFT_MSG062
Composition of CDS-View &1 contains duplicate views
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SADL_GEN_DRFT_MSG065
Assoc. #TO_COMPOSITION_PARENT in CDS-View &1 is defined multiple times
What causes this issue? The association #TO_COMPOSITION_PARENT is defined multiple times, either in the local view or via inheritance from an underly...
SADL_GEN_DRFT_MSG066
Association #TO_COMPOSITION_ROOT in CDS-View &1 is defined multiple times
What causes this issue? The association #TO_COMPOSITION_ROOT is defined multiple times, either in the local view or via inheritance from an underlyin...
Click on this link to search all SAP messages.