SD Report Custom development ALV report

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

  • VA05 List of Sales Orders. Lists orders and the first schedule-line date; no comparison with the actual goods issue date and no OTIF percentage.
  • VL06O Outbound Delivery Monitor. Tracks deliveries and goods issue status; does not compare them with the requested date and order quantity.

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 and requested delivery date in the header (driving table)—ECC + S/4
VBAPSales Document ItemMaterial, plant, order quantity and reason for rejectionVBAP-VBELN = VBAK-VBELNECC + S/4
VBEPSales Document: Schedule Line DataRequested delivery date in the first schedule lineVBEP-VBELN = VBAP-VBELN AND VBEP-POSNR = VBAP-POSNRECC + S/4
VBFASales Document FlowDocument flow from order item to delivery itemVBFA-VBELV = VBAP-VBELN AND VBFA-POSNV = VBAP-POSNR AND VBFA-VBTYP_N = 'J'ECC + S/4
LIPSDelivery Item DataDelivered quantityLIPS-VBELN = VBFA-VBELN AND LIPS-POSNR = VBFA-POSNNECC + S/4
LIKPDelivery HeaderActual goods issue dateLIKP-VBELN = LIPS-VBELNECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = VBAK-KUNNRECC + S/4
I_SalesDocumentScheduleLineSales Document Schedule LineIn S/4HANA it can replace VBEP with a clean core approachSalesDocument = VBAK-VBELNS/4HANA only

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_VKORGSales organizationRange / multipleVBAK-VKORGYes1000
S_VTWEGDistribution channelRange / multipleVBAK-VTWEGNo10
S_AUARTOrder typeRange / multipleVBAK-AUARTNoTA
S_KUNNRSold-to partyRange / multipleVBAK-KUNNRNo200145
S_VDATURequested delivery date rangeRange / multipleVBAK-VDATUYes01.10.2026 – 31.10.2026
S_WERKSPlantRange / multipleVBAP-WERKSNo1000
P_TOLDOn-time tolerance (days)Single value—No1
P_TOLQIn-full tolerance (%)Single value—No2

Output columns

#ColumnSource
1Sales orderVBAK-VBELN
2ItemVBAP-POSNR
3Sold-toVBAK-KUNNR
4Customer nameKNA1-NAME1
5MaterialVBAP-MATNR
6Order qtyVBAP-KWMENG
7Delivered qtyCalculated Sum of LIPS-LFIMG over the linked delivery items
8UnitVBAP-VRKME
9Requested dateVBEP-EDATU
10Actual goods issueLIKP-WADAT_IST
11Days lateCalculated Last LIKP-WADAT_IST − VBEP-EDATU (negative: early)
12On timeCalculated X when days late ≤ day tolerance
13In fullCalculated X when delivered ≥ VBAP-KWMENG × (1 − quantity tolerance)
14OTIFCalculated X when both On time and In full are X

Sample output

Sales orderItemSold-toCustomer nameMaterialOrder qtyDelivered qtyUnitRequested dateActual goods issueDays lateOn timeIn fullOTIF
0000123401000010200145Marmara Yapı MarketFG-1001500500PC10/06/202610/05/2026-1XXX
0000123401000020200145Marmara Yapı MarketFG-1002300240PC10/06/202610/06/20260X
0000123455000010200310Kuzey Gıda DağıtımFG-20501,2001,200KG10/12/202610/16/20264X
0000123498000010200422Anadolu Elektrik ToptanFG-31108080PC10/20/202610/20/20260XXX
A view built with fictional sample data; not real system data.

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

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

SD Package Custom

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 …

3 components · v1.0

Related reports

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

SD Report Custom ALV report

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 …

LIKP · VBUK · LIPS · KNA1

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: On-Time In-Full (OTIF) Delivery Performance Report by Customer