How To Fix VMD_API106 - Vendor &1: Default dunning area was deleted for company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: VMD_API - Vendor APIs

• Message number: 106

• Message text: Vendor &1: Default dunning area was deleted for company code &2

Similar to CMD_API106

What causes this issue?

The system checks whether the default dunning area exists for each
company code.

System Response

The system terminates processing if the check fails.

How to fix this error?

You must transfer the default dunning area for each company code during
creation. You can only delete the default dunning area during creation
if no other dunning areas exist for the company code concerned.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VMD_API106 - Vendor &1: Default dunning area was deleted for company code &2 ?

  The SAP error message VMD_API106 indicates that a default dunning area for a vendor has been deleted for a specific company code. This can occur in the context of vendor management and accounts payable processes within SAP.
  Cause:
  The error typically arises due to one of the following reasons:
  
  Deletion of Dunning Area: The default dunning area for the vendor was manually deleted or not properly configured in the system.
  Configuration Issues: There may be issues in the configuration settings related to dunning areas in the vendor master data.
  Data Inconsistency: There could be inconsistencies in the vendor master data or related tables that lead to the absence of a default dunning area.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Vendor Master Data:
  
  Go to the vendor master data (transaction code XK03 or MK03).
  Verify if the vendor has a default dunning area assigned for the relevant company code.
  
  
  
  Reassign Dunning Area:
  
  If the dunning area is missing, you can assign a new default dunning area to the vendor.
  Use transaction code XK02 or MK02 to edit the vendor master data and assign a valid dunning area.
  
  
  
  Review Dunning Configuration:
  
  Check the configuration of dunning areas in the system (transaction code OBD2).
  Ensure that the dunning area exists and is properly configured for the company code in question.
  
  
  
  Data Consistency Check:
  
  Run consistency checks on the vendor master data to identify any other potential issues.
  Use transaction code SE38 to run relevant reports or programs that can help identify inconsistencies.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to vendor dunning areas for any specific guidelines or updates.
  
  
  
  Contact SAP Support:
  
  If the issue persists after following the above steps, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Dunning Areas: Dunning areas are used in SAP to manage the dunning process for accounts receivable and payable. They define how dunning is processed for specific customers or vendors.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as XK01 (Create Vendor), XK02 (Change Vendor), XK03 (Display Vendor), and OBD2 (Dunning Area Configuration).
  SAP Notes: Check for any SAP Notes that may address specific issues related to dunning areas and vendor management.
  
  By following these steps, you should be able to resolve the error and ensure that the vendor has a valid default dunning area assigned.