Do you have any question about this error?
Message type: E = Error
Message class: RSO - BW Repository
Message number: 602
Message text: Keep existing texts for InfoProvider &1 in language &2
Texts in language &V2& were found in InfoProvider &V1&. These texts are
not, however, included in the 'D' version delivered by SAP.
The system retains these texts when it adjusts the SAP version to match
the active version.
Check whether it is necessary to adjust the texts in this language.
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.
RSO602
- Keep existing texts for InfoProvider &1 in language &2 ?The SAP error message RSO602 typically occurs in the context of SAP BW (Business Warehouse) when there is an issue related to the texts of an InfoProvider (like InfoCubes, DataStore Objects, etc.) in a specific language. The message indicates that the system is unable to keep the existing texts for the specified InfoProvider in the specified language.
Cause:
- Missing Language Texts: The texts for the InfoProvider in the specified language may not exist in the system.
- Inconsistent Language Settings: There may be inconsistencies in the language settings for the InfoProvider or the system.
- Transport Issues: If the InfoProvider was transported from one system to another, the texts may not have been transported correctly.
- Authorization Issues: The user may not have the necessary authorizations to view or modify the texts in the specified language.
Solution:
- Check Language Settings: Verify that the language settings for the InfoProvider are correct. You can do this by checking the InfoProvider's properties in the SAP BW modeling tools.
- Maintain Texts: If the texts are missing, you can maintain them by going to the relevant transaction (like RSA1 for InfoProviders) and adding the necessary texts for the specified language.
- Transport Texts: If the InfoProvider was transported, ensure that the texts were included in the transport request. You may need to re-transport the texts if they were missed.
- Authorization Check: Ensure that the user has the necessary authorizations to access and modify the texts for the InfoProvider.
- Check for Errors in the Transport Logs: If the issue arose after a transport, check the transport logs for any errors that might indicate why the texts were not transported correctly.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
RSO601
InfoProvider &1: The active version is different to the modified version
What causes this issue? You want to transfer the InfoProvider &v1& as delivered by SAP.System Response When the system compared the 'D&...
RSO600
----- Messages for Matching A/D Version InfoCubes / MultiProvider -------
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSO603
InfoObject &1 transferred from the 'M' version of InfoProvider &2
What causes this issue? The stored version of InfoProvider &V2& contains InfoObject &V1&. This InfoObject is not, however, present in...
RSO604
InfoObject &1 was assigned to dimension &2
What causes this issue? In the saved 'M' version, InfoObject &V1& is assigned to a different dimension to 'D' version.Sys...
Click on this link to search all SAP messages.