285123
285123 - JC - 8D4DME/ Internal charge for Radial Delivery
Copyright OBS Logistics © 2010
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
Change Request Summary:
Internal charging for radial deliveries for Cross Docked orders to calculate regardless of the Carrier applied to the trunk trip. Stuart Foster/Milton Keynes/UK/NFC
Change Request Details:
Need internal charges to generate for Cross Docked orders as with current functionality but regardless of the carrier applied to the trunk trip. EG Order from EXELBAWT - ASDACHEP is cross docked through SWCONSOL, currently if the Carrier is set to either MTS Carrier or Fleet the internal charging is calculated for radial delivery. Need has been identified for the radial rate calculation functionality to still calculate if the Carrier for the trunk trip has a type of Haulier.
Benefits identified as a result of the change:
Requirement of Revised Consol Centre processes
Solution
Currently when looking for internal charging details, the system checks that the carrier assigned to the trunk trip is of carrier type ‘FLEET’, this check will be removed.
To determine who is being charged for the trunk trip, the system identifies the group name of the loading location and to determine who is receiving the revenue for the trunk leg, the system identifies the group name of the hub location of the carrier.
If the group name of the carrier hub location = the group name of the load_location then no trunk charges are created, this will amended so that in addition, if the GROUP NAME of the carrier hub location is null, no trunk charges will be generated.
If TRUNK charges have been allocated, the hub location of the carrier is used to also allocate the RADIAL charges. If trunk charges have not been allocated, the unload location is used to allocate the radial charges.
We will amend the sql so that the system still looks for the hub location based on an outer join. This means that sub contracted trunk legs will still be included in the data. We will use the unload location (like currently used for own fleet trunk trips) to allocate the radial payments.
This means that the orders must always be cross docked to locations that have been assigned a group name. If there is not group name assigned at the unload location, no radial charges will be generated.
FUNCTIONAL DESCRIPTION
EXAMPLE
ORDER 123 is travelling from EXELBAWT to A customer site in London.
Order 123 is cross docked at EXELBELL, using a sub contractor YOUNG BROTHERS.
As YOUNG BROTHERS is not a fleet carrier , the group name of the hub location is NULL
Trunk charges would be generated between EXELBAWT and NULL resulting in no trunk charges.
Radial charges will be generated between the Load and unload GROUP NAMES EXELBAWT and EXELBELL.
REFERENCES
| EST-285123 JC - 8D4DME/ Internal charge for Radial Delivery.doc |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
