SD Report Custom development ALV report

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

  • V.02 List of Incomplete Sales Orders. Lists incomplete orders at document level; no missing field name and no count per field.
  • VA02 Change Sales Order. Shows the incompletion log of one order and lets you fix it; no list across orders.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
VBAKSales Document HeaderSales 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 skippedVBUK-VBELN = VBAK-VBELNECC only
VBUVSales Document: Incompletion LogMissing-field records: item, table, field, incompletion and status groupVBUV-VBELN = VBAK-VBELNECC + S/4
DD03LTable FieldsData element of the missing fieldDD03L-TABNAME = VBUV-TBNAM AND DD03L-FIELDNAME = VBUV-FDNAMECC + S/4
DD04TData Element TextsField name in the user's languageDD04T-ROLLNAME = DD03L-ROLLNAME AND DD04T-DDLANGUAGE = SY-LANGUECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = VBAK-KUNNRECC + 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

ParameterDescriptionTypeReference fieldRequiredExample
S_VKORGSales organizationRange / multipleVBAK-VKORGYes1000
S_VTWEGDistribution channelRange / multipleVBAK-VTWEGNo10
S_AUARTOrder typeRange / multipleVBAK-AUARTNoTA
S_ERDATCreation dateRange / multipleVBAK-ERDATYes01.11.2026 – 17.11.2026
S_ERNAMCreated byRange / multipleVBAK-ERNAMNoSIPARIS01
S_FDNAMMissing fieldRange / multipleVBUV-FDNAMNoZTERM
P_DLVBLKBlocking delivery onlyCheckbox—No—

Output columns

#ColumnSource
1Sales orderVBAK-VBELN
2ItemVBUV-POSNR
3Order typeVBAK-AUART
4Sold-toVBAK-KUNNR
5Customer nameKNA1-NAME1
6TableVBUV-TBNAM
7FieldVBUV-FDNAM
8Missing field textCalculated DD04T-SCRTEXT_M of the data element of VBUV-TBNAM/FDNAM
9Status groupVBUV-STATG
10Net valueVBAK-NETWR
11CurrencyVBAK-WAERK
12Requested delivery dateVBAK-VDATU
13Created byVBAK-ERNAM

Sample output

Sales orderItemOrder typeSold-toCustomer nameTableFieldMissing field textStatus groupNet valueCurrencyRequested delivery dateCreated by
0000123560000000TA200145Marmara Yapı MarketVBKDZTERMTerms of payment0148,200TRY11/20/2026SIPARIS01
0000123561000000TA200310Kuzey Gıda DağıtımVBKDBSTKDCustomer PO number0112,750TRY11/19/2026SIPARIS02
0000123561000020TA200310Kuzey Gıda DağıtımVBEPEDATUDelivery date0212,750TRY11/19/2026SIPARIS02
0000123575000010TA200422Anadolu Elektrik ToptanVBAPWERKSPlant029,300TRY11/24/2026SIPARIS01
A view built with fictional sample data; not real system data.

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.

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

SD Package Custom

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 …

5 components · v1.0

Related reports

SD Report Custom ALV report

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 …

VBUK · VBAK · VBAP · VBUP

SD Report Custom ALV report

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 …

VBAK · VBAP · VBFA · LIKP

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.

Related report: Incomplete Sales Orders with Missing Fields Report