Message type: E = Error
Message class:  /BOBF/FRW_CONTRACT -  
Message number: 010
Message text: Using "Draft Scope" requires BO migration to "Smart Validations"
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/FRW_CONTRACT010 indicates that there is an issue related to the use of "Draft Scope" in conjunction with the Business Object Framework (BOBF) in SAP. Specifically, this error suggests that the system requires a migration to "Smart Validations" in order to use the Draft Scope feature effectively.
Cause: Outdated Configuration: The system may be using an older version of the Business Object Framework that does not support the Draft Scope feature without Smart Validations. Missing Migration: The necessary migration to Smart Validations has not been performed, which is required for the Draft Scope functionality to work properly. Incompatibility: There may be an incompatibility between the current configuration of the Business Object and the Draft Scope feature.
Solution: Perform Migration: You need to migrate your Business Object to support Smart Validations. This typically involves: Accessing the relevant transaction codes in SAP (like /BOBF/CONF for configuration). Following the migration steps provided in the SAP documentation or notes
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
/BOBF/FRW_CONTRACT009 Inconsistent state in BOPF runtime after previous error
What causes this issue?  A program called a BOPF runtime API method when the runtime was already in an inconsistent state.  The inconsistency was caus...
/BOBF/FRW_CONTRACT008 Calling action EDIT_DEPENDENT on an active instance of BO "&" twice
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/BOBF/FRW_CONTRACT011 Class &1 is reserved for use by generated actions
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/BOBF/FRW_CONTRACT012 Method parameter violates condition "&1&2&3&4"
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.