# On-Time In-Full (OTIF) Delivery Performance Report by Customer

> A custom ALV report that compares every sales order item with the customer's requested delivery date and ordered quantity, and works out whether the item was delivered on time, in full, and both (OTIF). Sales and logistics teams see the OTIF percentage per customer, plant and material in one monthly list.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/otif-on-time-in-full-delivery-report-by-customer/


## Why is the standard not enough?

VA05 lists orders with the first schedule-line date and VL06O shows deliveries and their goods issue status. Neither compares the customer's requested delivery date with the actual goods issue date and the ordered quantity with the delivered quantity to flag each item as on time, in full or OTIF and to give a percentage per customer. Sales information system analyses depend on statistics updates and do not show partial deliveries at item level. Teams usually calculate the figure every month by merging several lists in Excel.

### Closest standard alternatives

- VA05: Lists orders and the first schedule-line date; no comparison with the actual goods issue date and no OTIF percentage.
- VL06O: Tracks deliveries and goods issue status; does not compare them with the requested date and order quantity.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBAK | Sales area, order type, customer and requested delivery date in the header (driving table) | Read | - | ECC + S/4 |
| VBAP | Material, plant, order quantity and reason for rejection | Read | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| VBEP | Requested delivery date in the first schedule line | Read | VBEP-VBELN = VBAP-VBELN AND VBEP-POSNR = VBAP-POSNR | ECC + S/4 |
| VBFA | Document flow from order item to delivery item | Read | VBFA-VBELV = VBAP-VBELN AND VBFA-POSNV = VBAP-POSNR AND VBFA-VBTYP_N = 'J' | ECC + S/4 |
| LIPS | Delivered quantity | Read | LIPS-VBELN = VBFA-VBELN AND LIPS-POSNR = VBFA-POSNN | ECC + S/4 |
| LIKP | Actual goods issue date | Read | LIKP-VBELN = LIPS-VBELN | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = VBAK-KUNNR | 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_VTWEG | Distribution channel | Range / multiple | VBAK-VTWEG | No |
| S_AUART | Order type | Range / multiple | VBAK-AUART | No |
| S_KUNNR | Sold-to party | Range / multiple | VBAK-KUNNR | No |
| S_VDATU | Requested delivery date range | Range / multiple | VBAK-VDATU | Yes |
| S_WERKS | Plant | Range / multiple | VBAP-WERKS | No |
| P_TOLD | On-time tolerance (days) | Single value | - | No |
| P_TOLQ | In-full tolerance (%) | Single value | - | No |

## Output columns

| Column | Source |
|---|---|
| Sales order | VBAK-VBELN |
| Item | VBAP-POSNR |
| Sold-to | VBAK-KUNNR |
| Customer name | KNA1-NAME1 |
| Material | VBAP-MATNR |
| Order qty | VBAP-KWMENG |
| Delivered qty | Calculated: Sum of LIPS-LFIMG over the linked delivery items |
| Unit | VBAP-VRKME |
| Requested date | VBEP-EDATU |
| Actual goods issue | LIKP-WADAT_IST |
| Days late | Calculated: Last LIKP-WADAT_IST − VBEP-EDATU (negative: early) |
| On time | Calculated: X when days late ≤ day tolerance |
| In full | Calculated: X when delivered ≥ VBAP-KWMENG × (1 − quantity tolerance) |
| OTIF | Calculated: X when both On time and In full are X |

## How does the report work?

1. VBAK and VBAP are read with the sales area, order type, customer and requested delivery date range from the selection screen; items with a reason for rejection (VBAP-ABGRU) are skipped.
2. The requested date of each item is taken from the first schedule line (VBEP, ETENR = 0001) as EDATU; without a schedule line, VBAK-VDATU from the header is used.
3. The delivery items linked to the order item (VBTYP_N = J) are found through VBFA. LIPS-LFIMG is summed as the delivered quantity and the latest LIKP-WADAT_IST is taken as the actual goods issue date. Deliveries without goods issue are not counted.
4. On time = last goods issue date ≤ requested date + day tolerance. In full = delivered quantity ≥ VBAP-KWMENG × (1 − quantity tolerance %). OTIF = both.
5. The result is shown in ALV at item level; subtotals per customer and plant calculate on-time %, in-full % and OTIF %.

## Authorization objects

- V_VBAK_VKO: Sales document display authorization by sales area
- V_VBAK_AAT: Authorization by sales document type
- V_LIKP_VST: Delivery authorization by shipping point

## Frequently asked questions

### How is OTIF calculated?

An item is on time when its last goods issue date is not later than the requested date plus the day tolerance, and in full when the delivered quantity reaches the order quantity within the tolerance. The OTIF percentage is the share of items that meet both conditions.

### Why is the goods issue date used instead of the date the customer received the goods?

The goods issue date exists on every delivery. If proof of delivery or transit times are used, the comparison can be extended to that date; this raises the effort range slightly.

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

Yes. VBAK, VBAP, VBEP, VBFA, LIKP and LIPS also exist in S/4HANA. For a clean core approach, I_SalesDocumentScheduleLine and the delivery CDS views can be used.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-otif-delivery-performance
