How To Fix RSO674 - Object &1 &2 on exception list. Dependents not checked

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO - BW Repository

• Message number: 674

• Message text: Object &1 &2 on exception list. Dependents 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 RSO674 - Object &1 &2 on exception list. Dependents not checked ?

  The SAP error message RSO674 typically indicates that there is an issue with an object (like a query, InfoProvider, or other BI objects) that is on the exception list, which prevents the system from checking its dependents. This can occur in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with queries, reports, or data models.
  Cause:
  The error message RSO674 can be caused by several factors, including:
  
  Object on Exception List: The object you are trying to work with is on the exception list, which means it has been flagged for some reason (e.g., it may be inactive, deleted, or not properly configured).
  Dependency Issues: The system cannot check the dependents of the object because it is in a state that prevents this check.
  Transport Issues: If the object was recently transported from one system to another, it may not have been properly activated or may have dependencies that are not met in the target system.
  Authorization Issues: Lack of proper authorizations to access or modify the object can also lead to this error.
  
  Solution:
  To resolve the RSO674 error, you can take the following steps:
  
  
  Check the Exception List: 
  
  Go to the transaction code RSO1 or RSO2 to view the exception list and identify the object causing the issue.
  Determine why the object is on the exception list and take appropriate action (e.g., reactivating the object, fixing configuration issues).
  
  
  
  Reactivate the Object: 
  
  If the object is inactive, reactivate it using the appropriate transaction (e.g., RSRT for queries, RSA1 for InfoProviders).
  
  
  
  Check Dependencies: 
  
  Ensure that all dependent objects are active and properly configured. You can use the RSR transaction codes to check the status of queries and InfoProviders.
  
  
  
  Transport Issues: 
  
  If the object was recently transported, ensure that all related objects were also transported and activated in the target system.
  
  
  
  Authorization Check: 
  
  Verify that you have the necessary authorizations to access and modify the object. Consult with your SAP security team if needed.
  
  
  
  Consult SAP Notes: 
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSO1 (Exception List), and RSRT (Query Monitor).
  SAP Documentation: Review SAP documentation and guides related to BW/BI object management and troubleshooting.
  Community Forums: Engage with SAP community forums or user groups for additional insights and shared experiences regarding this error.
  
  By following these steps, you should be able to identify the root cause of the RSO674 error and implement a solution to resolve it.