# Customers with Declining Order Intake vs Prior Year Report

> A custom ALV report that compares each customer's order value in the selected period with the same period of the previous year and shows the drop in percent, the last order date and the days without an order. Sales managers see customers that are slipping away without waiting for month end and plan their visits accordingly.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: S (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/customers-declining-order-intake-vs-prior-year-report/


## Why is the standard not enough?

VA05 lists the orders of a period, but it gives no per-customer comparison with the previous year, no drop percentage and no days since the last order. LIS analyses (information structures) are not updated in many systems or include rejected items. Teams download both periods separately and match them in Excel. The custom report calculates both periods from the documents in one run, leaves out rejected items and compares values in the statistics currency.

### Closest standard alternatives

- VA05: Lists the orders of one period; no per-customer comparison with the previous year, no drop percentage and no days without an order.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBAK | Order header: customer, order date, sales area, statistics currency (driving table) | Read | - | ECC + S/4 |
| VBAP | Item net value, statistics exchange rate and reason for rejection | Read | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| TVAK | Document category of the order type; quotations and contracts are excluded | Read | TVAK-AUART = VBAK-AUART | ECC + S/4 |
| KNA1 | Customer name and city | Read | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
| KNVV | Sales office and sales group of the customer | Read | KNVV-KUNNR = VBAK-KUNNR AND KNVV-VKORG = VBAK-VKORG AND KNVV-VTWEG = VBAK-VTWEG AND KNVV-SPART = VBAK-SPART | ECC + S/4 |
| I_SalesOrderItem | In S/4HANA it can replace VBAP with a clean core approach | Read | SalesOrder = VBAK-VBELN | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | Yes |
| S_VTWEG | Distribution channel | Range / multiple | VBAK-VTWEG | No |
| S_VKBUR | Sales office | Range / multiple | VBAK-VKBUR | No |
| S_KUNNR | Sold-to party | Range / multiple | VBAK-KUNNR | No |
| S_AUDAT | Current period (order date) | Range / multiple | VBAK-AUDAT | Yes |
| P_DROP | Minimum drop in percent | Single value | - | Yes |
| P_MINPY | Minimum prior-year order value | Single value | - | No |
| P_REJ | Exclude rejected items | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Customer | VBAK-KUNNR |
| Customer name | KNA1-NAME1 |
| City | KNA1-ORT01 |
| Sales office | KNVV-VKBUR |
| Sales group | KNVV-VKGRP |
| Orders (period) | Calculated: Number of distinct VBAK-VBELN in the current period |
| Order value (period) | Calculated: Σ VBAP-NETWR × VBAP-STCUR (current period) |
| Order value (prior year) | Calculated: Σ VBAP-NETWR × VBAP-STCUR (same period one year earlier) |
| Difference | Calculated: Period value − prior-year value |
| Change % | Calculated: Difference ÷ prior-year value × 100 |
| Last order date | Calculated: Latest VBAK-AUDAT |
| Days without order | Calculated: Today − last order date |
| Statistics currency | VBAK-STWAE |

## How does the report work?

1. The current period is the date range on the selection screen (VBAK-AUDAT); the comparison period is the same days one year earlier (29 February moves to 28 February).
2. VBAK and VBAP are read for both periods; the document category of the order type is checked through TVAK-VBTYP, and with "Exclude rejected items" selected, items with a reason for rejection (VBAP-ABGRU) are skipped.
3. The item net value (VBAP-NETWR) is converted with the statistics exchange rate (VBAP-STCUR) into the statistics currency (VBAK-STWAE), so customers ordering in different currencies can be compared.
4. Totals are built per sold-to party: number of distinct orders in the period, the value of both periods and the latest VBAK-AUDAT.
5. Change % = (current − prior) ÷ prior × 100. Customers whose prior-year value is above the minimum and whose drop exceeds the threshold remain; customers with no order in the current period appear with −100%.
6. Sales office and sales group are added from KNVV. The list is sorted by the difference in ascending order.

## Authorization objects

- V_VBAK_VKO: Sales document display authorization by sales area
- V_VBAK_AAT: Authorization by sales document type

## Frequently asked questions

### Why is the order value used instead of the invoiced value?

Order intake shows the customer's behaviour weeks before billing does, so a drop is noticed early. A comparison of the invoiced value (VBRP-NETWR) can be added with the same logic; this raises the effort range slightly.

### How are different currencies compared?

Each item is converted with the statistics exchange rate stored at order entry (VBAP-STCUR) into the statistics currency of the sales organization (VBAK-STWAE). No later exchange-rate effect is added, and both periods are totalled in the same currency.

### Does the report work on S/4HANA?

Yes. VBAK, VBAP, TVAK, KNA1 and KNVV also exist in S/4HANA. Even though customer master data is maintained as a business partner (BP), the customer number in KNA1 stays the same. For clean core, I_SalesOrderItem can be used.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-customer-order-intake-decline
