How To Fix RSO879 - Object &1 &2 to be deleted could not be written to transport request

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO - BW Repository

• Message number: 879

• Message text: Object &1 &2 to be deleted could not be written to transport request

What causes this issue?

Object &V1& &V2& to be deleted could not be written to a transport
request.

System Response

The object is nevertheless deleted, but the deletion might not be
transported.

How to fix this error?

Write object R3TR &V1& &V2& to a transport request manually to transport
the deletion.

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 RSO879 - Object &1 &2 to be deleted could not be written to transport request ?

  The SAP error message RSO879 indicates that there is an issue with writing an object to a transport request. This typically occurs when you are trying to delete an object (like a query, InfoProvider, or other BI-related objects) and the system is unable to record this action in the transport request. Here are some common causes, solutions, and related information for this error:
  Causes:
  
  Transport Request Issues: The transport request may be locked, not created properly, or not assigned to the correct transport layer.
  Authorization Problems: The user may not have the necessary authorizations to modify or delete the object in the transport request.
  Object Status: The object you are trying to delete may be in a status that does not allow it to be transported (e.g., it might be in a released state).
  System Configuration: There may be configuration issues in the transport management system (TMS) that prevent the object from being written to the transport request.
  Object Dependencies: The object may have dependencies that are not being handled correctly, preventing the deletion from being recorded.
  
  Solutions:
  
  Check Transport Request: Ensure that the transport request is not locked and is properly configured. You can check the status of the transport request in transaction SE09 or SE10.
  User Authorizations: Verify that the user has the necessary authorizations to delete the object and write to the transport request. You may need to consult with your security team to ensure proper roles are assigned.
  Object Status: Check the status of the object you are trying to delete. If it is released or in a state that does not allow deletion, you may need to change its status or consult with the object owner.
  Transport Management System (TMS): Review the TMS configuration to ensure that it is set up correctly. You can use transaction STMS to check the transport routes and settings.
  Dependencies: Investigate any dependencies related to the object. If there are dependent objects that need to be handled first, address those before attempting to delete the main object.
  Manual Deletion: If the object cannot be deleted through the normal process, consider manually removing it from the system (if appropriate) and then creating a transport request for the changes.
  
  Related Information:
  
  Transaction Codes: Use SE09/SE10 for transport requests, SE80 for object management, and STMS for transport management.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to transport management and object deletion for best practices and guidelines.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with SAP support or your internal SAP Basis team for further assistance.