How To Fix CMD_API036 - Customer &1: Date of 'last dunning' is in the future; correct

CMD_API036 - Overview

• Message type: E = Error

• Message class: CMD_API - Customer APIs

• Message number: 036

• Message text: Customer &1: Date of 'last dunning' is in the future; correct

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.

CMD_API036 - Details

• The SAP error message CMD_API036 indicates that there is an issue with the "last dunning" date for a customer. Specifically, it means that the date recorded as the last dunning date is set in the future, which is not valid. This can occur due to data entry errors or system issues.
  
  Cause:
  
  Data Entry Error: The user may have mistakenly entered a future date for the last dunning date.
  System Migration or Data Upload: If data was migrated or uploaded into the system, there may have been an error in the data that resulted in future dates being set.
  Incorrect Configuration: There may be a configuration issue in the dunning process that allows for future dates to be set.
  
  
  Solution:
  
  
  Correct the Date: 
  
  Navigate to the customer master data or the dunning data for the specific customer (Customer ID &1).
  Update the "last dunning" date to a valid date (i.e., a date that is today or in