How To Fix EE_AMI_MSG120 - Not all messages created for current dunning notice

SAP Error Message - Details

• Message type: E = Error

• Message class: EE_AMI_MSG - Message Class for AMI Messaging

• Message number: 120

• Message text: Not all messages created for current dunning notice

What causes this issue?

For the current dunning notice, an error occurred when creating the
message to the device.

System Response

The system could not create all messages.

How to fix this error?

Check the error messages in the log for the related dunning activity
run.

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 EE_AMI_MSG120 - Not all messages created for current dunning notice ?

  The SAP error message EE_AMI_MSG120 ("Not all messages created for current dunning notice") typically occurs in the context of the dunning process within the SAP system, particularly when dealing with accounts receivable and customer billing. This error indicates that there was an issue with generating all the necessary dunning messages for a specific dunning notice.
  Causes:
  
  Incomplete Configuration: The dunning procedure may not be properly configured, leading to missing message types or settings.
  Missing Data: Required data for generating dunning messages may be missing or incomplete in the customer master data or dunning data.
  Technical Issues: There could be a technical issue or bug in the system that prevents the generation of all messages.
  Authorization Issues: The user may not have the necessary authorizations to create or view all dunning messages.
  Dunning Levels: If the dunning levels are not set up correctly, it may lead to incomplete message generation.
  
  Solutions:
  
  
  Check Dunning Configuration:
  
  Review the dunning procedure settings in the SAP system (transaction code OB77).
  Ensure that all necessary message types are defined and activated.
  
  
  
  Review Customer Master Data:
  
  Check the customer master data for completeness (transaction code FD03).
  Ensure that the dunning information is correctly maintained.
  
  
  
  Run Dunning Program Again:
  
  Sometimes, simply re-running the dunning program (transaction code F150) can resolve the issue if it was a temporary glitch.
  
  
  
  Check for System Errors:
  
  Look into the system logs (transaction code SLG1) for any related error messages that could provide more context.
  If there are technical issues, consider reaching out to your SAP Basis team for assistance.
  
  
  
  Authorization Check:
  
  Ensure that the user executing the dunning process has the necessary authorizations to create and view dunning messages.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide patches.
  
  
  
  Testing in Development:
  
  If possible, replicate the issue in a development or test environment to identify the root cause without affecting production data.
  
  
  
  Related Information:
  
  Dunning Process: Understand the dunning process in SAP, which involves sending reminders to customers for overdue payments.
  Dunning Levels: Familiarize yourself with how dunning levels work and how they affect message generation.
  SAP Documentation: Refer to SAP Help documentation for detailed information on dunning procedures and error handling.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support or a consultant who specializes in SAP Financials for further assistance.