How To Fix FTBU347 - Partner & not yet converted

SAP Error Message - Details

• Message type: E = Error

• Message class: FTBU - Conversion: Treasury partner CBP messages

• Message number: 347

• Message text: Partner & not yet converted

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 FTBU347 - Partner & not yet converted ?

  The SAP error message FTBU347 "Partner & not yet converted" typically occurs in the context of financial accounting or when dealing with business partner data in SAP. This error indicates that a specific partner (such as a vendor or customer) has not been fully converted to the new business partner model, which is often part of the transition to S/4HANA or when implementing the Business Partner (BP) functionality in SAP.
  Cause:
  
  Incomplete Migration: The business partner data has not been fully migrated from the legacy system or from the previous data model to the new business partner model.
  Missing Configuration: The necessary configuration settings for the business partner might not be in place.
  Data Inconsistencies: There may be inconsistencies or missing data in the partner records that prevent them from being recognized as fully converted.
  Transaction Type: The transaction being executed may require a fully converted partner, and the current partner record does not meet this requirement.
  
  Solution:
  
  Check Business Partner Status: Use transaction code BP to check the status of the business partner in question. Ensure that it has been fully created and activated.
  Run Migration Programs: If you are migrating from an older system, ensure that all necessary migration programs have been executed successfully. This may include programs for converting vendor and customer data to the business partner format.
  Review Configuration: Verify that the configuration settings for business partners are correctly set up in the system. This includes checking the relevant customizing settings in SPRO.
  Data Consistency Check: Perform a data consistency check to identify any missing or inconsistent data in the business partner records. You may need to correct or complete the data.
  Consult Documentation: Refer to SAP documentation or notes related to business partner conversion for specific guidance on resolving this error.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP (Business Partner), OXK1 (Define Account Groups), and others that may be involved in business partner management.
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional guidance on business partner conversion issues.
  Training and Documentation: Review SAP training materials or documentation related to business partner management and migration processes, especially if you are transitioning to S/4HANA.
  
  By following these steps, you should be able to identify the cause of the FTBU347 error and implement a solution to resolve it.