# Dispatch Order Form and Dispatch Order Tracking Report

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

- Type: Program, Custom development, Form
- Module: SD
- Estimated effort: M (5–8 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/dispatch-order-form-and-tracking-report/


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

### Closest standard alternatives

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

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VTTK | Shipment header: plate, carrier, planned loading, overall status (driving table) | Read | - | ECC + S/4 |
| VTTP | Deliveries in the shipment and loading sequence | Read | VTTP-TKNUM = VTTK-TKNUM | ECC + S/4 |
| LIKP | Delivery header: ship-to, weight, goods issue date | Read | LIKP-VBELN = VTTP-VBELN | ECC + S/4 |
| LIPS | Delivery items: material, storage location, batch, quantity | Read | LIPS-VBELN = LIKP-VBELN | ECC + S/4 |
| VBSK | Delivery group header when no shipment document is used | Read | - | ECC + S/4 |
| VBSS | Deliveries in the delivery group | Read | VBSS-SAMMG = VBSK-SAMMG | ECC + S/4 |
| LFA1 | Carrier name | Read | LFA1-LIFNR = VTTK-TDLNR | ECC + S/4 |
| KNA1 | Ship-to name | Read | KNA1-KUNNR = LIKP-KUNNR | ECC + S/4 |
| NAST | Print status of the dispatch order | Read | NAST-OBJKY = VTTK-TKNUM | ECC + S/4 |

## BAPIs and functions used

- SSF_FUNCTION_MODULE_NAME: Finds the form function when Smart Forms is used
- FP_FUNCTION_MODULE_NAME: Finds the form interface when Adobe Forms is used
- READ_TEXT: Reads delivery and shipment notes
- SO_NEW_DOCUMENT_ATT_SEND_API1: Sends the dispatch order to the carrier as PDF

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_TPLST | Transportation planning point | Range / multiple | VTTK-TPLST | Yes |
| S_TKNUM | Shipment | Range / multiple | VTTK-TKNUM | No |
| S_DPLBG | Planned loading date | Range / multiple | VTTK-DPLBG | Yes |
| S_VSTEL | Shipping point | Range / multiple | LIKP-VSTEL | No |
| R_FORM | Print the dispatch order form | Radio button | - | No |
| R_LIST | Show the tracking report | Radio button | - | No |
| P_REPRT | Reprint orders already printed | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| Dispatch order (shipment) | VTTK-TKNUM |
| Plate | VTTK-SIGNI |
| Carrier | LFA1-NAME1 |
| Planned loading | VTTK-DPLBG |
| Deliveries | Calculated: Number of VTTP records |
| Total weight (kg) | Calculated: Σ LIKP-BTGEW |
| Printed | Calculated: Yes if NAST-VSTAT = 1 |
| Picking | Calculated: All deliveries picked, partly or not started |
| Goods issue | Calculated: Complete if LIKP-WADAT_IST is filled for all deliveries |
| Shipment status | VTTK-STTRG |

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

## Authorization objects

- V_VTTK_TDS: Shipment display and output authorization by transportation planning point
- V_LIKP_VST: Delivery 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.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=sd-dispatch-order
