Dunning Level Return Channel

The only way back to SAP: dunning level, dunning date, and dunning area per item.

Bilendo runs dunning. For the blocking process in IS-U to keep working, SAP needs to know which level an item has reached in Bilendo: the level reported back triggers the SAP dunning activity — for a basic supply account, “level 3 reached” is the starting signal for the disconnection threat.

What Bilendo delivers

• per item: item key (contract · document · company code · line), dunning level, date of the last dunning notice, dunning area

• as an export (a file that an SAP job reads in) or a webhook per change

• optionally dunning fees and late payment interest as amounts, if accounting needs them as FI-CA items

Where to write in SAP

The FI-CA dunning history cannot be written to from outside. Common approaches are Z fields on the item (extending DFKKOP via the intended append structures) or a Z table with item key, level, date, and dunning area. The receiver — an import report or a Z OData service with write permission — is built by the customer or their partner; the related questions are in the “Dunning level return channel” catalog.

The return channel is the only write operation toward SAP. It does not run through the data handler but is a Bilendo feature plus an SAP receiver.