3736965 - Dunning Block Not Triggered for Dispute Cases in Collections and Dispute Automation - SAP S/4HANA Cloud Public Edition

• In SAP S/4HANA Cloud System, Dispute Management have been configured to automatically set dunning blocks on dispute items.
• When a dispute case is created, the "dunning block" field remains empty in the journal entries.
• BRF+ and Event Handling logs show that progress is triggered, but no update occurs on the line item.

SAP S/4HANA Cloud Public Edition

1. Create dispute case on receivable item.
2. Check event handling /message monitoring /FINDC.
3. Check receivable item business blocks section and find that the "dunning block" field remains empty.

In SAP S/4HANA Cloud Public Edition, the "dunning procedure" is a mandatory pre-requisite for any dunning-related action on a journal entry.

Even though the automation is triggered via "Collection and Dispute Automation", the system cannot update the "dunning block" field if the business partner’s company code is missing a “dunning procedure”. Without this procedure, the line item is technically invisible to the dunning logic.

1. Navigate to app Maintain Business Partner app.
2. Locate the affected BP and switch to the FI Customer role.
3. Ensure a valid “Dunning Procedure” is assigned and saved.

Note: Once the master data is corrected, the system will now successfully apply the block to the receivable item automatically.

/findc, acdocdblck, 00003, dunning block, receivable item, brf+, dispute case, business blocks, message monitoring, aif, dunning procedure, customer master data, s/4hana cloud, collections and dispute, fi item update , KBA , FIN-FIO-CCD-COL-2CL , Fiori-UI for Collections and Dispute Management (Public Cld) , Problem