291782
DHL C-TMS
Add Net Cost to DESP2
FUNCTIONAL SPECIFICATION - 10.7
14/09/2011 - 1.0
Reference: FS 291782 BS-8LFGGC
Functional Overview
Client Requirement
Change Request Summary:
Due to a change in the commercial model between Openfield and DHL there is an immediate need to add the NET COST as an additional field into the outbound DESP2 EDI flow.
Change Request Details:
There is an immediate need to add the cost into the outbound EDI DESP2 flow as an additional field. This will need to be added to the schema so the location of the field can then be passed to DHL-Link so they can prepare the EDI xsd and commence development of the physical flow. The cost to be sent should be the total NET cost not the cost per tonne or the cost plus VAT. The Revenue should also be sent.
Benefits identified as a result of the change:
To enable charging to Openfield to continue electronically considerably reducing financial risk to the business of human error and continued audibility of revenue streams.
Solution
A new item ORDER_COST should be added to the schema flow, this item should appear at the end of the flow after the signature item. The value contained within this item will be the cost per tonne applied to the order multiplied by the contractual weight of the order as displayed in the Cost column in the carrier trip planning screen. The field will only be present in the DESP2 flow (omitted from DESP1), as will all fields in the DESP2 flow as this field will only be present in the flow if it is populated. The Revenue item is already sent within the DESP2 flow.
Scope
This change will be applied to system version 10.7.0.
Set-up
Pre-requisites
The new version 2.22 of the TripOrder.xsd file is in use by DHL Link.
Menu Structure
Unchanged
Data
Unchanged
Implementation Advice
The latest version of the ‘INT_XML_OUT2’ package need only will be applied.
Functional Description
TripOrder Format
The ‘TripOrder.xsd’ XML format will be changed to include a new item called ‘ORDER_COST’ after the ‘SIGNATURE’ item in the ‘MILESTONE’ section as shown below:
v2.21:
v2.22:
‘ORDER_COST’ will be defined as a decimal element type, with a maximum of 22 digits including 2 fractional digits; this will match the corresponding column called ‘ORD_COST’ on the ‘SCH_ORD’ database table (i.e. ‘NUMBER(20,2)’).
‘ORDER_COST’ will be an optional milestone items if no cost is populated.
Version 2.22 of ‘TripOrder.xsd’ will be created for this development and is included in Appendix A.
INT_XML_OUT2 Package
Procedure ‘GEN_MILESTONE_END’ will be changed to include the new ‘ORDER_COST’ item but only for process ‘DESP2’ and if the order cost has been populated (i.e. it is not a null value).
Process ‘DESP2’ is run once per day at a specific time for the ‘POD_RECEIVED’ trigger point; whereas process ‘DESP1’ is run at regular intervals for all trigger points.
Process ‘DESP2’ will only require the ‘ORDER_COST’ item to be populated; therefore the external system for the XML control record must be ‘DESP2’ for the item to be included.
The ‘ORDER_COST’ item will be populated directly from the ‘ORD_COST’ column on the ‘SCH_ORD’ table as the calculation used to populate this column is appropriate (i.e. the cost per tonne of the order multiplied by the contractual weight of the order).
In the example above, the ‘ORDER_COST’ item will display ‘203.00’ as taken from the ‘Cost’ field and not the ‘Total’ field because this includes the ‘VAT’.
Table Updates Required
No database table changes are required.
References
| EST-291782 BS-8LFGGC Add Net Cost to DESP2 v1.0.doc | |||
Glossary
| C-TMS | Calidus TMS |
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
