Do you have any question about this error?
Message type: E = Error
Message class: CMD_API - Customer APIs
Message number: 106
Message text: Customer &1: Default dunning area was deleted for company code &2
The system checks whether the default dunning area exists for each
company code.
The system terminates processing if the check fails.
Always transfer the default dunning area for a company code when
creating dunning data. You can only delete the default dunning area if
no other dunning areas exist for the company code concerned.
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.
CMD_API106
- Customer &1: Default dunning area was deleted for company code &2 ?The SAP error message CMD_API106 indicates that a default dunning area for a specific customer has been deleted for a particular company code. This can occur in the context of accounts receivable and dunning processes, where the system requires a valid dunning area to manage overdue payments and send dunning notices to customers.
Cause:
- Deletion of Dunning Area: The default dunning area for the customer was deleted, either intentionally or accidentally.
- Configuration Changes: Changes in the configuration settings related to dunning areas or customer master data may have led to this issue.
- Data Inconsistency: There may be inconsistencies in the customer master data or dunning area settings.
Solution:
To resolve this error, you can take the following steps:
Check Customer Master Data:
- Go to the customer master data (transaction code
FD03
for display).- Verify if the dunning area is still assigned to the customer for the relevant company code.
Reassign Dunning Area:
- If the dunning area has been deleted, you can reassign a valid dunning area to the customer.
- Use transaction code
FD02
to change the customer master data and assign a valid dunning area.Review Dunning Area 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 relevant company code.
Consult with SAP Basis or Functional Team:
- If you are unable to resolve the issue, consult with your SAP Basis or functional team to investigate further.
- They may need to check for any recent changes in the system that could have affected the dunning area.
Testing:
- After making the necessary changes, test the dunning process to ensure that the error does not reoccur.
Related Information:
FD03
: Display Customer Master DataFD02
: Change Customer Master DataOBD2
: Dunning Area ConfigurationBy following these steps, you should be able to resolve the CMD_API106 error and ensure that the dunning process functions correctly for the affected customer.
Get instant SAP help. Start your 7-day free trial now.
CMD_API105
Customer number &1 does not exist in company code &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CMD_API104
Customer number &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CMD_API107
Customer &1: Role &2 in sales area &3 has multiple default partners
What causes this issue? The system checks whether a default partner exists for each partner role in a sales area.System Response The system terminat...
CMD_API108
Customer &1: You cannot change role &3 in sales area &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.