Do you have any question about this error?
Message type: E = Error
Message class: RSO - BW Repository
Message number: 859
Message text: Error occurred when saving dependent object &4 of &1 &2 to a request (&3)
The additional object &V4& (required by object &V1& &V2&) could not be
saved to an order (&V3&).
The additional object &V4& will not be transported with object &V1& &V2&
Eliminate - if possible - the cause of the error and save / activate /
transport the object &V1& &V2& again.
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.
RSO859
- Error occurred when saving dependent object &4 of &1 &2 to a request (&3) ?The SAP error message RSO859 indicates that there was an issue when trying to save a dependent object (like a query, InfoObject, or other related objects) to a transport request. This error typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when working with data models, queries, or other objects that are part of a transport process.
Causes:
- Transport Request Issues: The transport request may be locked, incomplete, or not properly configured.
- Authorization Problems: The user may not have the necessary authorizations to save the object to the transport request.
- Object Dependencies: The dependent object may have issues or dependencies that are not resolved, preventing it from being saved.
- System Errors: There could be temporary system issues or inconsistencies in the database that are causing the error.
- Version Conflicts: There may be version conflicts between the objects being transported and the existing objects in the target system.
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.
- Review Authorizations: Verify that the user has the necessary authorizations to perform the action. This may involve checking roles and permissions in transaction PFCG.
- Resolve Dependencies: Investigate the dependent object mentioned in the error message. Ensure that all dependencies are resolved and that the object is in a consistent state.
- System Check: Perform a system check to identify any inconsistencies or issues. You can use transaction SE14 to check for database inconsistencies.
- Retry the Operation: Sometimes, simply retrying the operation after a short period can resolve temporary issues.
- Consult Logs: Check the system logs (transaction SLG1) for more detailed error messages that may provide additional context for the issue.
- Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it appears to be a system-level issue.
Related Information:
By following these steps, you should be able to diagnose and resolve the RSO859 error effectively.
Get instant SAP help. Start your 7-day free trial now.
RSO858
&1 &2: Dependant objects are not subject to recording in requests
What causes this issue? The successive objects in the log, dependant on the BW object &V1& &V2& , are not subject to requisite record...
RSO857
Error &2 during after import handling of objects with type(s) &1
What causes this issue? When handling objects with type(s) &V1&, an error message (&V2&) was not caught. The error message can be fou...
RSO860
BW systems with MDMP configuration are not supported
What causes this issue? Multiple Display - Multiple Processing (MDMP) is not supported for BW systems.System Response The system issues an error mes...
RSO861
Upgrade running (phase &1) - you can only make limited changes to objects
What causes this issue? The upgrade is already running in phase &V1&. DDIC and program objects have already been saved for the repository rep...
Click on this link to search all SAP messages.