Transport processing

Detailed workflow for creating, validating, and posting transports in daily shipping operations.

Purpose

This page explains how to combine posted shipment data into transport documents, validate them, and complete transport posting safely.

Standard BC setup context

A transport does not replace the shipping process. It consolidates already posted delivery documents into one operational handoff to a carrier or internal transport chain.

Transport sources in Controlled Sales Core are:

  • posted sales shipments
  • posted transfer shipments
  • posted warehouse shipments or shipment-derived lines
  • in exceptional cases, posted warehouse picks with a sales reference

Depending on the source, the transport process type is handled as Sales or Transfer. At consignment locations, a sales shipment can still be treated as transfer from a business perspective.

VDA4922 shipping order

Controlled Sales Core contains the Shipping Note VDA4922 report. In Business Central, start it through search or Reports and Analysis. Select Shipping Note VDA4922 and filter the relevant posted transport.

Before posting the shipment

Maintain and check the master data that will later be used by transport and report output:

  • customer, ship-to address, and unloading point,
  • location and shipping data,
  • shipping agent/carrier, and
  • item, packaging, and weight data.

These master-data values must exist before shipment posting so that the posted shipment and transport data are complete.

After posting and before printing

  1. Create or open the transport from the posted shipment context.
  2. Review transport number, delivery notes, transport lines, shipper, recipient, unloading points, and dates.
  3. Add vehicle, route, bordero, and shipping remarks where required.
  4. Review package and weight totals.
  5. Start Shipping Note VDA4922 through Reports and Analysis and filter the relevant transport.
  6. Review the preview and print the shipping order.

Automatic package data

When HUM and the HUM CSC connector are installed, package data for the report is transferred from posted HUM packages into the Loading Unit Print Buffer. The user does not maintain this buffer manually. Without available HUM packages, the report can only output the other transport data that is available.

For transports with several delivery notes, review unloading points per document. In 3PL/consignment scenarios, an unpopulated unloading point must not be a filter prerequisite. If output stops with an error concerning the loading-unit total, review transport lines, weights, and the 3PL/consignment reference.

Prerequisites

  • Shipments are posted and available for transport processing.
  • Transport number series is configured.
  • Shipping agent/carrier data is maintained.

Process map

graph LR;

%% Nodes
A("Select posted shipment")
B["Create transport"]
C["Check process type"]
D["Maintain carrier<br/>and dates"]
E["Check plausibility<br/>and weights"]
F["Post transport"]
G["Review posted<br/>transport"]

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E
E ==> F
F ==> G

%% Classes
class A btProcessTitle
class B,C,D,E,F,G btProcessActive

Flow

Process 1) Create transport Creates the transport header from shipment context.
  • Create transport from posted shipment context.
  • Verify number, carrier handoff date, and process type.
  • Confirm that relevant shipment links were transferred correctly.
Process 2) Complete transport details Ensures operational completeness before posting.
  • Maintain shipping agent, carrier handoff time, and delivery timing.
  • Add vehicle, route, and relevant shipment notes where needed.
  • Review weight totals and line assignment.
Process 3) Validate and post transport Final step of transport execution.
  • Ensure delivery date/time is not earlier than carrier handoff date/time.
  • Align exceptions with shipping and warehouse coordination.
  • Post only after all required data is complete.
Process 4) Use posted transport For traceability, audit, and controlled recovery scenarios.
  • Open posted transport for review and traceability.
  • Use attachments and lines for internal/external clarification.
  • In exceptional cases, posted transport can be restored to open transport.

Typical Error Patterns

Process Delivery date before handoff date Date/time plausibility issue during data entry.
  • Cause: invalid temporal sequence.
  • Fix: correct date/time values and validate again.
Process Duplicate transport reference Shipment data is already linked to another transport.
  • Cause: attempt to create transport twice for same shipment context.
  • Fix: review existing transport instead of creating a new one.

Operational fit with BC standard scenarios

  • For sales with warehouse shipment, the transport is usually created after the warehouse shipment has been posted.
  • For sales with pick, the transport comes after pick and shipment completion.
  • For transfer orders, the transport is relevant when the delivery chain must be documented or handed off to a carrier separately.
  • For direct posting without warehouse steps, the transport is optional and mainly used for logistics documentation.

Links

Further Information

Related processes