How To Fix DBMAN157 - &1 InfoProvider(s) excluded because of pruning (filter = &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: DBMAN - Data Manager Message Class

• Message number: 157

• Message text: &1 InfoProvider(s) excluded because of pruning (filter = &2)

What causes this issue?

One or more PartProviders were pruned in the query. Possible reasons:
Definition of a constant on an InfoObject
Restrictions on metadata (see report RSPP_PART_MAINTAIN)
MultiProvider hint (see table RRKMULTIPROVHINT)
Near-Line Storage / cold store: Possible reasons for pruning:
The global query filter contains a restriction on the primary
characteristic of the Data Archiving Process.
The intersection of the global filter and the archived data is
empty.Extended pruning on time characteristics is used (See Note
2129546)

How to fix this error?

To find out which InfoProviders have been pruned from the query and why
they were pruned, execute the query using transaction RSRT in debug
mode. Set the 'MultiProvider Explain' flag here.
If you want to view the result without pruning, execute the query using
transaction RSRT in debug mode. Set the ?No PartProvider Pruning? flag
here.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DBMAN157 - &1 InfoProvider(s) excluded because of pruning (filter = &2) ?

  The SAP error message DBMAN157 indicates that certain InfoProviders have been excluded from a query due to a process called "pruning." This typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when the system determines that certain InfoProviders do not contain relevant data based on the filters applied to the query.
  Cause:
  
  Filter Conditions: The error message suggests that the filters applied to the query do not match any data in the excluded InfoProviders. This can happen if the filter criteria are too restrictive or if the data in the InfoProviders does not meet the specified conditions.
  Data Model Changes: If there have been recent changes to the data model, such as changes in the InfoProviders or the underlying data, it may lead to situations where certain InfoProviders no longer contain relevant data for the current query.
  Inconsistent Data: There may be inconsistencies in the data that lead to certain InfoProviders being excluded from the result set.
  
  Solution:
  
  Review Filters: Check the filters applied to the query. Ensure that they are set correctly and are not overly restrictive. Adjust the filters if necessary to include the desired InfoProviders.
  Data Validation: Validate the data in the InfoProviders to ensure that they contain the expected data. If the data is missing or incorrect, you may need to refresh or load the data again.
  Check InfoProvider Configuration: Review the configuration of the InfoProviders to ensure they are set up correctly and are active. Make sure that they are included in the query definition.
  Query Design: If you are using a composite provider or a multi-provider, ensure that the underlying InfoProviders are correctly linked and that the data model is designed to support the query requirements.
  Rebuild Indexes: In some cases, rebuilding indexes or refreshing aggregates may help resolve issues related to data retrieval.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Query Monitor: Use the Query Monitor (transaction RSRT) to analyze the query execution and see which InfoProviders are being accessed and why some are excluded.
  Performance Analysis: If pruning is affecting performance, consider optimizing the query or the underlying data model to improve efficiency.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation and support.