# Vehicle Request Cockpit and Unsupplied Vehicle Report

> A custom cockpit that derives vehicle demand from deliveries ready for shipping, sends vehicle requests to logistics companies with vehicle type, date and route, and tracks through the shipment document whether each request was fulfilled. Vehicles that arrive late or are never supplied are reported per logistics company, so carrier performance can be measured.

- Type: Program, Custom development, Fiori app
- Module: SD
- Estimated effort: M (12–18 working days)
- Last updated: 2026-11-18
- URL: https://nekuhub.com/en/programs/vehicle-request-cockpit-and-unsupplied-vehicles/


## Why is the standard not enough?

The standard shipment document (VT01N) holds the carrier and the planned and actual check-in dates, but it does not record when a vehicle was requested, from which company, for which vehicle type, or whether the company accepted the request. VT11 lists shipments but does not calculate the share of requested vehicles that never came or arrived late per company. When requests run over phone and email, delays cannot be measured and carriers cannot be evaluated.

### Closest standard alternatives

- VT01N: Creates the shipment and holds the carrier; does not record the vehicle request, the company's reply or an unsupplied vehicle.
- VT11: Lists shipments; does not give on-time, late and unsupplied vehicle shares per company.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LIKP | Deliveries ready for shipping: route, planned goods issue date, weight | Read | - | ECC + S/4 |
| VTTP | Shipment items: deliveries assigned to the shipment | Read | VTTP-VBELN = LIKP-VBELN | ECC + S/4 |
| VTTK | Shipment header: carrier, plate, planned and actual check-in (written) | Read / write | VTTK-TKNUM = VTTP-TKNUM | ECC + S/4 |
| LFA1 | Logistics company name and address number | Read | LFA1-LIFNR = VTTK-TDLNR | ECC + S/4 |
| ADR6 | Request email address of the logistics company | Read | ADR6-ADDRNUMBER = LFA1-ADRNR | ECC + S/4 |
| TVRO | Route definition and transit time | Read | TVRO-ROUTE = LIKP-ROUTE | ECC + S/4 |

## BAPIs and functions used

- BAPI_SHIPMENT_CREATE: Creates a shipment for an accepted request
- BAPI_SHIPMENT_CHANGE: Writes carrier, plate and planned and actual check-in time
- BAPI_TRANSACTION_COMMIT: Commits the shipment changes
- SO_NEW_DOCUMENT_ATT_SEND_API1: Sends the vehicle request to the logistics company by email

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_TPLST | Transportation planning point | Range / multiple | VTTK-TPLST | Yes |
| S_DPREG | Planned check-in date | Range / multiple | VTTK-DPREG | Yes |
| S_TDLNR | Logistics company | Range / multiple | VTTK-TDLNR | No |
| S_ROUTE | Route | Range / multiple | LIKP-ROUTE | No |
| P_TOL | Delay tolerance (hours) | Single value | - | No |
| P_VIEW | View: requests / company performance | Radio button | - | No |

## Result list columns

| Column | Source |
|---|---|
| Request | Calculated: Vehicle request number created in the cockpit |
| Requested loading | Calculated: Date and time on the request |
| Vehicle type | Calculated: Vehicle type chosen on the request |
| Route | VTTK-ROUTE |
| Logistics company | VTTK-TDLNR |
| Company name | LFA1-NAME1 |
| Shipment | VTTK-TKNUM |
| Plate | VTTK-SIGNI |
| Actual check-in | VTTK-DAREG |
| Delay (hours) | Calculated: Actual check-in time − requested loading time |
| Status | Calculated: Sent, accepted, rejected, on time, late or not supplied |

## How does the program work?

1. For a transportation planning point and date range, the cockpit reads deliveries ready for shipping (LIKP: planned goods issue date, route, gross weight) and the shipment documents linked to them (VTTK/VTTP).
2. The planner groups deliveries by route and date; a vehicle request is created by choosing a vehicle type (truck-trailer, truck, van, reefer), the requested loading date and time and the preferred logistics company. The request is written with its status and timestamps to a request table defined during installation.
3. The request email is sent to the logistics company with SO_NEW_DOCUMENT_ATT_SEND_API1; the company's email address comes from the vendor master (LFA1 address number). The planner enters the company's reply (accepted with plate and driver, or rejected) in the cockpit; a rejected request is passed to another company with one click.
4. For an accepted request a shipment is created with BAPI_SHIPMENT_CREATE, or the carrier (VTTK-TDLNR), plate (VTTK-SIGNI) and planned check-in date and time (VTTK-DPREG/UPREG) are written to the existing shipment with BAPI_SHIPMENT_CHANGE.
5. When the vehicle enters the site, the actual check-in (VTTK-DAREG/UAREG) is set in the shipment. The program compares the requested loading time with the actual check-in: within tolerance it counts as on time, beyond tolerance as late, and if there is still no check-in a set time after the requested date, as not supplied.
6. The report view shows per logistics company the number of requests, accepted, on-time, late and unsupplied vehicles with their shares and the average delay in hours; the user drills down from a line to the requests and shipments.
7. In S/4HANA the LE-TRA transportation component (VTTK/VTTP) can be used under the compatibility scope; the strategic transportation solution is SAP TM. The cockpit works with the same shipment tables in both releases.

## Authorization objects

- V_VTTK_TDS: Shipment authorization by transportation planning point
- V_VTTK_SHT: Shipment authorization by shipment type
- S_OC_SEND: Sending external email to the logistics company

## Frequently asked questions

### We do not use shipment documents; does the cockpit still work?

Yes. Requests, replies and delay tracking are kept in the cockpit's own request table, so it works without shipments; vehicle arrival is then marked in the cockpit. When shipments are used, plate and check-in time are written to the standard document and later steps such as freight costs continue from it.

### When does the status not supplied occur?

If the time set during installation (for example the end of the same shift) has passed after the requested loading time, there is no vehicle check-in and the request was not passed to another company, the request is closed as not supplied. A request passed to another company counts as not supplied for the first company and as a new request for the new one.

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