How To Fix RSRD672 - Cannot read &2 (type &1, system alias &3)

SAP Error Message - Details

• Message type: E = Error

• Message class: RSRD - Report Dissemination

• Message number: 672

• Message text: Cannot read &2 (type &1, system alias &3)

What causes this issue?

Cannot read basis object &V2& (object type &V1&) for the broadcast
setting. It is in the system with system alias &V3&. This can be due to
many reasons:
The object does not exist.
You do not have authorization to display the object.
Cannot access the system with system alias &V3&.
Error occured reading the object in system &V3&.
Further error messages may provide information on the causes.

System Response

Cannot load or execute broadcast settings based on this object.

How to fix this error?

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

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 RSRD672 - Cannot read &2 (type &1, system alias &3) ?

  The SAP error message RSRD672 indicates that there is an issue with reading a specific object in the SAP system, typically related to a query or report. The message format is as follows:
  
  &1: Type of the object (e.g., InfoProvider, Query, etc.)
  &2: Name of the object that cannot be read
  &3: System alias being used
  
  Causes
  
  Object Does Not Exist: The specified object (e.g., InfoProvider or Query) may not exist in the system or may have been deleted.
  Authorization Issues: The user may not have the necessary authorizations to access the specified object.
  Incorrect System Alias: The system alias used may not be correctly configured or may point to a non-existent or incorrect system.
  Transport Issues: If the object was recently transported from another system, it may not have been properly imported or activated.
  Data Source Issues: If the object is a data source, there may be issues with the underlying data source configuration.
  
  Solutions
  
  Verify Object Existence: Check if the object (e.g., InfoProvider or Query) exists in the system. You can do this by navigating to the relevant transaction (e.g., RSA1 for InfoProviders).
  Check Authorizations: Ensure that the user has the necessary authorizations to access the object. You may need to consult with your security team to verify and adjust authorizations.
  Review System Alias Configuration: Check the configuration of the system alias in transaction RSC1. Ensure that it points to the correct system and that the connection is active.
  Transport Validation: If the object was recently transported, verify that the transport was successful and that the object is active in the target system.
  Data Source Configuration: If the object is a data source, check the configuration of the data source to ensure it is set up correctly and that the underlying data is accessible.
  
  Related Information
  
  Transaction Codes: 
  
  RSA1: Data Warehousing Workbench
  RSC1: Maintain System Aliases
  RSRV: Check and Repair Queries
  
  
  Authorization Objects: Check for relevant authorization objects that may restrict access to the InfoProvider or Query.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis or BW team for further investigation.