How To Fix /SMB/RUNTIME_CORE086 - New Data Model is on. Activation must not be used, anymore.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/RUNTIME_CORE -

• Message number: 086

• Message text: New Data Model is on. Activation must not be used, anymore.

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SMB/RUNTIME_CORE086 - New Data Model is on. Activation must not be used, anymore. ?

  The SAP error message /SMB/RUNTIME_CORE086 New Data Model is on. Activation must not be used, anymore. typically indicates that you are trying to use an activation process that is no longer supported due to the transition to a new data model in your SAP system. This is common in systems that have been upgraded or migrated to newer versions of SAP, particularly in the context of SAP S/4HANA or other modern SAP solutions.
  Cause:
  
  New Data Model Activation: The error arises because the system is configured to use the new data model, which does not support the traditional activation methods that were used in older versions of SAP.
  Legacy Code: If you are trying to execute legacy code or transactions that were designed for the old data model, they may not be compatible with the new model.
  Configuration Issues: There may be configuration settings that are still pointing to the old activation methods.
  
  Solution:
  
  Review Documentation: Check the SAP documentation for the specific version you are using to understand the changes in the data model and the recommended practices for activation.
  Update Custom Code: If you have custom code or Z-programs that rely on the old activation methods, you will need to update them to be compatible with the new data model.
  Use New Methods: Familiarize yourself with the new methods and processes for data handling and activation in the new data model. This may involve using new transaction codes or APIs that are designed for the new architecture.
  Consult SAP Notes: Look for relevant SAP Notes that address this issue. SAP frequently releases notes that provide guidance on handling specific errors and adapting to new features.
  Testing: After making changes, thoroughly test the affected processes to ensure that they work correctly with the new data model.
  
  Related Information:
  
  SAP S/4HANA: If you are using SAP S/4HANA, be aware that it has a fundamentally different data model compared to previous versions of SAP ERP. Understanding the implications of this change is crucial.
  Migration Guides: SAP provides migration guides and best practices for transitioning from older systems to newer ones. These resources can be invaluable in understanding how to adapt your processes.
  SAP Community: Engage with the SAP Community forums where you can find discussions and solutions from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.