259081
259081 - NW-7M8D33/ New Parameter to Control the Order Schedule Date
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
Create a new system parameter to control order schedule dates.
Currently when an order is created the schedule is determined based on the earliest collection date and time of the collection window.
A new system parameter is required to control this and therefore enable the schedule of an order to be determined by any of the following:
’ECDT’ - Earliest Collection Date Time
’LCDT’ - Latest Collection Date Time
’EDDT’ - Earliest Delivery Date Time
’LDDT’ - Latest Delivery Date Time
These four letter values should be applied to the system parameter, suggested name: ‘SCH_SCHED_ORD_DERIVE’.
Therefore if the parameter is set to ‘LCDT’ and the latest collection date and time on the order is 12:00 22/12/08 the schedule would be ‘081222’; if it is set to ‘ECDT’ and the earliest collection date and time on the order is 21:59 21/12/08 the schedule will be ‘081221’.
Note that you may need to reference ‘SCH_SCHED_START’ as this controls the time on which a schedule starts: ‘081222’ starts at 22:00 21/12/08.
Solution
A new system parameter called ‘SCH_SCHED_ORD_DERIVE’ will be introduced to control the schedule on which an order will be assigned when it is created either manually via the ‘Orders’ screen or via the ‘IMPORT’ process of the ‘Order_Import’ format name (this import will be for the ‘TI_ORDER’ import type, the ‘ORDER_AND_LINE’ record type and the ‘orders.csv’ filename as setup in the ‘Import Maintenance’ screen).
The new system parameter will control the schedule of the order if it has been set to one of 4 values:
’ECDT’ - Early Collection Date and Time
’LCDT’ - Late Collection Date and Time
’EDDT’ - Early Delivery Date and Time
’LDDT’ - Late Delivery Date and Time
If it has not been set or it has been set to a value other than those listed above then the existing default of the early collection date and time will be used to determine the schedule.
As the duration of the schedule may not be concurrent with the same day for a 24 hour period, the existing system parameter ‘SCH_SCHED_DURATION’ and ‘SCH_SCHED_START’ will be referenced, as at present, for when the order is assigned to a schedule.
For example, if ‘SCH_SCHED_ORD_DERIVE’ is set to ‘LCDT’ and the late collection date and time on the order is ‘12:00 22/12/08’ the schedule would be ‘081222’; if it is set to ‘ECDT’ and the early collection date and time on the order is ‘21:59 21/12/08’ the schedule will be ‘081221’ if the new schedule starts on ‘081222’ starts at ‘22:00 21/12/08’.
The new system parameter will also be referenced when the relevant date and time of the order is updated so that the schedule of the order is changed accordingly.
For example, if ‘SCH_SCHED_ORD_DERIVE’ is set to ‘ECDT’ and the early collection date and time of the order is changed so that it is within a different schedule window then the user will be prompted to confirm if the schedule should be changed; if so then the schedule of the order will be updated as advised.
The same logic will apply when an order is re-booked so that the user has the opportunity to update the schedule of the order.
The new system parameter called ‘SCH_SCHED_ORD_DERIVE’ will also be applicable for all UK Databases for assigning orders to schedules and it will behave as described in the above section.
Other clients are able to create orders via bookings using the ‘Create TI’s’ process in the ‘Booking Order’ screen and the new system parameter must be referenced to determine the schedule for the order and slots.
Note that when orders are reversed using the ‘Reverse TI’s’ process in the ‘Booking Order’ screen that the bookings are found for the schedule name of the booking and not the order should a schedule name have been specified in the parameters screen.
Scope
These changes will be applied to system version 10.6 on HCRTST and once approved HCRPRD.
SET-UP
Pre-Requisites
Database has parameter SCH_SCHED_DURATION and SCH_SCHED_START set up.
Data
The new functionality around Order Schedule Date will be controlled by new parameter SCH_SCHED_ORD_DERIVE. This parameter has 4 acceptable values;
’ECDT’ - Early Collection Date and Time
’LCDT’ - Late Collection Date and Time
’EDDT’ - Early Delivery Date and Time
’LDDT’ - Late Delivery Date and Time
This parameter will be set up in table ADM_SYSTEM_PARAM
This parameter can be configurable via the System Parameters form. It has initially been set to ECDT as the Early Collection date and Time is what is used in the original functionality. It will also be the default setting if it is not set up in a database so functionality remains unchanged. This can be changed to any of the acceptable values for permitted users.
FUNCTIONAL DESCRIPTION
Current Functionality
Below will detail some samples where the Schedule of an order is populated;
This shows the schedule being populated for a new order on a Save. You can see that the Early/late Collect/deliver times are all on different days. On a Save the Schedule is set to 090807 as the Early Collect Time determines this:
Below is an example of the current functionality. An order on Sched 070707 has had its Collect and Deliver times updated to 08/07/08. When saving the changes it asks the user do thay want to change the schedule to 070708, as the Early Collection Date and Time is passed into SCH.Get_Schedule to retrieve the relevant schedule. If the schedule retrieved doesn’t match that on the entry form, the user is asked do they want to change the schedule.
NOTE: The functionality around re-booking an order via the ORDERS form does not need to be amended. Below the new order created earlier on Sched 090807 has been re-booked. During this process the user can enter the date on which they want the re-booked order to appear. Entered below is 30-08-09. Clicking OK will ask the user whether they want to change the schedule of the re-booked order, and are given multiple options. This includes setting the schedule to that specified by the date enter or manually entering the schedule yourself.
If the user selects ENTER to manually enter a new schedule as seen below the collect and deliver times are updated according to the date the user entered in the re-book form, and the schedule can be edited as the user requires:
Therefore, the REBOOK functionality will remain unchanged unless there is a specific requirement to do so.
Import TI_Order
The estimate noted that Import Type of TI_ORDER would make use of the new functionality. Currently this process will set the Schedule of the Imported Order to the value held in the position according to field SCHED_DATE. You can see that this is a specific imported field in this type of import. Therefore, this will always determine the schedule of the order imported. It is possible to use either EARLY_AVAIL, LATE_AVAIL, ERLY_DEL or LATE_DEL to determine the orders schedule date as part of the new functionality, but it will first need to be confirmed by the client that it is ok for SCHED_DATE to be ignored in the imported file if parameter SCH_SCHED_ORD_DERIVE is set up in a specific database.
SCH.Get_Schedule
SCH.Get_Schedule is referenced in other areas of the system. However, it is the passed in date that determines which schedule name is assigned. As seen earlier, this is important in creating and updating orders in the ORDERS form as currently the Early Collection Date and Time is passed in, but the new functionality will pass in a different Date and Time depending on the value held in the new system parameter.
The below area which also reference SCH.Get_Schedule will not be amended as only 1 specific date can be passed in to determine the schedule. This is generally the Delivery Date associated with a Booking:
BKG.Create_Product_Summary
BKG.Apply_Prod_Sum
BKG.Auto_Summary_TSK
GEN_TI.Create_Booking_TIs
GEN_TI.Create_Booking_TIs_TSK
INT_MSG.Read_Booking_File
IMP.Process_ASN_Booking – only a delivery date imported so this must be used to determine the schedule
OMS.Validate_Schedule – specific single date passed to validate the schedule
OMS.Create_Order_From_Template – specific single date passed in not related to order info
OMS_INT.F_Duplicate_Order_Schedule – specific schedule passed in
BOOKINGS form uses Delivery date of a Booking
PURCH_ORD form uses Cargo Ready date of an order (IIB specific)
TRIPDTL form uses call to SCH.Get_Schedule the same as for Re-booking in ORDERS therefore no change is required as this functionality has ability to set Schedule Date as detailed earlier
TRIP_OVERVIEW forms passes in current date to set date of Schedule drop down
The following 3 functions make a call to OMS.Insert_Empty_Order passing in the EARLY_AVAIL date. OMS.Insert_Empty_Order then makes use of SCH.Get_Schedule and passes in the date to this. These 3 functions will need amending to reference the value held in new system parameter and pass in the correct date associated with an order:
INT_MSG.Post_Order
INT_XML_OUT.Post_Order
OMS_INT.Post_Order
Function OMS.Validate_Order and OMS.Insert_Order specifically call SCH.Get_Schedule from within their function always passing in EARLY_AVAIL. Again, these 2 functions will have to be updated to pass in the correct date according to the value held in new parameter SCH_SCHED_ORD_DERIVE.
Note Function INT_MSG.Process_Iggesund_Order_File makes use of SCH.Get_Schedule, passing in the EARLY_AVAIL date to get the Schedule of the order. This is IIB specific code which may be updated also, so if the time comes to release this functionality to IIB they can make use of the new functionality, or default back to the original functionality so that EARLY_AVAIL will always be passed in.
REFERENCES
| EST-259081 NW-7M8D33 New Parameter to Control the Order Schedule Date v1.doc | |||
| EST-259081 NW-7M8D33 New Parameter to Control the Order Schedule Date v2.doc | |||
| EST-259081 NW-7M8D33 New Parameter to Control the Order Schedule Date v4.doc |
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
