How To Fix SADL_CONSUMP_SERVICE104 - Draft enabled entity &1 does not contain draft table annotation

SAP Error Message - Details

• Message type: E = Error

• Message class: SADL_CONSUMP_SERVICE - SADL Consumption Service

• Message number: 104

• Message text: Draft enabled entity &1 does not contain draft table annotation

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 SADL_CONSUMP_SERVICE104 - Draft enabled entity &1 does not contain draft table annotation ?

  The SAP error message SADL_CONSUMP_SERVICE104 indicates that there is an issue with a draft-enabled entity in your SAP application. Specifically, the error states that the draft-enabled entity does not contain the necessary draft table annotation. This is typically encountered in the context of SAP Fiori applications or OData services that utilize the SAP Draft Framework.
  Cause:
  The error occurs when:
  
  You are trying to use a draft-enabled entity in your application, but the entity definition does not include the required annotations for draft handling.
  The draft table annotation is missing from the metadata of the entity, which is necessary for the SAP Draft Framework to manage draft data correctly.
  
  Solution:
  To resolve this error, you need to ensure that the draft-enabled entity is properly annotated in your OData service. Here are the steps to do this:
  
  
  Check the Entity Definition:
  
  Open the definition of the entity in your CDS (Core Data Services) view or the relevant data model.
  Ensure that the entity is marked as draft-enabled.
  
  
  
  Add Draft Table Annotations:
  
  You need to add the necessary annotations to the entity. The draft table annotation typically looks like this:
  @ObjectModel: {
    draftEnabled: true,
    draftTable: 'Your_Draft_Table_Name'
  }
  
  Make sure that the draft table is correctly defined and that the entity is linked to it.
  
  
  
  Activate the Changes:
  
  After making the necessary changes to the annotations, activate the CDS view or the data model.
  If you are using a transport system, ensure that the changes are transported to the relevant system.
  
  
  
  Regenerate the OData Service:
  
  If you are using an OData service, you may need to regenerate the service to reflect the changes made in the CDS view.
  
  
  
  Test the Application:
  
  After making the changes and regenerating the service, test the application again to see if the error persists.
  
  
  
  Related Information:
  
  SAP Draft Framework: This framework allows users to create drafts of business objects, enabling them to work on changes without immediately committing them to the database.
  Annotations: Annotations in SAP are metadata that provide additional information about the data model, such as UI behavior, draft handling, and more.
  CDS Views: Core Data Services (CDS) views are a way to define data models in SAP that can be consumed by various applications, including Fiori apps and OData services.
  
  If you continue to experience issues after following these steps, consider checking the SAP Community or SAP Notes for any specific guidance related to your version of SAP or the specific application you are working with.