How To Fix RSO874 - Content status entry for object &1 &2 (version &3) deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO - BW Repository

• Message number: 874

• Message text: Content status entry for object &1 &2 (version &3) deleted

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 RSO874 - Content status entry for object &1 &2 (version &3) deleted ?

  The SAP error message RSO874 indicates that the content status entry for a specific object (like a query, InfoProvider, or other BI objects) has been deleted. This can occur in SAP BW (Business Warehouse) or SAP BI (Business Intelligence) environments when the system cannot find the necessary metadata or content status for the specified object.
  Cause:
  
  Deletion of Object: The object (e.g., InfoObject, Query, etc.) may have been deleted or is no longer available in the system.
  Transport Issues: If the object was transported from one system to another, there may have been issues during the transport process that led to the loss of metadata.
  Inconsistent Metadata: The metadata in the system may be inconsistent due to manual changes or system errors.
  Versioning Issues: The specific version of the object may not exist or may have been deleted.
  
  Solution:
  
  Check Object Existence: Verify if the object (e.g., InfoObject, Query) still exists in the system. If it has been deleted, you may need to recreate it or restore it from a backup.
  Recreate Content Status: If the object exists but the content status is missing, you may need to recreate the content status entry. This can often be done by reactivating the object or performing a metadata refresh.
  Transport Check: If the issue arose after a transport, check the transport logs for errors and ensure that all necessary objects were transported correctly.
  Consistency Check: Run consistency checks in the BW system to identify and resolve any inconsistencies in the metadata.
  Version Management: If the issue is related to versioning, check if the correct version of the object is being referenced and ensure that it is active.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like RSA1 (Data Warehousing Workbench) to check the status of objects and their content.
  Logs and Traces: Check the system logs (transaction SLG1) for any related error messages that could provide more context on the issue.
  SAP Notes: Look for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to the specific object type you are working with for any known issues or best practices.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.