How To Fix RSDS035 - Inconsistent metadata: Non-permitted data record in &1

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDS - New DataSource

• Message number: 035

• Message text: Inconsistent metadata: Non-permitted data record in &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDS035 - Inconsistent metadata: Non-permitted data record in &1 ?

  The SAP error message RSDS035, which states "Inconsistent metadata: Non-permitted data record in &1," typically occurs in the context of SAP BW (Business Warehouse) or SAP BW/4HANA when there is an inconsistency in the metadata of a DataSource or InfoObject. This inconsistency can arise from various reasons, such as changes in the underlying data structure, issues during data loading, or problems with the DataSource configuration.
  Causes:
  
  Changes in DataSource Structure: If the structure of the DataSource has been modified (e.g., fields added or removed) without proper adjustments in the BW system, it can lead to inconsistencies.
  Data Loading Issues: If there were errors during the data loading process, it might leave the metadata in an inconsistent state.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production) without proper adjustments, inconsistencies can occur.
  Manual Changes: Manual changes to the DataSource or InfoObject in the BW system that do not align with the source system can lead to this error.
  
  Solutions:
  
  Check DataSource Configuration: Verify the configuration of the DataSource in the SAP BW system. Ensure that it matches the structure of the source system.
  Re-activate DataSource: Sometimes, reactivating the DataSource can resolve inconsistencies. You can do this by going to the DataSource in the Data Warehousing Workbench and reactivating it.
  Check for Transport Errors: If the issue arose after a transport, check the transport logs for any errors or warnings that might indicate what went wrong.
  Repair Metadata: Use transaction code RSDS to check the DataSource and repair any inconsistencies in the metadata.
  DataSource Replication: If necessary, replicate the DataSource again from the source system to ensure that the metadata is consistent.
  Check for Data Records: Investigate the specific data records mentioned in the error message. You may need to clean up or correct these records in the source system.
  
  Related Information:
  
  Transaction Codes: 
  
  RSDS - DataSource Maintenance
  RSA1 - Data Warehousing Workbench
  
  
  SAP Notes: Check for relevant SAP Notes that may address specific issues related to this error message. You can search the SAP Support Portal for notes related to RSDS035.
  Documentation: Review SAP documentation on DataSources and InfoObjects for best practices on maintaining metadata consistency.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further analysis and troubleshooting.