How To Fix FT343 - Dunning procedure & does not exist. Delete and create again

SAP Error Message - Details

• Message type: E = Error

• Message class: FT - FI Table Maintenance Error Messages

• Message number: 343

• Message text: Dunning procedure & does not exist. Delete and create again

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 FT343 - Dunning procedure & does not exist. Delete and create again ?

  The SAP error message FT343 indicates that there is an issue with the dunning procedure in the system. Specifically, it suggests that the dunning procedure you are trying to use does not exist or is not properly configured. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Non-Existent Dunning Procedure: The dunning procedure you are trying to use has not been created in the system.
  Incorrect Configuration: The dunning procedure may have been deleted or not properly configured in the system.
  Authorization Issues: The user may not have the necessary authorizations to access or modify the dunning procedure.
  Data Inconsistency: There may be inconsistencies in the data related to the dunning procedure.
  
  Solution:
  
  
  Check Dunning Procedure:
  
  Go to the transaction code OBD2 (Dunning Procedure) to check if the dunning procedure exists.
  If it does not exist, you will need to create it.
  
  
  
  Create a New Dunning Procedure:
  
  If the dunning procedure is missing, you can create a new one using transaction code OBD2.
  Fill in the necessary details such as the dunning procedure name, description, and other relevant settings.
  
  
  
  Delete and Recreate:
  
  If the dunning procedure exists but is not functioning correctly, consider deleting it and recreating it.
  Ensure that you have a backup or documentation of the settings before deletion.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access and modify dunning procedures.
  You may need to consult with your SAP security team to verify and adjust authorizations.
  
  
  
  Review Configuration:
  
  Check the configuration settings related to dunning procedures in the Financial Accounting (FI) module.
  Ensure that all related settings (like dunning levels, dunning texts, etc.) are correctly configured.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help files for detailed steps on creating and configuring dunning procedures.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OBD2: To create or modify dunning procedures.
  OBD3: To display existing dunning procedures.
  
  
  
  Dunning Procedure Settings: Dunning procedures can include various settings such as dunning levels, dunning texts, and parameters that control how dunning is processed.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to dunning procedures that might be relevant to your version of SAP.
  
  
  Testing: After creating or modifying a dunning procedure, it is advisable to test it in a development or quality environment before applying changes to the production system.
  
  
  By following these steps, you should be able to resolve the FT343 error and ensure that your dunning procedures are correctly set up in SAP.