On-Time In-Full (OTIF) Delivery Performance Report by Customer
Short answer: 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.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Sales managers, logistics and shipping planners, customer service and managers who track supply chain performance.
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 and requested delivery date in the header (driving table) | — | ECC + S/4 |
| VBAPSales Document Item | Material, plant, order quantity and reason for rejection | VBAP-VBELN = VBAK-VBELN | ECC + S/4 |
| VBEPSales Document: Schedule Line Data | Requested delivery date in the first schedule line | VBEP-VBELN = VBAP-VBELN AND VBEP-POSNR = VBAP-POSNR | ECC + S/4 |
| VBFASales Document Flow | Document flow from order item to delivery item | VBFA-VBELV = VBAP-VBELN AND VBFA-POSNV = VBAP-POSNR AND VBFA-VBTYP_N = 'J' | ECC + S/4 |
| LIPSDelivery Item Data | Delivered quantity | LIPS-VBELN = VBFA-VBELN AND LIPS-POSNR = VBFA-POSNN | ECC + S/4 |
| LIKPDelivery Header | Actual goods issue date | LIKP-VBELN = LIPS-VBELN | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
| I_SalesDocumentScheduleLineSales Document Schedule Line | In S/4HANA it can replace VBEP with a clean core approach | SalesDocument = VBAK-VBELN | S/4HANA only |
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_KUNNR | Sold-to party | Range / multiple | VBAK-KUNNR | No | 200145 |
| S_VDATU | Requested delivery date range | Range / multiple | VBAK-VDATU | Yes | 01.10.2026 – 31.10.2026 |
| S_WERKS | Plant | Range / multiple | VBAP-WERKS | No | 1000 |
| P_TOLD | On-time tolerance (days) | Single value | — | No | 1 |
| P_TOLQ | In-full tolerance (%) | Single value | — | No | 2 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Sales order | VBAK-VBELN |
| 2 | Item | VBAP-POSNR |
| 3 | Sold-to | VBAK-KUNNR |
| 4 | Customer name | KNA1-NAME1 |
| 5 | Material | VBAP-MATNR |
| 6 | Order qty | VBAP-KWMENG |
| 7 | Delivered qty | Calculated Sum of LIPS-LFIMG over the linked delivery items |
| 8 | Unit | VBAP-VRKME |
| 9 | Requested date | VBEP-EDATU |
| 10 | Actual goods issue | LIKP-WADAT_IST |
| 11 | Days late | Calculated Last LIKP-WADAT_IST − VBEP-EDATU (negative: early) |
| 12 | On time | Calculated X when days late ≤ day tolerance |
| 13 | In full | Calculated X when delivered ≥ VBAP-KWMENG × (1 − quantity tolerance) |
| 14 | OTIF | Calculated X when both On time and In full are X |
Sample output
| Sales order | Item | Sold-to | Customer name | Material | Order qty | Delivered qty | Unit | Requested date | Actual goods issue | Days late | On time | In full | OTIF |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0000123401 | 000010 | 200145 | Marmara Yapı Market | FG-1001 | 500 | 500 | PC | 10/06/2026 | 10/05/2026 | -1 | X | X | X |
| 0000123401 | 000020 | 200145 | Marmara Yapı Market | FG-1002 | 300 | 240 | PC | 10/06/2026 | 10/06/2026 | 0 | X | ||
| 0000123455 | 000010 | 200310 | Kuzey Gıda Dağıtım | FG-2050 | 1,200 | 1,200 | KG | 10/12/2026 | 10/16/2026 | 4 | X | ||
| 0000123498 | 000010 | 200422 | Anadolu Elektrik Toptan | FG-3110 | 80 | 80 | PC | 10/20/2026 | 10/20/2026 | 0 | X | X | X |
How does the report work?
- 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.
- 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.
- 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.
- On time = last goods issue date ≤ requested date + day tolerance. In full = delivered quantity ≥ VBAP-KWMENG × (1 − quantity tolerance %). OTIF = both.
- The result is shown in ALV at item level; subtotals per customer and plant calculate on-time %, in-full % and OTIF %.
Performance notes
Narrow the VBAK selection by sales organization and requested delivery date range. Read VBFA once with FOR ALL ENTRIES on the item key. For monthly OTIF, run the report as a background job at month end and keep the result.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the order number opens VA03; clicking a delivery opens VL03N.
- Export to Excel
- Runs as a background job
- Send the result by email At month end each sales manager can receive the OTIF summary of their own customers.
Authorization objects
- V_VBAK_VKOSales document display authorization by sales area
- V_VBAK_AATAuthorization by sales document type
- V_LIKP_VSTDelivery 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.
Packages that include this solution
Order Fulfilment and Backorder Pack
A three-component pack that tracks every day whether customer orders are delivered on time and in full: unconfirmed and backordered order items, a …
Related reports
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 …
Picked but Not Goods-Issued Deliveries Report
A custom ALV report that lists deliveries whose picking is complete but whose goods issue has not been posted, with the number of days they have been …
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.