SD Program Custom development Fiori app

Vehicle Request Cockpit and Unsupplied Vehicle Report

Short answer: 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.

Estimated effort
M · 12–18 working days
System
ECC and S/4HANA
Tables
6
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

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.

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

Closest standard alternatives

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

Tables used

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

TableRoleAccessSystem
LIKPDelivery HeaderDeliveries ready for shipping: route, planned goods issue date, weightReadECC + S/4
VTTPShipment ItemShipment items: deliveries assigned to the shipmentReadECC + S/4
VTTKShipment HeaderShipment header: carrier, plate, planned and actual check-in (written)Read / writeECC + S/4
LFA1Vendor Master (General Section)Logistics company name and address numberReadECC + S/4
ADR6E-Mail Addresses (Business Address Services)Request email address of the logistics companyReadECC + S/4
TVRORoutesRoute definition and transit timeReadECC + S/4

BAPIs and functions used

  • BAPI_SHIPMENT_CREATECreate Shipment. Creates a shipment for an accepted request
  • BAPI_SHIPMENT_CHANGEChange Shipment. Writes carrier, plate and planned and actual check-in time
  • BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Commits the shipment changes
  • SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends the vehicle request to the logistics company by email

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_TPLSTTransportation planning pointRange / multipleVTTK-TPLSTYes1000
S_DPREGPlanned check-in dateRange / multipleVTTK-DPREGYes01.11.2026 – 30.11.2026
S_TDLNRLogistics companyRange / multipleVTTK-TDLNRNo700120
S_ROUTERouteRange / multipleLIKP-ROUTENoTR0001
P_TOLDelay tolerance (hours)Single value—No2
P_VIEWView: requests / company performanceRadio button—NoTalepler

Result list columns

#ColumnSource
1RequestCalculated Vehicle request number created in the cockpit
2Requested loadingCalculated Date and time on the request
3Vehicle typeCalculated Vehicle type chosen on the request
4RouteVTTK-ROUTE
5Logistics companyVTTK-TDLNR
6Company nameLFA1-NAME1
7ShipmentVTTK-TKNUM
8PlateVTTK-SIGNI
9Actual check-inVTTK-DAREG
10Delay (hours)Calculated Actual check-in time − requested loading time
11StatusCalculated Sent, accepted, rejected, on time, late or not supplied

Sample result list

RequestRequested loadingVehicle typeRouteLogistics companyCompany nameShipmentPlateActual check-inDelay (hours)Status
AT-2026-041218.11.2026 08:00Truck-trailerTR0001700120Örnek Lojistik A.Ş.0001204534 ABC 12318.11.20260.50On time
AT-2026-041318.11.2026 10:00TruckTR0003700135Demo Nakliyat Ltd.0001204606 XYZ 45618.11.20264Late
AT-2026-041418.11.2026 13:00ReeferTR0002700120Örnek Lojistik A.Ş.Not supplied
AT-2026-041519.11.2026 07:30Truck-trailerTR0001700142Anadolu Taşımacılık A.Ş.0001205016 DEF 789Accepted
A view built with fictional sample data; not real system data.

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.

Performance notes

Restrict deliveries by transportation planning point and planned goods issue date; read VTTP and VTTK in one go for the delivery list. For the performance report read only requests of closed periods and aggregate per company in the database.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Send the result by email The vehicle request is emailed to the logistics company; if the company changes, a new request is sent automatically.
  • Double-click drill-down to the document From a company performance line the user drills down to requests and shipments.
  • Export to Excel
  • Line-by-line result and error log Every status change of a request is kept with user and time.

Authorization objects

  • V_VTTK_TDSShipment authorization by transportation planning point
  • V_VTTK_SHTShipment authorization by shipment type
  • S_OC_SENDSending 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.

Related reports

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: Vehicle Request Cockpit and Unsupplied Vehicle Report