How To Fix CRM_BSP_PROD111 - Basic Customizing in table &1 for relationship type &2 is missing

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_BSP_PROD - Messages for BSP Interface of CRM Product Master

• Message number: 111

• Message text: Basic Customizing in table &1 for relationship type &2 is missing

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 CRM_BSP_PROD111 - Basic Customizing in table &1 for relationship type &2 is missing ?

  The SAP error message "CRM_BSP_PROD111 Basic Customizing in table &1 for relationship type &2 is missing" typically indicates that there is a missing configuration in the SAP system related to the Business Partner (BP) relationships in the CRM module. This error often arises when the system is trying to access or display a relationship type that has not been properly defined or configured in the relevant customizing tables.
  Cause:
  
  Missing Configuration: The specific relationship type (e.g., a relationship between a customer and a product) has not been defined in the customizing tables.
  Incorrect Table Entries: The entries in the customizing tables may be incomplete or incorrect.
  Transport Issues: If the configuration was transported from another system, it may not have been transported correctly, leading to missing entries.
  Version Mismatch: There may be a mismatch between the version of the customizing settings and the version of the CRM application being used.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the transaction code SPRO and navigate to the relevant customizing path for CRM.
  Check the settings for the relationship types under the relevant section (e.g., "Basic Functions" -> "Business Partner" -> "Define Relationship Types").
  Ensure that the relationship type specified in the error message is defined in the relevant table.
  
  
  
  Maintain Missing Entries:
  
  If the relationship type is missing, create a new entry for it in the customizing table.
  Ensure that all required fields are filled out correctly.
  
  
  
  Transport Requests:
  
  If the configuration was supposed to be transported, check the transport requests to ensure that they were imported correctly.
  If necessary, re-transport the relevant customizing settings.
  
  
  
  Check for Notes and Patches:
  
  Check the SAP Support Portal for any notes or patches related to this error message. There may be known issues or updates that address this problem.
  
  
  
  Testing:
  
  After making the necessary changes, test the functionality again to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO for customizing settings.
  BP for managing business partners.
  
  
  Tables: 
  
  The specific table mentioned in the error message (e.g., BUT050 for business partner relationships).
  
  
  Documentation: 
  
  SAP Help documentation for CRM Business Partner and relationship types.
  
  
  SAP Notes: 
  
  Search for relevant SAP Notes that might provide additional insights or solutions.
  
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation.