Do you have any question about this error?
Message type: E = Error
Message class: RSO - BW Repository
Message number: 321
Message text: Source systems are not transported
When you collected the objects in the transport connection, you also
collected one or more source systems.
The source system(s) are not written to the transport request.
First, create the source system in the target system of the transport,
and then import the transport.
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.
RSO321
- Source systems are not transported ?The SAP error message RSO321 indicates that source systems are not transported. This typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with the transport of source system definitions from one SAP system to another, such as from a development environment to a production environment.
Cause:
- Missing Source System Definition: The source system you are trying to use is not defined in the target system.
- Transport Request Issues: The transport request that was supposed to carry the source system definition may not have been released or imported correctly.
- Inconsistent Transport Directory: There may be inconsistencies in the transport directory or issues with the transport management system.
- Authorization Issues: The user may not have the necessary authorizations to access the source system or to perform the transport.
Solution:
Check Source System Definition:
- Verify that the source system is defined in the target system. You can do this by navigating to the relevant transaction (e.g., RSA1 for Data Warehousing Workbench) and checking the source system settings.
Transport Request:
- Ensure that the transport request containing the source system definition has been properly released in the development system.
- Check the transport logs for any errors or warnings that might indicate why the transport did not succeed.
Import Transport:
- If the transport request is available but not yet imported into the target system, perform the import using transaction STMS (Transport Management System).
Recreate Source System:
- If the source system is missing and cannot be transported, you may need to manually recreate the source system in the target environment.
Check Authorizations:
- Ensure that the user performing the transport has the necessary authorizations to access and manage source systems.
Consult SAP Notes:
- Check for any relevant SAP Notes that might address specific issues related to source system transport. SAP Notes can provide patches or additional guidance.
Related Information:
By following these steps, you should be able to resolve the RSO321 error and ensure that your source systems are correctly transported and available in the target SAP environment.
Get instant SAP help. Start your 7-day free trial now.
RSO320
Internal error &1 when reading the object catalog entry (TADIR)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSO319
The post-processing lasts &1 seconds
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSO322
Error &3 when changing object catalog entry for object &1 (&2)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSO323
Exception '&3' in progrmm '&4' when passing type '&1' &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.