Sales Order – Delivery – Invoice Status Report
Short answer: 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 not shipped, which deliveries have not been billed and how much of the order value has turned into invoices.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
VA05 lists orders, VL06O deliveries and VF05 invoices separately. The document flow is visible only for one document at a time in VA03. Seeing the shipping and billing status of hundreds of orders in one list needs a custom report.
Who uses it? Sales operations, customer service, logistics and billing teams.
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 | Order header, sales area and customer (driving table); in S/4HANA it also holds the overall status | — | ECC + S/4 |
| VBAPSales Document Item | Order item, material, quantity and net value | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| VBFASales Document Flow | Document flow from order to delivery and invoice | VBFA-VBELV = VBAP-VBELN AND VBFA-POSNV = VBAP-POSNR | ECC + S/4 |
| LIKPDelivery Header | Delivery number and goods issue date | LIKP-VBELN = VBFA-VBELN (VBTYP_N = J) | ECC + S/4 |
| VBRKBilling Document Header | Invoice number and billing date | VBRK-VBELN = VBFA-VBELN (VBTYP_N = M) | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
| VBUKSales Document Header Status (ECC) | Overall order status in ECC | VBUK-VBELN = VBAK-VBELN | ECC only |
S/4HANA notes
- VBUK → VBAK: VBUK is not used in S/4HANA. The status fields moved to the respective document header: VBAK for sales, LIKP for deliveries, VBRK for billing. It is one of the most common fixes when custom reports move from ECC.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | Yes | 1000 |
| S_VTWEG | Distribution channel | Range / multiple | VBAK-VTWEG | No | 10 |
| S_SPART | Division | Range / multiple | VBAK-SPART | No | 00 |
| S_AUART | Sales document type | Range / multiple | VBAK-AUART | No | OR |
| S_KUNNR | Sold-to party | Range / multiple | VBAK-KUNNR | No | 200100 |
| S_AUDAT | Order date range | Range / multiple | VBAK-AUDAT | Yes | 01.10.2026 – 31.10.2026 |
| S_VBELN | Sales document | Range / multiple | VBAK-VBELN | No | 12001 |
| P_OPEN | Incomplete orders only | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Sales order | VBAK-VBELN |
| 2 | Item | VBAP-POSNR |
| 3 | Sold-to | VBAK-KUNNR |
| 4 | Customer name | KNA1-NAME1 |
| 5 | Material | VBAP-MATNR |
| 6 | Order qty | VBAP-KWMENG |
| 7 | Unit | VBAP-VRKME |
| 8 | Net value | VBAP-NETWR |
| 9 | Currency | VBAK-WAERK |
| 10 | Delivery | LIKP-VBELN |
| 11 | Goods issue date | LIKP-WADAT_IST |
| 12 | Invoice | VBRK-VBELN |
| 13 | Billing date | VBRK-FKDAT |
| 14 | Overall status | Calculated ECC: VBUK-GBSTK, S/4HANA: VBAK-GBSTK (A open, B partially processed, C completed) |
Sample output
| Sales order | Item | Sold-to | Customer name | Material | Order qty | Unit | Net value | Currency | Delivery | Goods issue date | Invoice | Billing date | Overall status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 12001 | 10 | 200100 | Marmara Gıda | FG-5001 | 500 | PC | 155,000 | TRY | 80004501 | 10/12/2026 | 90007801 | 10/13/2026 | Completed |
| 12001 | 20 | 200100 | Marmara Gıda | FG-5002 | 200 | PC | 48,000 | TRY | 80004501 | 10/12/2026 | Partially processed | ||
| 12044 | 10 | 200245 | Karadeniz Market | FG-5001 | 120 | PC | 37,200 | TRY | Open |
How does the report work?
- VBAK and VBAP are read with the selection criteria; items with a reason for rejection (ABGRU) can be excluded.
- For each item, subsequent documents are read from VBFA: VBTYP_N = J are deliveries, VBTYP_N = M are invoices.
- Delivery data (actual goods issue date) comes from LIKP, invoice data (billing date) from VBRK.
- Overall status is read from VBUK-GBSTK in ECC and from VBAK-GBSTK in S/4HANA.
- When an item has several deliveries, each delivery is shown on its own line; the customer name is added from KNA1.
Performance notes
VBFA is a large table; read it by preceding document (VBELV + POSNV) with a VBTYP_N filter. Keep the order date range mandatory. In S/4HANA the VBFA key changed, so do not rely on read order; sort explicitly.
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 Unbilled deliveries can be sent to the billing team every morning.
Authorization objects
- V_VBAK_VKOSales document authorization by sales area
- V_VBAK_AATAuthorization by sales document type
Frequently asked questions
How are the order, delivery and invoice linked?
Through the VBFA document flow table. The preceding document is the order item (VBELV, POSNV) and the subsequent document is the delivery (VBTYP_N = J) or invoice (VBTYP_N = M).
What changes in this report on S/4HANA?
S/4HANA no longer uses VBUK and VBUP; the status fields moved to VBAK, VBAP, LIKP and VBRK. Reports that read VBUK in ECC must be adjusted at this point.
How are partial deliveries shown?
Each delivery of an order item is shown on its own line; a summarized one-line-per-item view can be added if needed.
Related reports
Vendor Open Items Aging Report
A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …
Open Purchase Orders by Vendor Report
A custom ALV report that shows, per vendor, the quantity not yet received, the open order value and the days of delay since the delivery date in a …
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.