How To Fix /FTI/BO_STRUCT_DEL035 - Fetching change records.

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/BO_STRUCT_DEL -

• Message number: 035

• Message text: Fetching change records.

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 /FTI/BO_STRUCT_DEL035 - Fetching change records. ?

  The SAP error message /FTI/BO_STRUCT_DEL035 Fetching change records typically relates to issues encountered when trying to fetch change records in the context of SAP's Financial Transaction Infrastructure (FTI) or Business Object (BO) structures. This error can arise due to various reasons, including data inconsistencies, configuration issues, or problems with the underlying database.
  Possible Causes:
  
  Data Inconsistencies: There may be inconsistencies in the data stored in the database, which can prevent the system from fetching change records correctly.
  Configuration Issues: Incorrect configuration settings in the FTI or related modules can lead to this error.
  Database Issues: Problems with the database, such as locks, corruption, or performance issues, can also cause this error.
  Authorization Issues: Lack of proper authorizations for the user trying to fetch the change records can lead to this error.
  System Performance: High load on the system or database can lead to timeouts or failures in fetching records.
  
  Solutions:
  
  Check Data Consistency: Use transaction codes like SE11 or SE16 to check the relevant tables for inconsistencies. You may need to run consistency checks or repair tools provided by SAP.
  Review Configuration: Ensure that the configuration settings for FTI and related modules are correct. This may involve checking settings in transaction codes like SPRO.
  Database Health Check: Perform a health check on the database. Look for locks, long-running queries, or any signs of corruption. You may need to work with your database administrator to resolve these issues.
  User Authorizations: Verify that the user has the necessary authorizations to access the change records. This can be checked in transaction SU53 or by reviewing the user's roles and profiles.
  System Performance Monitoring: Monitor system performance and database load. If the system is under heavy load, consider optimizing queries or increasing resources.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve known issues.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for FTI and BO structures for detailed information on configuration and troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11, SE16, SPRO, and SU53 for data checks, configuration, and authorization checks.
  
  If the issue persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.