Message type: E = Error
Message class: /BOBF/CONF_CDS -
Message number: 086
Message text: [BO check] Migration to v1.0 not supported. Add 'draftEnabled' (view &1)
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.
The SAP error message
/BOBF/CONF_CDS086 [BO check] Migration to v1.0 not supported. Add 'draftEnabled' (view &1)
typically occurs in the context of Business Object Framework (BOF) and Core Data Services (CDS) views in SAP. This error indicates that the migration to version 1.0 of a Business Object is not supported because the required configuration for draft handling is missing.Cause:
- Draft Handling Not Enabled: The error suggests that the CDS view in question does not have draft handling enabled. Draft handling is essential for certain applications, especially those that require saving intermediate states of data.
- Version Compatibility: The system is trying to migrate to a version that requires draft support, but the current configuration does not meet this requirement.
- Configuration Issues: There may be a misconfiguration in the Business Object or the associated CDS view.
Solution:
To resolve this error, you need to enable draft handling for the specified CDS view. Here are the steps to do this:
Open the CDS View: Use the ABAP Development Tools (ADT) in Eclipse or the appropriate transaction in SAP to access the CDS view that is causing the error.
Modify the CDS View: Add the
@UI.draftEnabled: true
annotation to the CDS view definition. This annotation indicates that draft handling is enabled for the view.Example:
@AbapCatalog.sqlViewName: 'Z_MY_CDS_VIEW' @AbapCatalog.compiler.compareFilter: 'Z_MY_CDS_VIEW' @UI.draftEnabled: true define view Z_MY_CDS_VIEW as select from my_table { key field1, field2, ... }
Activate the CDS View: After making the changes, activate the CDS view to apply the new configuration.
Check Business Object Configuration: Ensure that the Business Object associated with the CDS view is correctly configured to support drafts.
Test the Changes: After making the changes, test the application or process that was previously generating the error to confirm that the issue has been resolved.
Related Information:
If you continue to experience issues after following these steps, consider checking SAP Notes or reaching out to SAP support for further assistance.
/BOBF/CONF_CDS085 [BO sync] Neither 'draft pers.' nor 'active pers.' not supported (v. &1)
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOBF/CONF_CDS084 [BO check] Switching scenario (&2~>&3) not supported (view &1)
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOBF/CONF_CDS087 [BO check] Child annotates active persistence, root doesn't (view &1)
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOBF/CONF_CDS088 [BO check] Child doesn't annotate active persistence, Root does (v. &1)
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.