Dunning & Feedback Channel
Dunning procedure becomes dunning area, dunning area becomes dunning group — and the level reached must be reported back.
Two Terms, Two Fields
| SAP | Bilendo | Meaning |
|---|---|---|
A_CustomerDunning.DunningProcedure (dunning procedure, T047) | Dunning area → Dunning strategy | HOW dunning is carried out: levels, deadlines, fees, interest, channel |
DunningArea (dunning area, on the debtor and on the item) | Dunning group | WHICH items go into a letter |
Both travel as a custom field of type “mapped” on the debtor; the value mapping (procedure → dunning area) is provided by the customer as a table.
Who Performs Which Step
| Step | Who | Note |
|---|---|---|
| Payment reminder, 1st/2nd/3rd dunning notice, dunning fees, default interest | Bilendo | One strategy per dunning area; the SAP dunning run pauses as of the cutoff date for the affected accounts. |
| Dunning block, payment block, installment plan, deferral | SAP is the source | Bilendo follows: dunning_stop on the debtor and on the item. |
| Judicial dunning procedure | SAP | LegDunningProcedureOn — from this point on, no one sends commercial dunning notices anymore. |
| Delivery block, credit limit, collection handover | SAP, triggered by the reported level | If such a process depends on the level, the return channel is not just cosmetic. |
Transfer of Dunning Authority
During the initial extraction, Bilendo takes over the dunning level and last dunning date once — from the debtor (A_CustomerDunning.DunningLevel, LastDunnedOn) and from the item (DunningLevel, LastDunningDate) —, so that an account at level 2 does not start over at level 1. After that, Bilendo manages the level and reports it back.
The Return Channel
It is the only write operation toward SAP and carries, per customer or item, level, date, and dunning area.
Preferred: a
PATCHonA_CustomerDunningvia the standard API of the business partner. Whether your system allows this is the first question in the QA system — it's a candidate, not a guarantee.Otherwise, the usual approach: Z-fields on the item (append structure) or a Z-table with item key, level, date, dunning area; populated from a file read by an SAP job, or via webhook on each change.
The dunning level on the item (MHND) cannot be written via any released API. Where downstream processes depend on it, this belongs in planning, not in go-live.