Dunning run header and item history per customer with dunning-level and customer name.
| Company Code | Customer | Dunning Run Date | Dunning Run ID | Dunning Level | Document Number | Fiscal Year | Line Item |
|---|---|---|---|---|---|---|---|
| 2000 | 100200 | 2026-06-26 | 01 | 03 | 1900002300 | 2026 | 02 |
| 1000 | 100483 | 2026-03-02 | 02 | 03 | 1900002511 | 2026 | Z1 |
| 2000 | 100766 | 2026-06-03 | 03 | 03 | 1900002722 | 2026 | 03 |
| 1000 | 101049 | 2026-04-12 | 10 | 04 | 1900002933 | 2026 | 10 |
| 2000 | 101332 | 2026-05-04 | 10 | 03 | 1900003144 | 2026 | 10 |
| 2000 | 101615 | 2026-04-17 | 01 | 03 | 1900003355 | 2026 | 10 |
| 1000 | 101898 | 2026-04-06 | 10 | 01 | 1900003566 | 2026 | 03 |
Connects read-only inside your own SAP session — your business data is never changed.
Your filters run inside SAP, so only matching rows ever travel the wire.
The engine links every source table on the correct key fields, automatically.
Raw SAP codes are resolved into readable names and descriptions on the way out.
Formatted rows land in your sheet, guarded by a max-row limit for fast first runs.
The report keeps its selection — one click pulls the latest data, any time.
Pre-selected key fields with text lookups resolved — customize freely.
Key relationships resolved automatically. Joins, text lookups and filter push-down are engineered by SAP solution architects — zero ABAP on your side.
Excel add-in, read-only in your own SAP session, live data in minutes. ECC & S/4HANA.
Dunning History 360 condenses what finance and controlling teams usually chase across multiple SAP screens into a single sheet: dunning run header and item history per customer with dunning-level and customer name. Rather than working through transactions one object at a time, you get 16 pre-selected columns side by side — keys, descriptions and organizational context in one place, ready to filter, pivot and share.
The usual route to this data is F150 for the on-screen view, followed by SE16 downloads of MHNK, MHND, KNA1 stitched together in Excel. Each export is a snapshot: text fields arrive as codes, the joins are rebuilt by hand, and by the time the workbook reconciles, the numbers are already a day old. Multiply that by every month-end or every expediting run, and the report becomes a job of its own.
In PostNow the report ships ready to run. The 4 underlying tables (MHNK, MHND, KNA1, KNB1) are already joined on the correct key fields, code values are resolved into plain-language texts, and results land directly in Excel. Every run is read-only inside your own SAP session — the engine reads data, it never changes it. Refresh whenever you need a current version, tighten the filters, or use the report as a starting point and adjust columns in the visual builder. It behaves identically on SAP ECC and S/4HANA.
It joins 4 tables — MHNK, MHND, KNA1, KNB1 — on their standard key fields. Text and check tables are resolved automatically, so the output shows readable names and descriptions instead of raw codes, and the 16 delivered columns can be extended in the visual builder if you need more.
Transactions like F150 show the data on screen, but a clean Excel extract from them means manual exports and re-formatting every time. PostNow reads the same tables through standard interfaces — no ABAP, no transports. You pick the report in the Excel add-in, set filters such as company code and date range, and the joined result is written straight into your sheet. Every run is read-only and happens inside your own SAP session — nothing is ever written back.
Yes. Every report has selection filters with SAP value help, so you can narrow by company code, posting or document dates, plants, accounts and more before anything is fetched. A max-rows guard keeps first runs fast, and once the selection looks right you can widen it and refresh — the report remembers your filters.
This preview uses sample data. Run the real thing from Excel in minutes — read-only, in your own SAP session.