# Backorders and Unconfirmed Sales Order Items Report

> A custom ALV report that shows, for open sales orders, how much of the requested quantity is not confirmed, the value of that quantity, how many days the customer has been waiting and whether unrestricted stock exists in the plant, all in one list. Sales and planning teams see at once which customer is waiting on which item and whether a rescheduling run would help.

- 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/backorders-unconfirmed-sales-order-items-report/


## Why is the standard not enough?

V.15 shows backorders per material or customer, but it does not show the value of the unconfirmed quantity, the days the customer has been waiting and the unrestricted stock in the plant on the same line. VA05 lists the confirmed quantity but calculates neither the difference nor its age. Teams rebuild this table in Excel every week. The custom report derives the unconfirmed quantity from the schedule lines, converts it to value and flags items that remain unconfirmed although stock exists.

### Closest standard alternatives

- V.15: Shows backorders per material or customer; no unconfirmed value, days waiting or unrestricted stock in the same list.
- VA05: Lists orders and the confirmed quantity; does not calculate the unconfirmed difference or its age.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBAK | Order header: customer, sales area, currency (driving table) | Read | - | ECC + S/4 |
| VBAP | Item: material, plant, net price, reason for rejection | Read | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| VBEP | Schedule lines: requested date, ordered and confirmed quantity | Read | VBEP-VBELN = VBAP-VBELN AND VBEP-POSNR = VBAP-POSNR | ECC + S/4 |
| VBUP | Item delivery status in ECC | Read | VBUP-VBELN = VBAP-VBELN AND VBUP-POSNR = VBAP-POSNR | ECC only |
| KNA1 | Customer name | Read | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
| MARD | Unrestricted stock in the plant | Read | MARD-MATNR = VBAP-MATNR AND MARD-WERKS = VBAP-WERKS | ECC + S/4 |
| I_SalesDocumentScheduleLine | In S/4HANA it can replace VBEP with a clean core approach | Read | SalesDocument = VBAK-VBELN | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | Yes |
| S_AUART | Order type | Range / multiple | VBAK-AUART | No |
| S_KUNNR | Sold-to party | Range / multiple | VBAK-KUNNR | No |
| S_WERKS | Plant | Range / multiple | VBAP-WERKS | No |
| S_MATNR | Material | Range / multiple | VBAP-MATNR | No |
| S_EDATU | Requested delivery date range | Range / multiple | VBEP-EDATU | No |
| P_KEYDT | Key date for days waiting (default: today) | Single value | SY-DATUM | Yes |
| P_NOCONF | Only items with no confirmation at all | Checkbox | - | No |
| P_STOCK | Show unrestricted stock | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Sales order | VBAK-VBELN |
| Item | VBAP-POSNR |
| Customer | VBAK-KUNNR |
| Customer name | KNA1-NAME1 |
| Material | VBAP-MATNR |
| Description | VBAP-ARKTX |
| Plant | VBAP-WERKS |
| Requested delivery date | VBEP-EDATU |
| Ordered qty | Calculated: Σ VBEP-WMENG |
| Confirmed qty | Calculated: Σ VBEP-BMENG |
| Unconfirmed qty | Calculated: Ordered qty − confirmed qty |
| Unit | VBAP-VRKME |
| Unconfirmed value | Calculated: Unconfirmed qty × VBAP-NETPR ÷ VBAP-KPEIN |
| Currency | VBAK-WAERK |
| Days waiting | Calculated: Key date − VBEP-EDATU |
| Unrestricted stock | Calculated: Σ MARD-LABST in the plant |

## How does the report work?

1. VBAK and VBAP are read with the selection-screen criteria; only order-category documents (VBAK-VBTYP = C), items without a reason for rejection (VBAP-ABGRU) and items not fully delivered are kept (VBUP-LFSTA ≠ C in ECC, VBAP-LFSTA in S/4HANA).
2. The VBEP schedule lines of each item are summed: ordered quantity = Σ VBEP-WMENG, confirmed = Σ VBEP-BMENG. Unconfirmed quantity = the difference; items where it is zero are skipped.
3. The requested delivery date is VBEP-EDATU of the first schedule line. Days waiting = key date − that date.
4. Unconfirmed value = unconfirmed quantity × VBAP-NETPR ÷ VBAP-KPEIN.
5. With "Show unrestricted stock" selected, the sum of MARD-LABST for the material in the plant is added. Items that are unconfirmed although stock exists are highlighted; they usually need a rescheduling run (V_V2) or a change to the availability check setup.
6. The result is sorted by days waiting, with subtotals per material and customer.

## Authorization objects

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

## Frequently asked questions

### How is the unconfirmed quantity calculated?

The sum of the requested quantity (VBEP-WMENG) over all schedule lines of the item minus the sum of the confirmed quantity (VBEP-BMENG). Rejected and fully delivered items are not included.

### Why would an item be unconfirmed while stock exists?

If the stock arrived after the order was entered and no rescheduling run (V_V2) took place, or the stock is reserved for other orders, the item stays unconfirmed. The report flags these items; running it again after rescheduling shows the effect.

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

Yes. VBUP does not exist in S/4HANA; the delivery status is read from VBAP-LFSTA. For a clean core approach, I_SalesDocumentScheduleLine can replace VBEP.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-backorders-unconfirmed-items
