SD Program Custom development Form

Dispatch Order Form and Dispatch Order Tracking Report

Short answer: A dispatch order form that tells the warehouse which orders are loaded on which vehicle, with which driver and in which sequence, plus a report that tracks the printing, picking, loading and goods issue status of these orders. The form is prepared per vehicle, showing storage location, batch, quantity and weight on one page.

Estimated effort
M · 5–8 working days
System
ECC and S/4HANA
Tables
9
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

The standard picking list is printed per delivery and does not contain vehicle, driver or loading sequence. Although shipment output (VT70) exists, it does not provide the warehouse with an item-level loading order. Which dispatch orders were printed, picked and loaded cannot be followed in one list either. The custom solution prints the order per vehicle and shows its status on the same screen.

Who uses it? Shipment planners, warehouse supervisors and loading teams, logistics managers.

Closest standard alternatives

  • VT70 Output for Shipments. Processes shipment output in bulk; no item-level loading order for the warehouse and no tracking list.
  • VL06O Outbound Delivery Monitor. Lists deliveries by picking and goods issue status; does not group them by vehicle.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
VTTKShipment HeaderShipment header: plate, carrier, planned loading, overall status (driving table)ReadECC + S/4
VTTPShipment ItemDeliveries in the shipment and loading sequenceReadECC + S/4
LIKPDelivery HeaderDelivery header: ship-to, weight, goods issue dateReadECC + S/4
LIPSDelivery Item DataDelivery items: material, storage location, batch, quantityReadECC + S/4
VBSKCollective Processing for a Sales Document HeaderDelivery group header when no shipment document is usedReadECC + S/4
VBSSCollective Processing: Sales DocumentsDeliveries in the delivery groupReadECC + S/4
LFA1Vendor Master (General Section)Carrier nameReadECC + S/4
KNA1Customer Master (General Section)Ship-to nameReadECC + S/4
NASTMessage StatusPrint status of the dispatch orderReadECC + S/4

BAPIs and functions used

  • SSF_FUNCTION_MODULE_NAMEGet Smart Form Function Module Name. Finds the form function when Smart Forms is used
  • FP_FUNCTION_MODULE_NAMEGet Adobe Form Function Module Name. Finds the form interface when Adobe Forms is used
  • READ_TEXTRead Long Text. Reads delivery and shipment notes
  • SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends the dispatch order to the carrier as PDF

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_TPLSTTransportation planning pointRange / multipleVTTK-TPLSTYes1000
S_TKNUMShipmentRange / multipleVTTK-TKNUMNo1000004521
S_DPLBGPlanned loading dateRange / multipleVTTK-DPLBGYes18.11.2026
S_VSTELShipping pointRange / multipleLIKP-VSTELNo1000
R_FORMPrint the dispatch order formRadio button—No—
R_LISTShow the tracking reportRadio button—NoX
P_REPRTReprint orders already printedCheckbox—No—

Result list columns

#ColumnSource
1Dispatch order (shipment)VTTK-TKNUM
2PlateVTTK-SIGNI
3CarrierLFA1-NAME1
4Planned loadingVTTK-DPLBG
5DeliveriesCalculated Number of VTTP records
6Total weight (kg)Calculated Σ LIKP-BTGEW
7PrintedCalculated Yes if NAST-VSTAT = 1
8PickingCalculated All deliveries picked, partly or not started
9Goods issueCalculated Complete if LIKP-WADAT_IST is filled for all deliveries
10Shipment statusVTTK-STTRG

Sample result list

Dispatch order (shipment)PlateCarrierPlanned loadingDeliveriesTotal weight (kg)PrintedPickingGoods issueShipment status
100000452134 ABC 128Örnek Nakliyat Ltd. Şti.11/18/2026621,850YesCompleteComplete7
100000452234 ABD 455Örnek Nakliyat Ltd. Şti.11/18/202646,120YesPartlyPending4
100000452316 DMR 310Demo Lojistik A.Ş.11/18/202639,480NoNot startedPending1
100000452435 EGE 774Demo Lojistik A.Ş.11/19/2026514,260YesNot startedPending2
A view built with fictional sample data; not real system data.

How does the program work?

  1. The dispatch order unit is the shipment document (VTTK/VTTP); if shipment documents are not used, the collective processing delivery group (VBSK/VBSS) is used instead.
  2. The form header shows vehicle plate, driver, carrier (VTTK-TDLNR → LFA1) and planned loading date and time. Deliveries are listed in loading sequence (VTTP-TPRFO); for each delivery the ship-to and address are printed, and for each item material, storage location, batch, quantity and weight.
  3. Shipment and delivery numbers are printed as barcodes to be scanned at the gate. Delivery notes are added with READ_TEXT.
  4. The form is defined as shipment output in NACE; when the shipment reaches the planning status it is printed on the warehouse printer and, if needed, sent to the carrier as PDF.
  5. The tracking report shows for each dispatch order printing (NAST), picking (delivery picking status), goods issue (LIKP-WADAT_IST) and the overall shipment status (VTTK-STTRG); late orders are highlighted in colour.

Performance notes

Read shipment items and deliveries once with the shipment numbers. In the tracking report, take picking and goods issue status in bulk from LIKP and the status fields instead of reading per delivery; in S/4HANA the statuses sit directly in the delivery tables.

Features

  • ALV list (sort, filter, subtotals)
  • Double-click drill-down to the document Double-clicking the shipment opens VT03N; clicking a delivery opens VL03N.
  • Send the result by email The dispatch order can be sent to the carrier as PDF.
  • Runs as a background job

Authorization objects

  • V_VTTK_TDSShipment display and output authorization by transportation planning point
  • V_LIKP_VSTDelivery display authorization by shipping point

Frequently asked questions

We do not use shipment documents; can the dispatch order still be printed?

Yes. In that case the delivery group created in collective processing becomes the dispatch order unit; vehicle plate and driver are entered in the group header or a small entry screen.

Where does the driver information come from?

The driver is read from the shipment's partner roles or the shipment header text. If personnel numbers are used for your own fleet, the driver's name is printed from the personnel master.

Is barcode scanning at the warehouse gate supported?

The form prints the shipment and delivery numbers as barcodes. Scanning the barcode and confirming the loading can be added as an extra development with a mobile screen.

Related reports

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 program 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: Dispatch Order Form and Dispatch Order Tracking Report