How To Fix /BOBF/DAC021 - Union DAC doesn't support requests regarding draft AND active data

/BOBF/DAC021 - Overview

• Message type: E = Error

• Message class: /BOBF/DAC -

• Message number: 021

• Message text: Union DAC doesn't support requests regarding draft AND active data

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 /BOBF/DAC021 - Union DAC doesn't support requests regarding draft AND active data ?

  The SAP error message /BOBF/DAC021 Union DAC doesn't support requests regarding draft AND active data typically occurs in the context of the Business Object Processing Framework (BOPF) when there is an attempt to access both draft and active data simultaneously in a Union Data Access Class (DAC). This situation arises because Union DACs are designed to handle either draft or active data, but not both at the same time.
  
  Cause:
  
  Union DAC Limitation: The Union DAC is not designed to handle requests that involve both draft and active data. This is a limitation of the framework.
  Request Configuration: The request being made may inadvertently include both draft and active data, which is not supported.
  Data Model Design: The underlying data model may be incorrectly configured to allow for such requests.
  
  
  Solution:
  
  Separate Requests: Modify the logic in your application to ensure that requests are made separately for draft and active data. You should either query for