SD Program Custom development Background program

Vehicle Loading and Shipment Planning Program (Domestic and Export)

Short answer: A custom planning program that groups deliveries ready for shipping by route and destination and proposes loads based on the weight, volume and pallet capacity of each vehicle type. The planner adjusts the proposal on screen, shipment documents are created automatically for approved loads, and deliveries that do not fit on a vehicle on the planned date are listed separately as staging (interim storage) demand.

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

Why is the standard not enough?

VT04 and VT01N create shipments from deliveries, but they do not calculate utilization per vehicle type or propose loads; the planner decides manually which delivery goes on which vehicle. How much staging space is needed for goods that are ready but have no vehicle is not visible in standard screens either. Transportation management products do this but need a separate licence and implementation. The custom program closes the gap using the existing shipment document.

Who uses it? Shipment planners, logistics and warehouse managers, export operations teams.

Closest standard alternatives

  • VT04 Transportation Worklist. Creates shipments collectively with a selection variant; no capacity-based load proposal or utilization calculation.
  • VT01N Create Shipment. Creates shipments one at a time; deliveries are chosen manually by the planner.

Tables used

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

TableRoleAccessSystem
LIKPDelivery HeaderDeliveries ready for shipping: route, ship-to, weight, volume, planned goods issue dateReadECC + S/4
LIPSDelivery Item DataDelivery items: material and quantity (for the pallet calculation)ReadECC + S/4
VEKPHandling Unit HeaderPallet and carton count of packed deliveriesReadECC + S/4
MARMUnits of Measure for MaterialConversion factor of the material to the pallet unitReadECC + S/4
KNA1Customer Master (General Section)Ship-to country and city (export split and sequencing)ReadECC + S/4
TVRORoutesRoute and transit timeReadECC + S/4
VTTKShipment HeaderShipment header created: carrier, plate, planned loading dateWriteECC + S/4
VTTPShipment ItemShipment items: delivery and loading sequence; check for unassigned deliveriesRead / writeECC + S/4

BAPIs and functions used

  • BAPI_SHIPMENT_CREATECreate Shipment. Creates the shipment document for each approved load
  • BAPI_SHIPMENT_CHANGEChange Shipment. Updates the planning status and vehicle data
  • BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Commits each load separately

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_VSTELShipping pointRange / multipleLIKP-VSTELYes1000
S_WADATPlanned goods issue dateRange / multipleLIKP-WADATYes18.11.2026 – 19.11.2026
S_ROUTERouteRange / multipleLIKP-ROUTENoR-IZM
P_TPLSTTransportation planning pointSingle valueVTTK-TPLSTYes1000
P_SHTYPShipment typeSingle valueVTTK-SHTYPYes0001
P_EXPORTPlan export deliveries in separate loadsCheckbox—NoX
P_TESTProposal only (do not create shipments)Checkbox—NoX

Result list columns

#ColumnSource
1LoadCalculated Load number in the proposal
2Vehicle typeCalculated Vehicle or container type chosen from the parameter table
3RouteLIKP-ROUTE
4DeliveriesCalculated Number of deliveries assigned to the load
5Weight (kg)Calculated Σ LIKP-BTGEW
6Weight utilization %Calculated Σ LIKP-BTGEW / vehicle maximum weight × 100
7Volume utilization %Calculated Σ LIKP-VOLUM / vehicle volume × 100
8PalletsCalculated VEKP pallet count or LIPS quantity / MARM pallet factor
9ShipmentVTTK-TKNUM
10Planned loadingVTTK-DPLBG
11StatusCalculated Proposed, created or staging

Sample result list

LoadVehicle typeRouteDeliveriesWeight (kg)Weight utilization %Volume utilization %PalletsShipmentPlanned loadingStatus
1Truck 13.6 mR-IZM621,8509184.5032100000452111/18/2026Created
2Lorry 7.5 tR-ANK46,12081.607712100000452211/18/2026Created
3Container 40'R-EXP-MRS318,40069.7092.302211/19/2026Proposed
4R-IZM23,9007Staging
A view built with fictional sample data; not real system data.

How does the program work?

  1. LIKP/LIPS are read by shipping point, planned goods issue date and route; deliveries without goods issue that are not yet assigned to a shipment (no record in VTTP) enter planning.
  2. Weight and volume of each delivery come from LIKP-BTGEW and LIKP-VOLUM. The pallet count comes from packing (VEKP) if available, otherwise from the material’s pallet unit conversion (MARM).
  3. Vehicle types and their capacities (maximum weight, volume, pallets, and container types for export) are read from a parameter table defined during installation. Deliveries are grouped by route and ship-to sequence, sorted from largest to smallest and placed on vehicles without exceeding capacity. Export deliveries (recipient country differs from the company country) are planned in separate loads.
  4. The planner sees the load proposals in an ALV, moves deliveries between loads, changes the vehicle type or postpones a load to the next day. Utilization percentages are recalculated after every change.
  5. For each approved load a shipment document (VTTK/VTTP) is created with BAPI_SHIPMENT_CREATE; carrier, vehicle plate and planned loading date are written to the header, and the planning status is set to complete with BAPI_SHIPMENT_CHANGE.
  6. Deliveries that fit on no vehicle on the planned date, or that are past their goods issue date and still not loaded, go to the staging demand list, which shows total pallets and weight per shipping point and day. The program also runs in the background as a nightly proposal job.

Performance notes

Read VTTP once with the delivery numbers to find unassigned deliveries; avoid a SELECT per delivery. Buffer MARM conversions per material. Create shipments with one BAPI call and COMMIT per load, so that one failing load does not stop the others.

Features

  • ALV list (sort, filter, subtotals)
  • Test mode (check without posting) The proposal can be reviewed and changed without creating shipments.
  • Runs as a background job A nightly proposal job brings ready loads to the planner in the morning.
  • Line-by-line result and error log
  • Export to Excel

Authorization objects

  • V_VTTK_TDSShipment creation authorization by transportation planning point
  • V_LIKP_VSTDelivery display authorization by shipping point

Frequently asked questions

Where are the vehicle capacities kept?

Vehicle and container types are kept with maximum weight, volume and pallet count in a small parameter table created during installation and maintained by the logistics team. Your own fleet and hired vehicles can be defined as separate types.

How is the staging demand calculated?

The pallet and weight totals of deliveries that fit on no load for the planned day, or that are past their goods issue date and still not loaded, are listed per shipping point and day. The warehouse sees in advance how much temporary space it will need on which day.

Does it work on S/4HANA?

Yes. The program uses the classic shipment document (VTTK/VTTP), which is still available in S/4HANA. If a move to transportation management is planned, the same capacity rules can be carried over.

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: Vehicle Loading and Shipment Planning Program (Domestic and Export)