Returns and Credit Memos by Return Reason Report
Short answer: A custom ALV report that lists return orders with the return reason, the original invoice, the goods receipt of the return delivery and the credit memo amount on the same line. Sales and quality teams see which customer, material and reason drive returns, with the value attached.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
In VA05 returns are listed together with other orders; the return reason, the referenced invoice, the goods receipt of the return delivery and the credit memo are not on the same line. VF05 lists credit memos but not the return reason or the original invoice. There is no standard list of total return value and return rate per reason.
Who uses it? Sales managers, customer service, quality teams and financial controllers who track the cost of returns.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| VBAKSales Document Header | Return document header: type, customer, date and return reason (driving table) | — | ECC + S/4 |
| VBAPSales Document Item | Returned material, quantity and reference to the original invoice | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| VBFASales Document Flow | Document flow to the return delivery and the credit memo | VBFA-VBELV = VBAP-VBELN AND VBFA-POSNV = VBAP-POSNR | ECC + S/4 |
| LIKPDelivery Header | Goods receipt date of the return delivery | LIKP-VBELN = VBFA-VBELN (VBTYP_N = T) | ECC + S/4 |
| VBRKBilling Document Header | Credit memo header and cancellation flag | VBRK-VBELN = VBFA-VBELN (VBTYP_N = O) | ECC + S/4 |
| VBRPBilling Document: Item Data | Credit memo amount and quantity on the original invoice | VBRP-VBELN = VBRK-VBELN; orijinal fatura için VBRP-VBELN = VBAP-VGBEL AND VBRP-POSNR = VBAP-VGPOS | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
| I_CustomerReturnItemReturns Order Item | In S/4HANA it can be read for return items with a clean core approach | CustomerReturn = VBAK-VBELN | S/4HANA only |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | Yes | 1000 |
| S_AUART | Return document type | Range / multiple | VBAK-AUART | No | RE |
| S_AUDAT | Document date | Range / multiple | VBAK-AUDAT | Yes | 01.07.2026 – 31.10.2026 |
| S_KUNNR | Customer | Range / multiple | VBAK-KUNNR | No | 200145 |
| S_AUGRU | Return reason | Range / multiple | VBAK-AUGRU | No | R02 |
| S_MATNR | Material | Range / multiple | VBAP-MATNR | No | FG-1002 |
| P_OPEN | Only returns without a credit memo | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Return order | VBAK-VBELN |
| 2 | Item | VBAP-POSNR |
| 3 | Return reason | VBAK-AUGRU |
| 4 | Customer | VBAK-KUNNR |
| 5 | Customer name | KNA1-NAME1 |
| 6 | Material | VBAP-MATNR |
| 7 | Returned qty | VBAP-KWMENG |
| 8 | Unit | VBAP-VRKME |
| 9 | Original invoice | VBAP-VGBEL |
| 10 | Billed qty | VBRP-FKIMG |
| 11 | Return rate % | Calculated VBAP-KWMENG ÷ VBRP-FKIMG on the original invoice × 100 |
| 12 | Return delivery | LIKP-VBELN |
| 13 | Goods receipt date | LIKP-WADAT_IST |
| 14 | Credit memo | VBRK-VBELN |
| 15 | Credit amount | VBRP-NETWR |
| 16 | Currency | VBRK-WAERK |
Sample output
| Return order | Item | Return reason | Customer | Customer name | Material | Returned qty | Unit | Original invoice | Billed qty | Return rate % | Return delivery | Goods receipt date | Credit memo | Credit amount | Currency |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0060001201 | 000010 | R02 Damaged goods | 200145 | Marmara Yapı Market | FG-1002 | 24 | PC | 0090045512 | 300 | 8 | 0084000311 | 10/09/2026 | 0070002210 | 3,360 | TRY |
| 0060001215 | 000010 | R05 Wrong product | 200310 | Kuzey Gıda Dağıtım | FG-2050 | 50 | KG | 0090045588 | 1,200 | 4.20 | 0084000327 | 10/15/2026 | 0070002231 | 2,150 | TRY |
| 0060001229 | 000010 | R02 Damaged goods | 200422 | Anadolu Elektrik Toptan | FG-3110 | 5 | PC | 0090045630 | 80 | 6.30 | 0084000341 | 10/27/2026 | 0 | TRY |
How does the report work?
- Returns (VBAK-VBTYP = H) and credit memo requests (K) are read with the sales area, document type and date range from the selection screen; the return reason comes from VBAK-AUGRU.
- The original invoice is taken from the item reference (VBAP-VGBEL / VGPOS); without a reference, the preceding billing document in VBFA (VBTYP_V = M) is used. The billed quantity is VBRP-FKIMG.
- The return delivery (VBTYP_N = T) is found through VBFA and its goods receipt date is added from LIKP-WADAT_IST.
- The credit memo (VBTYP_N = O) is read from VBRK/VBRP; cancelled documents (VBRK-FKSTO) are skipped.
- Return rate = returned quantity ÷ quantity on the original invoice × 100. ALV shows subtotals per return reason, customer and material.
Performance notes
Select the return documents by document type and date range; read VBFA once with the list of return items. Run long periods in the background.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking a document number opens VA03, VL03N or VF03.
- Export to Excel
- Runs as a background job
- Send the result by email A monthly returns summary can be sent to the sales and quality managers.
Authorization objects
- V_VBAK_VKOSales document display authorization by sales area
- V_VBAK_AATAuthorization by sales document type
- V_VBRK_VKOBilling document authorization by sales organization
Frequently asked questions
What happens to returns without a reason?
They are listed in a "no reason" group. If the return reason is made a mandatory field for the return document type, this group disappears over time.
Can returns be linked to quality notifications?
Yes. If the return order or delivery is stored in the quality notification (QMEL), the notification number and defect code can be added as extra columns.
Does it work on S/4HANA?
Yes. The sales and billing tables used keep the same structure in S/4HANA; for clean core, I_CustomerReturnItem and the billing CDS views can be used.
Related reports
Customer Complaints Traced to Delivery, Batch and Inspection Lot Report
A custom ALV report that shows customer complaint notifications on the same line as the delivery, the batch, the inspection lot of that batch, its …
Sales Order – Delivery – Invoice Status Report
A custom ALV report that shows every sales order item on the same line as its delivery and invoice documents. You see in one list which orders have …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.