How To Fix RSAR660 - Obselete field definitions deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: RSAR - Data Transfer and Metadata Maintenance

• Message number: 660

• Message text: Obselete field definitions deleted

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 RSAR660 - Obselete field definitions deleted ?

  The SAP error message RSAR660, which states "Obsolete field definitions deleted," typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when there are outdated or obsolete field definitions in the data model or InfoObjects.
  Cause:
  
  Obsolete Field Definitions: This error indicates that there are field definitions in your InfoObjects or data models that are no longer valid or have been marked for deletion. This can happen due to changes in the data model, such as the removal of fields or changes in the structure of InfoObjects.
  Data Model Changes: If there have been recent changes to the data model, such as the addition or removal of fields, the system may automatically clean up obsolete definitions.
  Transport Issues: Sometimes, if changes are transported from one system to another (e.g., from development to production), inconsistencies can arise, leading to obsolete definitions.
  
  Solution:
  
  Check InfoObjects: Review the InfoObjects in your data model to identify any obsolete fields. You can do this by navigating to the InfoObject maintenance transaction (e.g., RSA1) and checking the definitions.
  Delete Obsolete Fields: If you find any obsolete fields, you can delete them from the InfoObject definition. Ensure that these fields are not being used in any queries or reports before deletion.
  Re-activate InfoObjects: After making changes, you may need to re-activate the InfoObjects to ensure that the changes take effect.
  Check for Dependencies: Ensure that there are no dependencies on the obsolete fields in queries, transformations, or data flows. If there are, you may need to update those objects accordingly.
  Transport Consistency: If the issue arose after a transport, check the transport logs for any inconsistencies and ensure that all related objects were transported correctly.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to RSAR660 for any specific guidance or patches that may address this issue.
  Documentation: Review SAP documentation on InfoObjects and data modeling in BW/BI for best practices on managing field definitions.
  System Logs: Look at system logs (transaction SLG1) for additional context or related error messages that may provide more insight into the issue.
  SAP Community: Engage with the SAP Community forums for discussions and solutions shared by other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the RSAR660 error and maintain a clean and efficient data model in your SAP BW/BI environment.