How To Fix FSBP_TC104 - BP relationship category &1 for selection variant &2 was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: FSBP_TC -

• Message number: 104

• Message text: BP relationship category &1 for selection variant &2 was not found

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 FSBP_TC104 - BP relationship category &1 for selection variant &2 was not found ?

  The SAP error message FSBP_TC104 indicates that a specific business partner (BP) relationship category for a given selection variant was not found. This error typically arises in the context of business partner management, particularly when trying to access or manipulate relationships between business partners in the SAP system.
  Cause:
  
  Missing Relationship Category: The specified relationship category does not exist in the system for the given selection variant.
  Incorrect Configuration: The configuration for business partner relationships may not be set up correctly, leading to the absence of the expected relationship category.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables that define business partner relationships.
  Selection Variant Issues: The selection variant being used may not be properly defined or may not correspond to any existing relationship categories.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for business partner relationships in the SAP system (transaction code BP or SPRO).
  Verify that the relationship category you are trying to use is defined and active for the selection variant in question.
  
  
  
  Define Missing Relationship:
  
  If the relationship category is indeed missing, you may need to create it. This can be done in the configuration settings under the business partner relationship management section.
  
  
  
  Review Selection Variant:
  
  Ensure that the selection variant you are using is correctly defined and corresponds to the relationship categories you expect to work with.
  
  
  
  Data Consistency Check:
  
  Perform a consistency check on the business partner data to ensure that all necessary entries are present and correctly configured.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on business partner relationships and selection variants.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  BP - Business Partner Maintenance
  SPRO - Customizing Implementation Guide
  
  
  Tables: 
  
  Check relevant tables such as BUT000 (Business Partner: General Data) and BUT050 (Business Partner: Relationships) for any inconsistencies or missing entries.
  
  
  SAP Notes: 
  
  Look for SAP Notes related to business partner management and relationship categories for any known issues or patches.
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.