3734132 - Dunning run assigns level 1 instead of highest level for 60+ day overdue items - SAP S/4HANA Cloud Public Edition

The dunning run is assigning Level 1 for an open item overdue by 60+ days instead of the highest level as defined in the dunning procedure configuration.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

SAP S/4HANA Cloud Public Edition

1. Define a dunning procedure with multiple levels (for example: 1/7/14/21/30/45/60/75/90 days).
2. Assign this dunning procedure to a customer.
3. Ensure the customer has at least one open item overdue beyond the highest threshold (for example, 60+ days), and clear any existing dunning levels on items and on the customer.
4. Run “Create Dunning Notices” on a date where the oldest item is 60+ days overdue.
5. Observe that the system assigns dunning level 1 instead of the highest level.

The system behaves as expected.

1. Verify the customer’s current dunning level in the correspondence data; if it is blank, the first successful dunning run will set the level to 1 regardless of how overdue the oldest item is.

2. Note that in S/4HANA Cloud Public Edition, dunning level escalation is progressive and does not jump to the highest level in a single run.

3. To reach higher levels, perform subsequent dunning runs according to your dunning schedule so the level increases progressively based on the procedure thresholds.

Dunning level, Progressive, Create Dunning Notices, Overdue item, Accounts Receivable, Dunning procedure, Correspondence tab, Public Cloud, Grace days. , KBA , FI-AR-AR-C-2CL , Dunning/Interest (Public Cloud) , Problem