How To Fix DBMAN878 - Restriction to &1 not permitted for InfoProvider &2 (type &3)

DBMAN878 - Overview

• Message type: E = Error

• Message class: DBMAN - Data Manager Message Class

• Message number: 878

• Message text: Restriction to &1 not permitted for InfoProvider &2 (type &3)

What causes this issue?

A restriction on a characteristic is not allowed for this InfoProvider.
Generally, this is a restriction on the request ID for a MultiProvider
that has more than one InfoCube as a part provider.
In this case, assignment of request IDs to the individual InfoProviders
is longer possible, thus this restriction is not permitted.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DBMAN878 - Restriction to &1 not permitted for InfoProvider &2 (type &3) ?

  The SAP error message DBMAN878 typically indicates that there is a restriction being applied to an InfoProvider that is not allowed. This can occur in various contexts, such as when working with SAP BW (Business Warehouse) or SAP HANA, where certain restrictions or queries are not permitted on specific types of InfoProviders.
  
  Cause:
  The error message DBMAN878 can arise due to several reasons:
  
  Invalid Restrictions: The restriction being applied is not valid for the specified InfoProvider type. For example, you might be trying to apply a filter or restriction that is not supported by the InfoProvider.
  InfoProvider Type: The type of InfoProvider (e.g., InfoCube, DataStore Object, etc.) may have limitations on the types of queries or restrictions that can be applied.
  Authorization Issues: There may be authorization issues preventing the application of certain restrictions.
  Data Model Issues: The underlying data model may not support the requested operation due to design constraints.
  
  
  Solution:
  To resolve the DBMAN878 error, consider