How To Fix RSMPC162 - DM check of request &1 in data source &1: Request filtered out

SAP Error Message - Details

• Message type: E = Error

• Message class: RSMPC - Messages for Process Chains of Generic Processes

• Message number: 162

• Message text: DM check of request &1 in data source &1: Request filtered out

What causes this issue?

The data mart check of data source &V2& filtered request&V1& . A
request is filtered out, for example, if a repeat for this request is
still possible or if it was not yet updated.
DTP requests can be terminated with this error message if the request is
still green, but is to be deleted.

System Response

You are not allowed to delete this request because at least one data
mart or DTP has updated this request.
If you want to compress this request, you can only do this after all
data marts/DTPs have retrieved the request.

How to fix this error?

Only delete these requests if they have not been retrieved by data
mart/DTP using a delta update.
You can only compress requests that have been updated in the connected
targets.
In the administration of the source &V1& , this is indicated by a
selected checkbox.
If it is a green DTP request that is to be deleted, first set the status
of this request to red and then start the deletion again.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSMPC162 - DM check of request &1 in data source &1: Request filtered out ?

  The SAP error message RSMPC162 indicates that a data request has been filtered out during the data extraction process from a data source. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when data is being loaded from a source system into the data warehouse.
  Cause:
  The error message "Request filtered out" can occur due to several reasons:
  
  
  Data Selection Criteria: The data request may not meet the selection criteria defined in the data source or transformation. This could be due to filters applied in the data extraction process that exclude the data being requested.
  
  
  Data Source Configuration: The data source may be incorrectly configured, leading to the filtering of requests that should otherwise be processed.
  
  
  Data Quality Issues: If the data in the source system does not meet the expected quality or format, it may be filtered out during the extraction process.
  
  
  Request Status: The request may have been previously processed and marked as completed or failed, leading to it being filtered out in subsequent processing.
  
  
  Delta Mechanism: If you are using delta loads, the delta mechanism may not have captured any new data since the last load, resulting in no data being available for the request.
  
  
  Solution:
  To resolve the RSMPC162 error, you can take the following steps:
  
  
  Check Selection Criteria: Review the selection criteria in the data source and transformation to ensure that they are set correctly and that they allow for the data you expect to be loaded.
  
  
  Review Data Source Configuration: Ensure that the data source is properly configured and that there are no issues with the connection to the source system.
  
  
  Examine Data Quality: Check the data in the source system for any quality issues that may prevent it from being extracted. This includes checking for missing values, incorrect formats, or other anomalies.
  
  
  Monitor Request Status: Look at the status of the request in the data loading monitor. If it has been processed previously, you may need to reset or reprocess it.
  
  
  Check Delta Load Settings: If you are using delta loads, verify that the delta mechanism is functioning correctly and that there are indeed new records to be loaded.
  
  
  Review Logs: Check the logs for any additional error messages or warnings that may provide more context about why the request was filtered out.
  
  
  Test with Different Data: If possible, try running the extraction with different data or a different time frame to see if the issue persists.
  
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to monitor and manage data loads.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific data source or extraction process you are using.
  Documentation: Refer to SAP documentation for best practices on data extraction and transformation processes in BW/BI.
  
  By following these steps, you should be able to identify the cause of the RSMPC162 error and implement a solution to resolve it.