Incomplete Sales Orders with Missing Fields Report
Short answer: A custom ALV report that lists sales orders with an incompletion log, one line per missing field, with the field name, the affected item, the order value, the requested delivery date and the user who created the order. It shows in one list which field is forgotten most often and which orders cannot ship because of it.
- Estimated effort
- S · 2–4 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
V.02 lists incomplete documents at document level; to see which field is missing, the incompletion log of each order has to be opened separately in VA02. There is no standard list that shows the missing field, the order value, the requested date and the creating user on the same line and counts the errors per field.
Who uses it? Customer service and order entry teams, sales operations managers and SD consultants.
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 | Sales area, order type, customer, net value, requested date and creating user (driving table) | — | ECC + S/4 |
| VBUKSales Document Header Status (ECC) | Header incompletion status; complete documents are skipped | VBUK-VBELN = VBAK-VBELN | ECC only |
| VBUVSales Document: Incompletion Log | Missing-field records: item, table, field, incompletion and status group | VBUV-VBELN = VBAK-VBELN | ECC + S/4 |
| DD03LTable Fields | Data element of the missing field | DD03L-TABNAME = VBUV-TBNAM AND DD03L-FIELDNAME = VBUV-FDNAM | ECC + S/4 |
| DD04TData Element Texts | Field name in the user's language | DD04T-ROLLNAME = DD03L-ROLLNAME AND DD04T-DDLANGUAGE = SY-LANGU | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
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_AUART | Order type | Range / multiple | VBAK-AUART | No | TA |
| S_ERDAT | Creation date | Range / multiple | VBAK-ERDAT | Yes | 01.11.2026 – 17.11.2026 |
| S_ERNAM | Created by | Range / multiple | VBAK-ERNAM | No | SIPARIS01 |
| S_FDNAM | Missing field | Range / multiple | VBUV-FDNAM | No | ZTERM |
| P_DLVBLK | Blocking delivery only | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Sales order | VBAK-VBELN |
| 2 | Item | VBUV-POSNR |
| 3 | Order type | VBAK-AUART |
| 4 | Sold-to | VBAK-KUNNR |
| 5 | Customer name | KNA1-NAME1 |
| 6 | Table | VBUV-TBNAM |
| 7 | Field | VBUV-FDNAM |
| 8 | Missing field text | Calculated DD04T-SCRTEXT_M of the data element of VBUV-TBNAM/FDNAM |
| 9 | Status group | VBUV-STATG |
| 10 | Net value | VBAK-NETWR |
| 11 | Currency | VBAK-WAERK |
| 12 | Requested delivery date | VBAK-VDATU |
| 13 | Created by | VBAK-ERNAM |
Sample output
| Sales order | Item | Order type | Sold-to | Customer name | Table | Field | Missing field text | Status group | Net value | Currency | Requested delivery date | Created by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0000123560 | 000000 | TA | 200145 | Marmara Yapı Market | VBKD | ZTERM | Terms of payment | 01 | 48,200 | TRY | 11/20/2026 | SIPARIS01 |
| 0000123561 | 000000 | TA | 200310 | Kuzey Gıda Dağıtım | VBKD | BSTKD | Customer PO number | 01 | 12,750 | TRY | 11/19/2026 | SIPARIS02 |
| 0000123561 | 000020 | TA | 200310 | Kuzey Gıda Dağıtım | VBEP | EDATU | Delivery date | 02 | 12,750 | TRY | 11/19/2026 | SIPARIS02 |
| 0000123575 | 000010 | TA | 200422 | Anadolu Elektrik Toptan | VBAP | WERKS | Plant | 02 | 9,300 | TRY | 11/24/2026 | SIPARIS01 |
How does the report work?
- VBAK is read with the sales area, order type and creation date from the selection screen; documents whose VBUK incompletion status fields (UVALL, UVALS, UVVLK) are not complete remain.
- For these documents the missing-field records are read from VBUV: item (POSNR), schedule line (ETENR), table (TBNAM), field (FDNAM), incompletion group (FEHGR) and status group (STATG).
- A readable field name is taken from DD04T in the user’s language through the data element in DD03L.
- With “Blocking delivery only” selected, only records in status groups that block delivery remain.
- Order value, requested delivery date and creating user are added from VBAK, the customer name from KNA1. ALV shows subtotals and counts per field.
Performance notes
VBUV only holds records for incomplete documents, so it is small; limiting the selection by creation date is enough. Read the field texts from DD04T once per table/field pair and buffer them.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the order number opens VA02, where the incompletion log can be called.
- Export to Excel
- Runs as a background job
- Send the result by email Each user can receive the incomplete orders they created every morning.
Authorization objects
- V_VBAK_VKOSales document display authorization by sales area
- V_VBAK_AATAuthorization by sales document type
Frequently asked questions
Where does the missing-field information come from?
SAP writes a VBUV record for every field left empty according to the incompletion procedure. The report reads these records, so it lists the same fields that appear in the standard incompletion log.
Can quotations and returns be listed too?
Yes. Quotation, return or contract types can be entered in the document type field; the logic is the same.
Does it work on S/4HANA?
Yes. In S/4HANA the VBUK status fields moved to VBAK, so the selection is done on VBAK; VBUV keeps the same structure.
Packages that include this solution
Order-to-Cash Control Pack
A five-report pack that shows every point where a sales order gets stuck, with one sales organization selection: missing data, credit blocks, picked …
Related reports
Credit-Blocked Sales Orders by Value and Age Report
A custom ALV report that groups credit-blocked sales orders per credit account and shows the blocked order value, the age of the oldest block, the …
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.