Do you have any question about this error?
Message type: E = Error
Message class: RSDD_LM - Messages for Lean Modeler (API and RSLIMO)
Message number: 135
Message text: The InfoObject name for column &1 will change
The global InfoObject currently being used cannot be used any more for
the field. The BEx queries on this CompositeProvider have to be
adjusted, as the name of the InfoObject will change. The reason that the
global InfoObject cannot be used any more might be an additional
mapping.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the connection of the field or adjust the dependent BEx queries.
Error message extract from SAP system. Copyright SAP SE.
RSDD_LM135
- The InfoObject name for column &1 will change ?The SAP error message RSDD_LM135 indicates that there is a change in the InfoObject name for a column in a query or data model. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BW/4HANA when there are changes made to InfoObjects, such as renaming or modifying them.
Cause:
- Renaming of InfoObjects: The most common cause is that an InfoObject has been renamed in the data model or InfoProvider, which leads to inconsistencies in queries or reports that reference the old name.
- Changes in Data Model: Changes in the underlying data model, such as modifications to the structure of InfoProviders or InfoObjects, can also trigger this message.
- Transport Issues: If changes were transported from one system to another (e.g., from development to production), and the InfoObject names were not updated accordingly, this error may arise.
Solution:
- Update Queries: If the InfoObject has been renamed, you need to update any queries or reports that reference the old name. This can be done in the Query Designer or BEx Query Designer by replacing the old InfoObject with the new one.
- Check Data Model: Review the data model and ensure that all references to the InfoObject are consistent. This includes checking InfoProviders, transformations, and data flows.
- Re-activate Objects: Sometimes, reactivating the affected InfoObjects or queries can resolve the issue. This can be done in the SAP BW system by navigating to the InfoObject or query and selecting the reactivation option.
- Transport Consistency: If the issue is related to transport, ensure that all relevant objects have been transported correctly and that there are no inconsistencies between the development and production environments.
- Consult Documentation: Check SAP notes or documentation for any specific guidance related to the version of SAP BW you are using, as there may be version-specific considerations.
Related Information:
By following these steps, you should be able to resolve the RSDD_LM135 error and ensure that your queries and reports function correctly with the updated InfoObject names.
Get instant SAP help. Start your 7-day free trial now.
RSDD_LM134
Error while displaying the documentation
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDD_LM133
Column &1 in InfoProvider &2 is not correctly defined
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDD_LM136
InfoObject &1 is already an attribute of reference InfoObject &2
What causes this issue? InfoObject &V1& is already an attribute of reference characteristic &V2& . It cannot be added as a local attr...
RSDD_LM137
Reference InfoObject &1 does not exist
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.