How To Fix FARR_SDBP_MIGRATION035 - Table 'FARRIC_SDBPEXISTS' not updated for Logical system &1, RFC Dest &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_SDBP_MIGRATION - Message for SDBP RAI migration to new format

• Message number: 035

• Message text: Table 'FARRIC_SDBPEXISTS' not updated for Logical system &1, RFC Dest &2

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 FARR_SDBP_MIGRATION035 - Table 'FARRIC_SDBPEXISTS' not updated for Logical system &1, RFC Dest &2 ?

  The SAP error message FARR_SDBP_MIGRATION035 indicates that the table FARRIC_SDBPEXISTS has not been updated for a specific logical system and RFC destination. This error typically arises during the migration or configuration of the SAP system, particularly in the context of the SAP Flexible Real Estate Management (RE-FX) module or similar scenarios involving data migration.
  Cause:
  
  Missing Configuration: The logical system or RFC destination may not be properly configured in the system.
  Data Migration Issues: There may be issues with the data migration process, such as missing entries or incomplete data transfer.
  Authorization Issues: The user executing the migration may not have the necessary authorizations to update the table.
  Technical Issues: There could be underlying technical issues, such as database locks or connectivity problems with the RFC destination.
  
  Solution:
  
  
  Check Configuration:
  
  Verify that the logical system and RFC destination are correctly configured in the SAP system.
  Use transaction SM59 to check the RFC destination settings and ensure they are active and reachable.
  
  
  
  Update the Table Manually:
  
  If necessary, you can manually update the FARRIC_SDBPEXISTS table to include the missing entries for the logical system and RFC destination. This should be done with caution and ideally under the guidance of an SAP Basis or technical consultant.
  
  
  
  Review Migration Process:
  
  Review the migration process to ensure that all necessary steps have been completed. Check for any logs or error messages that may provide additional context.
  
  
  
  Check Authorizations:
  
  Ensure that the user executing the migration has the appropriate authorizations to perform updates on the relevant tables.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SM59: For checking and configuring RFC destinations.
  SE11: For viewing and managing database tables.
  SE37: For checking function modules related to the migration process.
  
  
  
  Documentation: Review the SAP documentation related to the specific module you are working with (e.g., RE-FX) for any additional configuration steps that may be required.
  
  
  Logs: Check the system logs (transaction SLG1) for any related error messages that could provide more context on the issue.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.