# Incomplete Sales Orders with Missing Fields Report

> 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.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: S (2–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/incomplete-sales-orders-missing-fields-report/


## 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.

### Closest standard alternatives

- V.02: Lists incomplete orders at document level; no missing field name and no count per field.
- VA02: Shows the incompletion log of one order and lets you fix it; no list across orders.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBAK | Sales area, order type, customer, net value, requested date and creating user (driving table) | Read | - | ECC + S/4 |
| VBUK | Header incompletion status; complete documents are skipped | Read | VBUK-VBELN = VBAK-VBELN | ECC only |
| VBUV | Missing-field records: item, table, field, incompletion and status group | Read | VBUV-VBELN = VBAK-VBELN | ECC + S/4 |
| DD03L | Data element of the missing field | Read | DD03L-TABNAME = VBUV-TBNAM AND DD03L-FIELDNAME = VBUV-FDNAM | ECC + S/4 |
| DD04T | Field name in the user's language | Read | DD04T-ROLLNAME = DD03L-ROLLNAME AND DD04T-DDLANGUAGE = SY-LANGU | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |

## 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_AUART | Order type | Range / multiple | VBAK-AUART | No |
| S_ERDAT | Creation date | Range / multiple | VBAK-ERDAT | Yes |
| S_ERNAM | Created by | Range / multiple | VBAK-ERNAM | No |
| S_FDNAM | Missing field | Range / multiple | VBUV-FDNAM | No |
| P_DLVBLK | Blocking delivery only | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Sales order | VBAK-VBELN |
| Item | VBUV-POSNR |
| Order type | VBAK-AUART |
| Sold-to | VBAK-KUNNR |
| Customer name | KNA1-NAME1 |
| Table | VBUV-TBNAM |
| Field | VBUV-FDNAM |
| Missing field text | Calculated: DD04T-SCRTEXT_M of the data element of VBUV-TBNAM/FDNAM |
| Status group | VBUV-STATG |
| Net value | VBAK-NETWR |
| Currency | VBAK-WAERK |
| Requested delivery date | VBAK-VDATU |
| Created by | VBAK-ERNAM |

## How does the report work?

1. 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.
2. 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).
3. A readable field name is taken from DD04T in the user's language through the data element in DD03L.
4. With "Blocking delivery only" selected, only records in status groups that block delivery remain.
5. Order value, requested delivery date and creating user are added from VBAK, the customer name from KNA1. ALV shows subtotals and counts per field.

## Authorization objects

- V_VBAK_VKO: Sales document display authorization by sales area
- V_VBAK_AAT: Authorization 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-incomplete-orders-missing-fields
