3787390 - Dunning list is empty after excluding blocked items in Dunning proposal

• The generated Dunning List is empty: "List does not contain any data", no dunning notice is issued.
• Blocked documents (Dunning Block set) are correctly excluded from the proposal and appear in the exception list.
• Removing the dunning block from the blocked items causes the Dunning List to generate successfully. Reapplying the block causes the list to become empty again.

SAP S/4HANA Cloud Public Edition

1. Configure a dunning procedure where the Days in Arrears for Dunning Level 1 is lower than the Min. Days in Arrears (Acct) value.
   For example:
   • Dunning Level 1 – Days in Arrears: 2 days
   • Min. Days in Arrears (Acct): 6 days
2. Ensure that the customer account contains:
   • Multiple overdue invoices without a dunning block.
   • Credit memos or other open items with a dunning block.
3. Use the Create Dunning Notices app to create a dunning proposal.
4. Open the proposal log and review the dunning items.
5. Observe that:
   • The eligible invoices are assigned Dunning Level 1.
   • The blocked documents are excluded from the dunning proposal.
   • The proposal log confirms that dunning data has been generated and account items are output.
6. Open the Dunning List.
7. Observe that the Dunning List displays "List does not contain any data" and no dunning notice is issued.

The dunning procedure evaluates fulfilled before a dunning notice receives the status "to be sent".

1. Days in Arrears (Dunning Level): Defines the minimum number of days an individual line item must be overdue to be assigned a dunning level. When this threshold is met, the system assigns the dunning level and logs that dunning data has been generated - this is why the proposal log shows successful processing.
2. Min. Days in Arrears (Account): Defines an additional account-level condition. The dunning notice is only issued if at least one open item on the account reaches this minimum number of days in arrears.

When documents carrying a dunning block are excluded from the dunning run, the remaining unblocked items may not individually satisfy the Min. Days in Arrears (Account) threshold — even though they meet the per-level days in arrears condition.In this case, the dunning notice is not eligible to be sent and therefore does not appear in the Dunning List, although the proposal log confirms that dunning data was generated.
This is standard and expected system behavior in SAP S/4HANA Cloud Public Edition.

Depending on the business requirement, consider one of the following options:

Option 1 – Run the dunning proposal at a later date
Create a new dunning proposal once the eligible open items fulfill the configured Min. Days in Arrears (Acct) requirement.

Option 2 – Review the dunning procedure configuration
Review the Days in Arrears and Min. Days in Arrears (Acct) settings in the relevant dunning procedure.
If the business requirement is to issue a dunning notice when an item reaches the configured dunning-level threshold, consider adjusting Min. Days in Arrears (Acct) accordingly.

Note: Changes to the dunning procedure may affect all customers using the procedure.

Option 3 – Review the dunning blocks
Check whether the dunning blocks on the excluded items are still required.
If a dunning block is no longer applicable from a business perspective, remove it and re-evaluate the dunning proposal.

KBA 3662677 - Dunning notices not sent for overdue invoices due to blocked customer account in dunning run – SAP S/4HANA Cloud Public Edition

dunning list empty, dunning proposal, min days in arrears (acct), account minimum days in arrears, dunning notice not to be sent, dunning block, reason e, blocked items, credit memo, create dunning notices app, fi-ar, receivables management, public cloud, always dun, print all items , KBA , FI-AR-AR-C-2CL , Dunning/Interest (Public Cloud) , Problem