Datasheet
Release Notes - New Features included in Release 2.4.0
Page 24 of 89
(Pack an Order Line) data but otherwise will use the weight plus tare weight defined on PDMT
(Maintain Product Data). All weights are displayed in Kgs.
Sales order lines selected for possible inclusion into the shipment are sorted by despatch due date,
customer priority and delivery area so that the more urgent orders are displayed first and orders for
a region are grouped together. NB. customer priority is defined by the “Alloc priority” field on
CAMT (Maintain Customer Data).
It is also possible to remove sales order lines from a shipment, by entering the shipment number and
“Y”es to “Display Shipment”. The include flag will default to “Y” against each sales order line and
changing this to “N” will result in the removal of the sales order/line/delivery from the shipment.
When a shipment is complete, a PKDD (Request Despatch Documents) must to be executed to
produce the despatch documentation.
Please note that like PKCM (Multi-Customer Shipment) the LOAD (Lorry Loading) transaction can
only be used in sales environments where the “Method of Despatch” field is mandatory and where
consignments are not generated at selection.
4.2.3.13 Delivery Routes (SR4159)
This enhancement introduces delivery routes to TROPOS. This is a simple route planning tool.
Delivery routes can be defined and linked to delivery addresses, and delivery promise dates can be
calculated, based on the delivery routes. The major benefit of using this software is to provide more
accurate delivery promise dates. The best delivery route for a shipment can be calculated if an
address has more than one possible delivery route.
It is not currently integrated with the available to promise calculations automatically performed
when a sales order line is entered. It may be used, for example, by SDK development.
The software primarily consists of transactions to maintain definitions of delivery routes in terms of
drop numbers linking customer addresses to specific stages (‘day’) on one or more delivery routes,
and a program to calculate planned delivery dates based on the routes.
A delivery route consists of general information about the route and information for each ‘day’ or
stage. Each day has a range of drop numbers associated with it. A delivery route can have one or
more versions with different effective dates. Each version can have a different pattern of delivery
drops. There is only one header for the route which applies to all the versions. The base version of a
route (version 0) is used for delivery date calculations. Addresses are linked to routes by assigning a
drop number to an address. An address can be linked to more than one route, each with a different
drop number.
General information about a route (‘header’) is added with RTHM (Maintain Delivery Route). The
information consists of a description, a calendar identifier, a shift pattern and loading times. The
loading times, calendar and shift pattern are used in the delivery promise date calculations.
Information about each stage is added with RTDM (Route Delivery Pattern). An address is linked to
a route with NADR (Address Delivery Route).
A new version of a route is created by copying the delivery pattern of an existing version and
making any changes which may be required. The copy is done automatically by RTDM when a new
version is added.
Refer to the HELP text for transaction TS06 for information about the delivery date calculations.