Solution : https://service.sap.com/sap/support/notes/374213 (SAP Service marketplace login required)
Summary :
In SAP automatic credit control (Transaction OVA8), issues occur where documents are not blocked despite exceeding the configured highest dunning level ('High.dunn.level'). The system defaults to checking the highest dunning level against open customer items rather than the dunning level within the customer master data. During the checking process, if a customer's open item dunning level surpasses the highest dunning level set in Customizing, the document faces credit blocking. This mechanism ensures current status reflection, considering any new payments which might alter the dunning status until the next dunning review cycle, thereby keeping the credit management process up-to-date and aligned with active customer records within SAP's R/3 system.
Key words :
terms maximum dunning level, highest dunning level stored, highest dunning level set, exceeded highest dunning level, highest dunning level determined, knb5-mahns > t691f-dunng, post incoming payments, customer master data, highest dunning level, dunning level displayed
Related Notes :
| 425483 | Consulting note collection: Credit checks |