# Vehicle Loading and Shipment Planning Program (Domestic and Export)

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

- Type: Program, Custom development, Background program
- Module: SD
- Estimated effort: L (12–18 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/vehicle-loading-and-shipment-planning-program/


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

### Closest standard alternatives

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

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LIKP | Deliveries ready for shipping: route, ship-to, weight, volume, planned goods issue date | Read | - | ECC + S/4 |
| LIPS | Delivery items: material and quantity (for the pallet calculation) | Read | LIPS-VBELN = LIKP-VBELN | ECC + S/4 |
| VEKP | Pallet and carton count of packed deliveries | Read | VEKP-VPOBJKEY = LIKP-VBELN | ECC + S/4 |
| MARM | Conversion factor of the material to the pallet unit | Read | MARM-MATNR = LIPS-MATNR | ECC + S/4 |
| KNA1 | Ship-to country and city (export split and sequencing) | Read | KNA1-KUNNR = LIKP-KUNNR | ECC + S/4 |
| TVRO | Route and transit time | Read | TVRO-ROUTE = LIKP-ROUTE | ECC + S/4 |
| VTTK | Shipment header created: carrier, plate, planned loading date | Write | - | ECC + S/4 |
| VTTP | Shipment items: delivery and loading sequence; check for unassigned deliveries | Read / write | VTTP-VBELN = LIKP-VBELN | ECC + S/4 |

## BAPIs and functions used

- BAPI_SHIPMENT_CREATE: Creates the shipment document for each approved load
- BAPI_SHIPMENT_CHANGE: Updates the planning status and vehicle data
- BAPI_TRANSACTION_COMMIT: Commits each load separately

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VSTEL | Shipping point | Range / multiple | LIKP-VSTEL | Yes |
| S_WADAT | Planned goods issue date | Range / multiple | LIKP-WADAT | Yes |
| S_ROUTE | Route | Range / multiple | LIKP-ROUTE | No |
| P_TPLST | Transportation planning point | Single value | VTTK-TPLST | Yes |
| P_SHTYP | Shipment type | Single value | VTTK-SHTYP | Yes |
| P_EXPORT | Plan export deliveries in separate loads | Checkbox | - | No |
| P_TEST | Proposal only (do not create shipments) | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| Load | Calculated: Load number in the proposal |
| Vehicle type | Calculated: Vehicle or container type chosen from the parameter table |
| Route | LIKP-ROUTE |
| Deliveries | Calculated: Number of deliveries assigned to the load |
| Weight (kg) | Calculated: Σ LIKP-BTGEW |
| Weight utilization % | Calculated: Σ LIKP-BTGEW / vehicle maximum weight × 100 |
| Volume utilization % | Calculated: Σ LIKP-VOLUM / vehicle volume × 100 |
| Pallets | Calculated: VEKP pallet count or LIPS quantity / MARM pallet factor |
| Shipment | VTTK-TKNUM |
| Planned loading | VTTK-DPLBG |
| Status | Calculated: Proposed, created or staging |

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

## Authorization objects

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

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