281781
281781 - JB-89RUHB/ Unilever MIS
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
There is a requirement to get the following modifications made to MTS / MTS extract and MTS COGNOS MIS to facilitate the reporting required for the Unilever contract due to go live on Nov 1st
Priority GAP's
- Report - POD Performance GAP: POD Scanned Date. (POD date may be in Dunelm version now , consider that would only work for orders POD'd after change implemented.)
- Report - Vehicle Fill : GAP : How do we exclude certain hauliers e.g. FGP (factory gate pricing). JB - There is no categorisation of these currently. Look at setting the hauliers up with additional code prefixed with FGP.
- Report - Case Fill : GAP : Line level information is populated within CTMS where customers provide it , this is required within COGNOS.
- Report : POD Feedback : GAP : No debrief time provided.
Secondary GAP's
- Report : Subcontract spend :GAP: direct costs are not within MTS.
- Report - Warehouse capacity :GAP - Where do we get static data for the warehouse's input / output constraints. JB - Can this be held against the collection points within
CTMS , how much granularity do we need on the variance in hour of the day.
- Report : Loads planned (expected to depart) out per hour:GAP : Missing the audit history which would show when a load changed into various states such as PLANNED.
- Report - Cancellations Revenue GAP : Notification period.
- Report - Cancellation Revenue : GAP: Cancellation Date not being sent in existing extract , could be part of bigger problem in that audit records not sent.
- Report - Lates: GAP : Reason Code , Sub Reason Code, Reason Code Comments are not reported.
Update from Jez Brookes only items 1 - 4 are to be addressed by C-TMS
Solution
- POD_DATE column will be added to relevant data table and necessary trigger applied to populate subsequently updated records.
- Will be handled by data changes made within C-TMS by the implementation team (i.e. prefix carrier code with FGP)
- SCH_ORD_ITEM and SCH_ORD_ITEMS_REASONS will be added to the extract
- SCH_TRIP_AUDIT table will be added to the MIS extract to display ‘CONFIRMED’ status change date.
- Additionally FULL_LOAD will be added from SCH_TRIP to assist with identifying Full Trailer Loads. (Added during meeting 07/10/10)
Scope
This change will be applied to system version 10.5
FUNCTIONAL DESCRIPTION
Item 1
POD Performance GAP: POD Scanned Date. (POD date may be in Dunelm version now , consider that would only work for orders POD'd after change implemented.)
POD_DATE column will be added to relevant data table and necessary trigger applied to populate subsequently updated records.
See 278544 - AS-86WEWU for details:
T_SCH_ORD_POCPOD.sql v5.3 and AT_SCH_TRIP_278544.sql to be applied.
Item 2
Report - Vehicle Fill : GAP : How do we exclude certain hauliers e.g. FGP (factory gate pricing). JB - There is no categorisation of these currently. Look at setting the hauliers up with additional code prefixed with FGP.
No Action required by OBS.
Item 3
Report - Case Fill : GAP : Line level information is populated within CTMS where customers provide it , this is required within COGNOS.
See Appendix A for details. Columns from tables:
SCH_ORD_ITEMS SCH_ORD_ITEM_REASONS
Item 4
Report : POD Feedback : GAP : No debrief time provided.
See Appendix A for details. Columns from table:
SCH_TRIP_AUDIT
Item 5
Additionally FULL_LOAD will be added to the MIS_EXTRACT_DETAILS from SCH_TRIP to assist with identifying Full Trailer Loads.
REFERENCES
Not Available
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
