How To Fix /SMB/FKCHK035 - Values are not found in reference master data tables in the database

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/FKCHK -

• Message number: 035

• Message text: Values are not found in reference master data tables in the database

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 /SMB/FKCHK035 - Values are not found in reference master data tables in the database ?

  The SAP error message /SMB/FKCHK035 Values are not found in reference master data tables in the database typically occurs in the context of financial transactions, particularly when dealing with the SAP Business One or SAP S/4HANA systems. This error indicates that the system is unable to find certain values in the reference master data tables that are necessary for processing a transaction.
  Causes:
  
  Missing Master Data: The most common cause is that the required master data (such as customers, vendors, or accounts) has not been created or is missing in the database.
  Incorrect Configuration: There may be configuration issues where the system is looking for values in the wrong tables or the wrong fields.
  Data Migration Issues: If data has been migrated from another system, some records may not have been transferred correctly, leading to missing references.
  Data Integrity Issues: There may be inconsistencies or corruption in the database that prevent the system from finding the necessary values.
  
  Solutions:
  
  Check Master Data: Verify that the required master data exists in the system. For example, if the error is related to a customer, ensure that the customer record is present and correctly configured.
  Create Missing Records: If you identify that certain records are missing, create them in the system. This may involve creating new customers, vendors, or accounts as needed.
  Review Configuration: Check the configuration settings in the system to ensure that they are set up correctly and that the system is pointing to the right tables and fields.
  Data Migration Review: If the issue arose after a data migration, review the migration process to ensure that all necessary data was transferred correctly. You may need to re-import or fix any missing records.
  Database Integrity Check: Run database integrity checks to identify and resolve any inconsistencies or corruption in the database.
  Consult Documentation: Refer to SAP documentation or support resources for specific guidance related to the error message and the context in which it occurs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as SE11 (Data Dictionary) to check table structures or SE16 (Data Browser) to view table contents.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance. Provide them with detailed information about the error, including the context in which it occurs and any steps you have already taken to resolve it.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.