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
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| VTTKShipment Header | Shipment header: plate, carrier, planned loading, overall status (driving table) | Read | ECC + S/4 |
| VTTPShipment Item | Deliveries in the shipment and loading sequence | Read | ECC + S/4 |
| LIKPDelivery Header | Delivery header: ship-to, weight, goods issue date | Read | ECC + S/4 |
| LIPSDelivery Item Data | Delivery items: material, storage location, batch, quantity | Read | ECC + S/4 |
| VBSKCollective Processing for a Sales Document Header | Delivery group header when no shipment document is used | Read | ECC + S/4 |
| VBSSCollective Processing: Sales Documents | Deliveries in the delivery group | Read | ECC + S/4 |
| LFA1Vendor Master (General Section) | Carrier name | Read | ECC + S/4 |
| KNA1Customer Master (General Section) | Ship-to name | Read | ECC + S/4 |
| NASTMessage Status | Print status of the dispatch order | Read | ECC + 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
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_TPLST | Transportation planning point | Range / multiple | VTTK-TPLST | Yes | 1000 |
| S_TKNUM | Shipment | Range / multiple | VTTK-TKNUM | No | 1000004521 |
| S_DPLBG | Planned loading date | Range / multiple | VTTK-DPLBG | Yes | 18.11.2026 |
| S_VSTEL | Shipping point | Range / multiple | LIKP-VSTEL | No | 1000 |
| R_FORM | Print the dispatch order form | Radio button | — | No | — |
| R_LIST | Show the tracking report | Radio button | — | No | X |
| P_REPRT | Reprint orders already printed | Checkbox | — | No | — |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Dispatch order (shipment) | VTTK-TKNUM |
| 2 | Plate | VTTK-SIGNI |
| 3 | Carrier | LFA1-NAME1 |
| 4 | Planned loading | VTTK-DPLBG |
| 5 | Deliveries | Calculated Number of VTTP records |
| 6 | Total weight (kg) | Calculated Σ LIKP-BTGEW |
| 7 | Printed | Calculated Yes if NAST-VSTAT = 1 |
| 8 | Picking | Calculated All deliveries picked, partly or not started |
| 9 | Goods issue | Calculated Complete if LIKP-WADAT_IST is filled for all deliveries |
| 10 | Shipment status | VTTK-STTRG |
Sample result list
| Dispatch order (shipment) | Plate | Carrier | Planned loading | Deliveries | Total weight (kg) | Printed | Picking | Goods issue | Shipment status |
|---|---|---|---|---|---|---|---|---|---|
| 1000004521 | 34 ABC 128 | Örnek Nakliyat Ltd. Şti. | 11/18/2026 | 6 | 21,850 | Yes | Complete | Complete | 7 |
| 1000004522 | 34 ABD 455 | Örnek Nakliyat Ltd. Şti. | 11/18/2026 | 4 | 6,120 | Yes | Partly | Pending | 4 |
| 1000004523 | 16 DMR 310 | Demo Lojistik A.Ş. | 11/18/2026 | 3 | 9,480 | No | Not started | Pending | 1 |
| 1000004524 | 35 EGE 774 | Demo Lojistik A.Ş. | 11/19/2026 | 5 | 14,260 | Yes | Not started | Pending | 2 |
How does the program work?
- 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.
- 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.
- Shipment and delivery numbers are printed as barcodes to be scanned at the gate. Delivery notes are added with READ_TEXT.
- 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.
- 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
Mass Post Goods Issue from a Warehouse Confirmation File Program
A custom program that reads the picking confirmation file from an external warehouse or warehouse system, writes the picked quantity and batch to the …
Overnight Outbound Delivery Creation Job for Due Sales Orders with Exception List
A custom background program that creates outbound deliveries every night for confirmed sales order items whose material availability date has come, …
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 program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.