How To Fix RSO675 - Request &1 on exception list. Not checked

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO - BW Repository

• Message number: 675

• Message text: Request &1 on exception list. Not checked

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 RSO675 - Request &1 on exception list. Not checked ?

  The SAP error message RSO675 typically indicates that a request (data load) has been flagged as being on an exception list, which means that it has not been checked or validated for some reason. This can occur in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with data loads and requests.
  Cause:
  
  Data Quality Issues: The request may have encountered data quality issues during the data load process, leading to it being flagged for review.
  Load Failures: If there were errors during the data extraction or transformation process, the request may not have been processed correctly.
  Manual Intervention: Sometimes, users may manually place requests on an exception list for further investigation or validation.
  Configuration Issues: There may be configuration settings in the data source or transformation that are causing the request to be flagged.
  
  Solution:
  
  Check the Request Status: Go to the Data Warehousing Workbench (transaction RSA1) and check the status of the request. Look for any error messages or warnings associated with it.
  Review the Exception List: Access the exception list to see why the request was flagged. This can provide insights into the specific issues that need to be addressed.
  Validate Data: Ensure that the data being loaded meets the required quality standards. This may involve checking for duplicates, missing values, or incorrect formats.
  Reprocess the Request: If the issues have been resolved, you can attempt to reprocess the request. This can often be done by selecting the request and choosing the option to "Reprocess" or "Load Again."
  Consult Logs: Check the logs for the data load process to identify any specific errors that occurred. This can help in diagnosing the root cause of the issue.
  Configuration Review: If the problem persists, review the configuration settings for the data source, transformation, and data targets to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSMO (Monitor Data Loads), and RSPC (Process Chain Maintenance) for monitoring and managing data loads.
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message RSO675. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Review SAP documentation on data loading processes, exception handling, and data quality management to better understand how to prevent and resolve such issues in the future.
  
  By following these steps, you should be able to identify the cause of the RSO675 error and take appropriate action to resolve it.