PATCH CTMS P038
Release Notes
CALIDUS TMS
15th Dec 2020 - 1.0
Reference: P038
SUMMARY INTRODUCTION
INTRODUCTION
The main aim of this document is to provide CALIDUS TMS users with the level of detail required to accurately test all software included in the patch. The document also contains set-up and configuration details to enable the user to configure the system correctly for the new functionality to work.
GLOSSARY OF TERMS
| Term | Meaning |
|---|---|
| C-TMS | Transport Management System |
| C-WMS | Warehouse Management System |
| CR | Change Request |
| C-WCS | Warehouse Control System |
| C-ePOD | Electronic Proof of Delivery |
| C-MCS | Mobile Control System |
| C-TTM | Track and Trace Management |
| EDI | Electronic Data Interchange |
| TID | Testing Issue Development, or Log |
TESTING PROCESS
TIDs AND RESOLUTION
If there are any areas of the functionality that are not acceptable or do not meet the requirement specified in the Change Request then these should be expressed by raising a TID.
FINAL 'END TO END' TESTING
Prior to release to a production database, a full 'End to End' test is required on the test system by all sites using the database. Once this is signed off, a release date can be arranged.
AUTHORISATION
Authorisation from nominated release personnel only will be required when requesting a release to a production environment
CHANGE REQUESTS
Customer Ref: PO-087071
| OBS Log Number: | 360569 |
| Summary of Call | Web service request for PWSCORE |
| Detail of Fix | New Order Enquiry Webservice for PWSCORE |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Order Integration
| OBS Log Number: | 370557 |
| Summary of Call | Order Integration |
| Detail of Fix | Changes to the Inbound XML for integration |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Booking Integration
| OBS Log Number: | 370558 |
| Summary of Call | Booking Integration - Update back to OR3 |
| Detail of Fix | New outbound flow from C-TMS to OR3 |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Email Order
| OBS Log Number: | 370560 |
| Summary of Call | Email output of order booking |
| Detail of Fix | Changes for Customer Services screen. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Format File
| OBS Log Number: | 373655 |
| Summary of Call | Data Warehouse format file (tab) |
| Detail of Fix | New system parameter MIS_TAB_DELIMITER exists to use a tab as a delimiter for the MIS extracts. When this parameter is Y, a tab will be used as a delimiter for the MIS extract files.
Assesses a new value for the MIS query to use: Transactional will use created date and updated date within the date ranges for the MIS report values of 'P_from_date' and 'p_to_date' to select records. The standard delimiter should be setup as '||'@'||' for conversion to a tab delimiter. Reference (which is the default value) will use the existing queries. |
| Set-up and Configuration |
| New Parameters | |||
|---|---|---|---|
| Parameter Name | Config Level | Setting Value | Result |
| MIS_TAB_DELIMITER | SYSTEM | Y | A tab will be used as the delimiter for the MIS extract files. |
| MIS_TAB_DELIMITER | SYSTEM | N | The specified delimiter will be used for the MIS extract files. |
Customer Ref: CSV Import
| OBS Log Number: | 375194 |
| Summary of Call | CSV import changes |
| Detail of Fix | System parameter TRM_PROTECT_SHUNTS will be used to resequence the trips stops by planned arrival and departure times.
The trip stops will be created for the different types of trips for the orders. These trips will include shunts between the same locations, collections from suppliers and deliveries to stores. The collection stops from suppliers will be fixed to the planned available times of the orders on the stops. These stops will contain orders for the same time windows for collection or delivery. |
| Set-up and Configuration |
| New Parameters | |||
|---|---|---|---|
| Parameter Name | Config Level | Setting Value | Result |
| TRM_PROTECT_SHUNTS | SYSTEM | Y | To prevent the orders from being scheduled onto the same stops, when an order is added to a trip, the system will check if there is an existing stop at the required location and if the order currently on the stop has different order windows, a new stop will be created. The stops created will inherit both the collection and delivery times from the order. |
| TRM_PROTECT_SHUNTS | SYSTEM | N | This trip stop protection will not be active. |
Customer Ref: CR-41
| OBS Log Number: | 370034 |
| Summary of Call | Asset to Asset Scanning |
| Detail of Fix | The new T2A functionality for transport units will be available in the new Forward Items and Unload screens.
The latest version 4.0.0.0 of T2A will need to be released with this development. The reason codes AP (Added to Primary Transport Unit), TU (Successfully Unloaded Contents from Primary Transport Unit) and UU (Unexpectedly Unloaded Contents from Primary Transport Unit) will need to be setup for type ITEM_NON_CON when Forward Items is active. The new system parameter T2A_ASSET_ARRIVED_OFFSET_DAYS can be set with a number of days to select DELIVERED orders that have arrived at the depot. The new system parameter T2A_ASSET_DUE_OFFSET_DAYS can be set with a number of days to select planned orders that are due to arrive at the depot. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM01-IM02
| OBS Log Number: | 373052 |
| Summary of Call | ARM: Mapping & Mods to Order Flow |
| Detail of Fix | The inbound EDI process will have new parameters available to set the ordered quantity for orders based on the weight of the order lines when an ordered quantity cannot be provided.
An EDI parameter called CALC_ORD_DU_QTY can be set to Y to activate the new functionality. An EDI parameter called WEIGHT_BASED_DU_QTY can be set to Y to enable a calculation to be performed for the WEIGHT provided and the Max Kg of the DU type. The ordered quantity will then be based on the WEIGHT/Max Kg with the next whole number used. If this calculation is not supported by the absence of a WEIGHT provided or the Max Kg for the DU type, an EDI parameter called DFLT_DU_QTY can be set to a number to specify that a default number of DUs will be ordered. Note the EDI parameter VOLUME_BASED_DU_QTY_QTY overrides the weight calculation and default. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM03
| OBS Log Number: | 373053 |
| Summary of Call | ARM: Parcel Load Message |
| Detail of Fix | Changes to prevent messages from being sent more than once when PREVENT_RESEND_ORDER is added to flow and set to Y |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM04
| OBS Log Number: | 373054 |
| Summary of Call | ARM: Core Fleet Parcels |
| Detail of Fix | Exclude du categorys from Scheduling engine based on specific parameters |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM05
| OBS Log Number: | 373055 |
| Summary of Call | ARM: Pack message flow JDA - CTMS |
| Detail of Fix | New functionality is available for the order packing processes for XML files, CIPD files and manual packing, unpacking and label printing in CTMS.
See functional specification 'FS-373055 - ARM - IM05 Pack Message Flow JDA - CTMS for Parcel Carrier Orders v3.0' for further advice about setup to activate the new functionality. This development will enable unscheduled orders to be packed for the standard packing process. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM08
| OBS Log Number: | 373057 |
| Summary of Call | ARM: Core Fleet Labels |
| Detail of Fix | Changes to allow labels to be printed for UNSCHEDULED and SCHED_COLL orders |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM09
| OBS Log Number: | 373058 |
| Summary of Call | ARM: Shunt / Trunk Planning |
| Detail of Fix | The new system parameter called PAR_SHUNT_TRUNK can be set to Y to enable the Paragon interface to maintain shunt/trunk trips based on fixed routes instead of cross-dock paths.
A new button called Schedule to Depot will be displayed in the Order Export page of the Paragon Interface screen from which the UNSCHEDULED orders can be cross-docked before the Export button is used. The Export button will validate first that an order exists that has been cross-docked before any orders are exported to Paragon. The Schedule to Depot process is intended to cross-dock all available orders. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM10
| OBS Log Number: | 373088 |
| Summary of Call | ARM: Stage Planning- Schedule for parcel |
| Detail of Fix | A Carrier Trunk flag has been introduced for the Fixed Routes to enable cross-docking of orders for collection by parcel carriers.
This flag will be effective for TRUNK route types in the scheduling engine for parcel carriers. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM12 (split IM13-14)
| OBS Log Number: | 373091 |
| Summary of Call | ARM: Load Message for JDA |
| Detail of Fix | New functionality is available for the triggering and generaion of the LOAD files in CTMS.
See functional specification 'FS-373091 - ARM - IM12 Load Message for JDA v2.0' for further advice about setup to activate the new functionality. This development will enable orders to be triggered only when they have not been sent previously for the same EDI process. New references will be available in the output files based on new EDI parameters INC_TRIP_ACTION for a trip reference and INC_TRIP_TYPE for an order reference. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM15 (split IM16)
| OBS Log Number: | 373092 |
| Summary of Call | ARM: Despatch Messages from JDA |
| Detail of Fix | Changes to the EDI processing to receive a Despatch message from JDA - New EDI parameters required on the flow. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM17
| OBS Log Number: | 373093 |
| Summary of Call | ARM: Report re-label required |
| Detail of Fix | A new export called 'Orders for Relabelling' is available to authorise to users to create an extract for a specified schedule of orders that have had labels printed before they were scheduled for delivery and then they have been scheduled for delivery to a carrier with a different label format. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Screening charge
| OBS Log Number: | 373170 |
| Summary of Call | Screening Fee |
| Detail of Fix | Changes to the Finance function to allow Screening charges to be calculated and configured |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM13 - IM14 (split)
| OBS Log Number: | 373631 |
| Summary of Call | ARM: Load Message for JDA at a Hub |
| Detail of Fix | UNLOAD and LOAD messages will be available for configuration at a hub location.
Trips for unloading and loading at a depot to cross-dock orders will be triggered by the usual methods for the EDI processes: updating the trip status to a specific status, updating the planned trip stop times, assigning an order to the trip whilst at the specified trip status. The depot for the EDI process will apply to the location where the trip is being unloaded or loaded. An UNLOAD message will require the new EDI parameter UNLOAD_ONLY to be set to Y otherwise the EDI process will apply to LOAD messages as standard. New EDI parameters will apply to the orders to include in the UNLOAD and LOAD messages and if these messages need to be delayed until previous EDI messages have been received to provide the expected level of data to include in these messages. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM16 (split)
| OBS Log Number: | 373633 |
| Summary of Call | ARM: Receipt Messages from JDA |
| Detail of Fix | RCVD messages will be available for receipt scans into a hub location.
EDI parameters may be configured to ensure that these scans are only used for auditing purposes or to update the scanned items as packed nd despatched as tracking references. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: PO 44010989681
| OBS Log Number: | 374133 |
| Summary of Call | SCR:Extract Suite changes |
| Detail of Fix | The TRIP_TYPE reporting suite extract will include new columns for Start DateTime and End DateTime. These columns will select the same data as the existing Start Time and End Time columns and they can be used as alternative columns.
The new columns can be used as selection criteria with a range of dates and times. The same columns will be available for the EX_TRIP reporting suite extract. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM12 - 2
| OBS Log Number: | 377157 |
| Summary of Call | ARM: LOAD Message with Child Addresses |
| Detail of Fix | A new EDI parameter called INC_ORDER_CHILD_ADDR has been introduced to include any child addresses for the delivery location of the order in the ORDER_HEADER_ADDRESS section.
The ADDRESS_ID will further be decoded to the original location code for the child location using the CN_LOCATION_MAPPING. This EDI parameter is intended to be made active for LOAD messages to specific WMS source systems. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: WREQ0049241
| OBS Log Number: | 378047 |
| Summary of Call | GSN:Add Customer Ref to UKMAIL Label |
| Detail of Fix | Changes to the UKMAIL label to show external ref |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: WREQ0049355
| OBS Log Number: | 378048 |
| Summary of Call | GSN:Change Import xml from CTMS to EFX |
| Detail of Fix | The new system parameter EFX_INV_TRIP_VEH_TYPE controls the population of the VEHICLE_TYPE in the EFX files:
When N: TRIP level: NULL, ORDER level: TIPPER When Y: TRIP/ORDER level: Trailer type for the trip stops |
| Set-up and Configuration |
| New Parameters | |||
|---|---|---|---|
| Parameter Name | Config Level | Setting Value | Result |
| EFX_INC_TRIP_VEH_TYPE | COST_CENTRE | N | Does not include the vehicle type for the trip stop from EFX. |
| EFX_INC_TRIP_VEH_TYPE | COST_CENTRE | Y | Includes the vehicle type for the trip stop from EFX. |
Customer Ref: WREQ0050167
| OBS Log Number: | 378203 |
| Summary of Call | GSN:Changes to DTS label |
| Detail of Fix | Changes to the Label format for DTS |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Customer Account
| OBS Log Number: | 378263 |
| Summary of Call | Customer Account - going on hold |
| Detail of Fix | The customer and its available orders can be placed on hold via a new EDI process or via the Customer Maintenance screen using the new AccOn Hold tick box.
Orders may be updated to a status of ON-HOLD and released to their appropriate status of INVALID or UNSCHEDULED afterwards. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: WREQ0050313
| OBS Log Number: | 378264 |
| Summary of Call | GSN:Flow - Output IF007B and IF054 |
| Detail of Fix | New CFX interface , sending trips when status changed to Tendered |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: TID-Microlise
| OBS Log Number: | 378652 |
| Summary of Call | Prevent empty resource tags |
| Detail of Fix | Prevent empty resource tags from being sent to Microlise set MIC_SEND_EMPTY to Y to use the functionality |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: WREQ0030373
| OBS Log Number: | 376771 |
| Summary of Call | CTMS & Microlise Improvements (2) |
| Detail of Fix | Changed to Paragon and Microlise processing |
| Set-up and Configuration | No set-up/configuration required |
SUPPORT INCIDENTS
Customer Ref: INC33792237
| OBS Log Number: | 374383 |
| Summary of Call | CMTS Issue |
| Detail of Fix | Changes to the POP list on Carr _id in the Order Well |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC34072383
| OBS Log Number: | 375557 |
| Summary of Call | Inbound outbound scanning not reading |
| Detail of Fix | Correct load scan figure on cross dock report
Ensure load figure for crossdock report is correct in all cases |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Portal Order Import
| OBS Log Number: | 376720 |
| Summary of Call | Portal Order Import processing inactive |
| Detail of Fix | Validate location status and reject inactive on portal import |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: IM15 - 2
| OBS Log Number: | 377426 |
| Summary of Call | ARM: Amendments to DSPD Message |
| Detail of Fix | The DSPD message will account for a full trip ID in the TRIP_ID item.
Pre-packed orders will not be updated. Duplicate tracking references and order items will not be stored based on the ITEM_IDENTIFIER item although the order line quantity will be incremented to indicate that a parcel may be added to a pallet. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC35182669
| OBS Log Number: | 377941 |
| Summary of Call | C-TMS manual manifest process |
| Detail of Fix | Ensure the failure/success files can be viewed. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC35185040
| OBS Log Number: | 377947 |
| Summary of Call | Issue with User account access in CTMS |
| Detail of Fix | Amendment to trip manipulation screen TRIPSUM to correct for default layout of unscheduled orders section so does not display over the scroll-bar on right hand side. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC35270134
| OBS Log Number: | 378022 |
| Summary of Call | Ducplicate entry in OF |
| Detail of Fix | DU type string on the financials string now includes statement to sequence in DU type order. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Del Point
| OBS Log Number: | 378030 |
| Summary of Call | Del Point Ref on Trip Sheet |
| Detail of Fix | The Del Point Ref column will wrap the reference to the next line like the Customer Ref and Booking Ref columns in the customer Trip Sheet. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Extract Carrier
| OBS Log Number: | 378068 |
| Summary of Call | Carrier missing from Extract |
| Detail of Fix | Correct label for Carrier ref |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC35394670
| OBS Log Number: | 378089 |
| Summary of Call | Order are not auto-scheduling |
| Detail of Fix | A default value of 'NONE' will apply to the system parameter 'SCHED_ENG_EXC_DU_CATEGORY' when processing orders for parcel carriers in the scheduling engine.
When this system parameter contains a DU category the order will be assessed and excluded from scheduling in the engine to a parcel carrier if the order has that DU category. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: UAT Screening
| OBS Log Number: | 378222 |
| Summary of Call | Minor change following UAT |
| Detail of Fix | Amendment to RATING to create payment at status A following UAT |
| Set-up and Configuration |
| Registry/Rules Settings | ||
|---|---|---|
| Path & Name | Setting Value | Result |
| TDL_ITEM_IN_PORTAL_FORMAT | Y/N | N – items are generated as current setup
Y – items are generated in same format as the portal order entry |
Customer Ref: Trip sheet Issues
| OBS Log Number: | 378284 |
| Summary of Call | Trip sheet Issues |
| Detail of Fix | The Driver Trip Sheet has had its layout amended for consistency. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Customer Collections
| OBS Log Number: | 378653 |
| Summary of Call | PTV unschedules Customer Collections. |
| Detail of Fix | Amendment to the RESET NEW function to check current location of an order and work out the status |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Item Identifier
| OBS Log Number: | 377872 |
| Summary of Call | Item identifier issue |
| Detail of Fix | If new parameter TDL_ITEM_IN_PORTAL_FORMAT is set to Y, the .Gen Items. in CTMS order entry will create in the same format as the portal order entry |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: ITINC0188491
| OBS Log Number: | 377123 |
| Summary of Call | Orders not updating on epod |
| Detail of Fix | Send EPOPD updates when orders are added or removed even when the trip is at status COMPLETED in C-TMS |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: ITINC0191619
| OBS Log Number: | 377907 |
| Summary of Call | Checklist - TMS Incident - pick up |
| Detail of Fix | Fix to allow the same driver name for different depots. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Trip option
| OBS Log Number: | 378053 |
| Summary of Call | Remove Delete Trip Option |
| Detail of Fix | Delete Trips using the button or the menu option can be performed for PLANNED, TENDERED or ACCEPTED trips in the ALL page if the user has access to the function TRM_Delete_Trip.
Debrief can be performed using the button of the menu option for EN-ROUTE, COMPLETED or CONFIRMED trips in the ALL page and the STATUS pages. The trips and orders are displayed at the advised level for the preferences. Configurable layouts may be used for each status and level. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC35581457
| OBS Log Number: | 378228 |
| Summary of Call | Cross-dock report contains no data |
| Detail of Fix | Changes to the scanning process to prevent sucessful scans from being added if an item is marked as damaged |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC35784605
| OBS Log Number: | 378404 |
| Summary of Call | Scheduling auto planning all parcelorder |
| Detail of Fix | All On Sched PARCEL orders will be excluded from the parcel scheduling engine process when the system parameter ORD_ON_SCHED_DEL_LOC is active for the customer of the orders. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: INC33969738
| OBS Log Number: | 375128 |
| Summary of Call | Order disappeared |
| Detail of Fix | Additional test put in ORDERS form to prevent users from blanking out the cost centre name - orders without a cost centre are not visible in the order well. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Child Location
| OBS Log Number: | 377660 |
| Summary of Call | ARM: Child location code format |
| Detail of Fix | The first 8 characters of the location code will be used to form the location code in CTMS and then to create variant child addresses for free type addresses.
These 8 characters can include an underscore although an underscore will also be used to form the location code for the variant address for the order. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Tracking Ref
| OBS Log Number: | 377661 |
| Summary of Call | ARM: Maximum length of tracking referenc |
| Detail of Fix | The first part of the ITEM_IDENTIFIER before the pipe delimiter will be used as the tracking reference and/or the order item when EDI parameter STORE_SHIPPING_LPN = Y.
This parameter will be used for an inbound DSPD message for despatch scanning of pallets and items. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Missing Routes
| OBS Log Number: | 378414 |
| Summary of Call | Routes missing from planning screen |
| Detail of Fix | Trips will be created for the routes and the orders will be planned to those routes when they are imported.
If a problem occurs during auto-planning, an attempt will be made to rollback the trip that has been created. If the trip could not be rolled back, it can be identified in the trip planning screens and updated as required. The user will be informed in the Results and Failures files about which routes have been created successfully or not. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Portal Label
| OBS Log Number: | 377811 |
| Summary of Call | Portal Label |
| Detail of Fix | Alternative version of Portal Label for A6 size labels. |
| Set-up and Configuration | No set-up/configuration required |
TID CHANGES
OBS Log Number: 375979
| Customer Ref: | POL UAT |
| Summary of Call | Change following UAT |
| Detail of Fix | Changes following UAT |
| Set-up and Configuration | No set-up/configuration required |
OBS Log Number: 378655
| Customer Ref: | TMS-CTL |
| Summary of Call | Issue with flow from TMS to CTL |
| Detail of Fix | Changes to customer services to allow for invalid orders to be processed. |
| Set-up and Configuration | No set-up/configuration required |
OBS Log Number: 378646
| Customer Ref: | Webservice updates |
| Summary of Call | PWScore webservices updates |
| Detail of Fix | Changes for PWSCORE webservice highlighted in UAT |
| Set-up and Configuration | No set-up/configuration required |
OBSL PRODUCT DEVELOPMENT
OBS Log Number: 354359
| Summary of Call | New Trigger Point WMS-TMS - Resources |
| Detail of Fix | Changes to the transport data for the trip and the loading trip stop at the depot will update the route/load via the TMS-WMS interface.
The carrier, driver, tractor, trailer and seal number will update the transport data for the route/load. |
| Set-up and Configuration | No set-up/configuration required |
OBS Log Number: 378237
| Summary of Call | Exclude On Sched PARCEL during scheduling |
| Detail of Fix | Orders for customers will only be added to existing 'MAN' or 'PAR' trips by the scheduling engine.
Orders for a DU category can be excluded from the scheduling engine using the system parameter 'SCHED_ENG_EXC_DU_CATEGORY' (e.g. 'PALLET'). Orders for a delivery type can be excluded from the scheduling engine using the system parameter 'ORD_ON_SCHED_DEL_LOC' (e.g. 'PARCEL,'). These 'PARCEL' orders will be excluded when they are 'On Sched' or when they match an existing 'PALLET' category order for the same locations and the same order dates. |
| Set-up and Configuration | No set-up/configuration required |
OBS Log Number: 377448
| Summary of Call | New order screen scroll bar issue |
| Detail of Fix | The vertical scrollbar in the Order Items tab page in the ORDERS_WIDE screen can be used to display all records in the block. |
| Set-up and Configuration | No set-up/configuration required |
OBS Log Number: 377699
| Summary of Call | Unable to query data on reason codes |
| Detail of Fix | The Reason Codes in the Business Data Maintenance screen will be selected based on the system parameter ORD_REASON_CODE_FILTER for the user's cost centre and/or customer group. These records can then be filtered. |
| Set-up and Configuration | No set-up/configuration required |
OBS Log Number: 377823
| Summary of Call | MCS - trip debrief issue |
| Detail of Fix | The trips for the airport (lodgment, flight and collection) also will be debriefed automatically on despatch and receipt when an air waybill has not been captured. |
| Set-up and Configuration | No set-up/configuration required |
MODULES DELIVERED
| Module Name | Version No | Description | Log Number |
|---|---|---|---|
| ACC.sql | 5.81 | Accounts package | 373170 |
| ACC_MAINT.fmx | 2.93 | Accounts Maintenance | 373170 |
| ACC_MAINT.fmx | 2.95 | Accounts Maintenance | 370560 |
| AT_ACC_PAYMENT_TYPE_373170.sql | 1.1 | AT Script | 373170 |
| AT_ACC_SERVICES_370560.sql | 5.2 | AT Script | 370560 |
| AT_GEO_LOCATION_373055.sql | 1.1 | AT Script | 373055 |
| AT_GEO_PLAN_REGION_DEPOT_373058.sql | 1.1 | AT Script | 373058 |
| AT_INT_ORD_REFERENCES_373092.sql | 1.1 | AT Script | 373092 |
| AT_INT_XML_ORD_DETAILS_370557.sql | 1.1 | AT Script | 370557 |
| AT_MIS_EXTRACT_HEADER_373655.sql | 1.1 | AT Script | 373655 |
| AT_OMS_SCHED_GROUP_370560.sql | 5.1 | AT Script | 370560 |
| AT_ORG_CUSTOMER_373170.sql | 1.1 | AT Script | 373170 |
| AT_ORG_CUSTOMER_378263.sql | 1.1 | AT Script | 378263 |
| AT_PAR_TRIP_DTL_376771.sql | 1.1 | AT Script | 376771 |
| AT_RTE_ROUTE_373088.sql | 1.1 | AT Script | 373058 |
| AT_RTE_ROUTE_373088.sql | 1.1 | AT Script | 373088 |
| AT_SCH_ORD_AUDIT_370560.sql | 1.1 | AT Script | 370560 |
| AT_SCH_ORD_AUDIT_ARCHIVE_370560.sql | 5.1 | AT Script | 370560 |
| AT_SCH_ORD_ITEMS_370034.sql | 1.1 | AT Script | 370034 |
| AT_SCH_ORD_ITEMS_CONTENT_370557.sql | 1.1 | AT Script | 370557 |
| AT_SCH_ORD_SERVICES_370560.sql | 5.2 | AT Script | 370560 |
| BDM.fmx | 2.101 | Business Data Form | 370560 |
| BDM.fmx | 2.102 | Business Data Form | 377699 |
| CSV.sql | 5.121 | CSV extract package | 373058 |
| CT_INT_PAR_DEL_DATES.sql | 1.3 | CT Script | 376771 |
| CT_ORG_CUSTOMER_SCREENING_373170.sql | 1.6 | CT Script | 373170 |
| CT_SEQ_CUST_SCREENING_373170.sql | 1.1 | CT Script | 373170 |
| CT_SEQ_INT_STOP_XML.sql | 1.1 | CT Script | 376771 |
| CT_SEQ_PAR_DEL_DATES.sql | 1.1 | CT Script | 376771 |
| CT_T_ORDER_LIST_370034.sql | 1.1 | CT Script | 370034 |
| CT_T_TU_CONTENTS_LIST_370034.sql | 1.1 | CT Script | 370034 |
| CUST_COST.fmx | 2.135 | Customer Maintenance form | 373170 |
| CUST_COST.fmx | 2.136 | Customer Maintenance form | 378263 |
| DATA_ADM_LOG_PROG_NAME_370034.sql | 1.1 | Data Script | 370034 |
| DATA_ADM_SYSTEM_PARAM_360569.sql | 1.2 | Data Script | 360569 |
| DATA_ADM_SYSTEM_PARAM_370557.sql | 1.1 | Data Script | 370557 |
| DATA_ADM_SYSTEM_PARAM_370558.sql | 1.1 | Data Script | 370558 |
| DATA_ADM_SYSTEM_PARAM_370560.sql | 1.1 | Data Script | 370560 |
| DATA_ADM_SYSTEM_PARAM_373054.sql | 1.1 | Data Script | 373054 |
| DATA_ADM_SYSTEM_PARAM_373170.sql | 1.1 | Data Script | 373170 |
| DATA_ADM_SYSTEM_PARAM_375194.sql | 1.1 | Data Script | 375194 |
| DATA_ADM_SYSTEM_PARAM_376771.sql | 1.1 | Data Script | 376771 |
| DATA_ADM_SYSTEM_PARAM_377123.sql | 1.1 | Data Script | 377123 |
| DATA_ADM_SYSTEM_PARAM_377872.sql | 1.1 | Data Script | 377872 |
| DATA_ADM_SYSTEM_PARAM_378047.sql | 1.2 | Data Script | 378047 |
| DATA_ADM_SYSTEM_PARAM_378048.sql | 1.1 | Data Script | 378048 |
| DATA_ADM_SYSTEM_PARAM_378264.sql | 1.1 | Data Script | 378264 |
| DATA_ADM_SYSTEM_PARAM_378646.sql | 1.2 | Data Script | 378646 |
| DATA_ADM_SYSTEM_PARAM_378652.sql | 1.1 | Data Script | 378652 |
| DATA_ADM_SYSTEM_PARAM_CONFIG_378047.sql | 1.1 | Data Script | 378047 |
| DATA_ADM_SYSTEM_PARAM_CONFIG_378048.sql | 1.1 | Data Script | 378048 |
| DATA_ADM_SYSTEM_PARAM_CONFIG_378264.sql | 1.1 | Data Script | 378264 |
| DATA_ADM_SYSTEM_PARAM_CONFIG_360569.sql | 1.2 | Data Script | 360569 |
| DATA_ADM_SYSTEM_PARAM_CONFIG_373054.sql | 1.1 | Data Script | 373054 |
| DATA_ADM_SYSTEM_PARAM_CONFIG_377872.sql | 1.1 | Data Script | 377872 |
| DATA_EDI_FLOW_TYPES_370558.sql | 1.1 | Data Script | 370558 |
| DATA_I_1_ADM_SYSTEM_PARAM_373055.sql | 1.1 | Data Script | 373055 |
| DATA_I_1_ADM_SYSTEM_PARAM_373091.sql | 1.1 | Data Script | 373091 |
| DATA_I_2_ADM_SYSTEM_PARAM_CONF_373055.sql | 1.1 | Data Script | 373055 |
| DATA_I_ADM_SYSTEM_PARAM_370034.sql | 1.2 | Data Script | 370034 |
| DATA_I_ADM_SYSTEM_PARAM_373058.sql | 1.1 | Data Script | 373058 |
| DATA_I_ADM_SYSTEM_PARAM_373655.sql | 1.1 | Data Script | 373655 |
| DATA_IMP_FIELD_373170.sql | 1.1 | Data Script | 373170 |
| DATA_IMP_FIELD_376771.sql | 1.1 | Data Script | 376771 |
| DATA_IMP_IMPORT_TYPE_373170.sql | 1.1 | Data Script | 373170 |
| DATA_IMP_IMPORT_TYPE_376771.sq | 1.1 | Data Script | 376771 |
| DATA_ORG_CUST_REV_CHG_TYPE_373170.sql | 1.1 | Data Script | 373170 |
| DATA_ORS_MASTER_DATA_374133.sql | 1.1 | Data Script | 374133 |
| DATA_ORS_MASTER_DATA_378068.sql | 1.10 | Data Script | 378068 |
| DATA_REP_REPORT_370560.sql | 5.10 | Data Script | 370560 |
| DATA_REP_REPORT_373093.sql | 1.1 | Data Script | 373093 |
| DATA_REP_REPORT_PARAM_373093.sql | 1.1 | Data Script | 373093 |
| DATA_RES_LABEL_FORMAT_378203.sql | 1.1 | Data Script | 378203 |
| DP_ASSET_SCANNING.sql | 5.52 | Tag to Asset Scanning | 370034 |
| DP_ASSET_SCANNING.sql | 5.54 | Tag to Asset Scanning | 377907 |
| DP_CARRIER.sql | 1.90 | Carrier Management | 373055 |
| DP_CARRIER.sql | 1.91 | Carrier Management | 373057 |
| DP_CARRIER.sql | 1.92 | Carrier Management | 378047 |
| DP_CSV_DHL.sql | 1.22 | Export Package | 373093 |
| DP_CSV6.sql | 1.41 | CSV Extract package | 375557 |
| DP_CUST_SERV.sql | 1.30 | Customer Service Package | 370558 |
| DP_CUST_SERV.sql | 1.33 | Customer Service Package | 370560 |
| DP_CUST_SERV.sql | 1.34 | Customer Service Package | 378655 |
| DP_EPOD_WEB_SERVICE.sql | 1.130 | EPOD Web Service | 360569 |
| DP_EPOD_WEB_SERVICE.sql | 1.132 | EPOD Web Service | 378646 |
| DP_EPOD_WEB_SERVICE.sql | 1.129 | EPOD Web Service | 370034 |
| DP_IMP.sql | 5.39 | Imports Package | 373055 |
| DP_IMP.sql | 5.40 | Imports Package | 373170 |
| DP_IMP_2.sql | 1.78 | Import Package | 376720 |
| DP_INT_XML_CFX.sql | 1.1 | Database Package | 378264 |
| DP_MCS_SCANNING.sql | 5.67 | MCS Scanning Package | 377823 |
| DP_MIS.sql | 5.6 | MIS Interface Package | 373655 |
| DP_NOKIA_LOC_PLAT.sql | 1.31 | Nokia Location Platform Interface | 360569 |
| DP_RDT_FAST_UNLOAD.sql | 5.47 | RF Unload Package | 378228 |
| DP_SCHEDULING_ENGINE.sql | 5.164 | Scheduling Package | 373054 |
| DP_SCHEDULING_ENGINE.sql | 5.165 | Scheduling Package | 373058 |
| DP_SCHEDULING_ENGINE.sql | 5.166 | Scheduling Package | 373088 |
| DP_SCHEDULING_ENGINE.sql | 5.167 | Scheduling Package | 378089 |
| DP_SCHEDULING_ENGINE.sql | 5.168 | Scheduling Package | 373631 |
| DP_SCHEDULING_ENGINE.sql | 5.169 | Scheduling Package | 378237 |
| DP_SCHEDULING_ENGINE.sql | 5.170 | Scheduling Package | 378404 |
| DP_SHIPMENT.sql | 5.31 | Shipment Code package | 375979 |
| DP_WEB_SERVICE_ENQUIRY.sql | 1.1 | Web Service Package | 360569 |
| DP_WEB_SERVICE_ENQUIRY.sql | 1.3 | Web Service Package | 378646 |
| IMP.sql | 5.200 | CSV Imports Package | 373170 |
| IMP.sql | 5.201 | CSV Imports Package | 376771 |
| IMP.sql | 5.202 | CSV Imports Package | 378414 |
| IMPORTS_EXEC.fmx | 10.28 | Import executions | 376771 |
| IMPORTS_EXEC.fmx | 10.22 | Import executions | 377941 |
| INT_XML_EFX.sql | 5.18 | EFX XML Package | 378048 |
| INT_XML_IN.sql | 5.201 | Order Import Package | 373052 |
| INT_XML_IN.sql | 5.202 | Order Import Package | 373055 |
| INT_XML_IN.sql | 5.205 | Order Import Package | 373092 |
| INT_XML_IN.sql | 5.207 | Order Import Package | 377426 |
| INT_XML_IN.sql | 5.208 | Order Import Package | 377660 |
| INT_XML_IN.sql | 5.209 | Order Import Package | 377661 |
| INT_XML_IN.sql | 5.210 | Order Import Package | 370557 |
| INT_XML_IN.sql | 5.211 | Order Import Package | 373633 |
| INT_XML_IN.sql | 5.212 | Order Import Package | 378263 |
| INT_XML_IN_REFS.sql | 1.12 | Openfield Order upload procedures | 373092 |
| INT_XML_IN_REFS.sql | 1.13 | Openfield Order upload procedures | 373633 |
| INT_XML_MIC.sql | 5.151 | MIC interface | 376771 |
| INT_XML_MIC.sql | 5.152 | MIC interface | 378652 |
| INT_XML_MIC.sql | 5.149 | MIC interface | 373091 |
| INT_XML_OUT2.sql | 5.306 | Outbound XML Package | 373053 |
| INT_XML_OUT2.sql | 5.307 | Outbound XML Package | 373091 |
| INT_XML_OUT2.sql | 5.308 | Outbound XML Package | 370558 |
| INT_XML_OUT2.sql | 5.309 | Outbound XML Package | 377157 |
| INT_XML_OUT2.sql | 5.311 | Outbound XML Package | 373631 |
| INT_XML_SMA.sql | 5.23 | SMA interface | 373091 |
| INV.sql | 5.52 | Invoice Package | 378022 |
| ITEM_MANAGEMENT.fmx | 1.7 | Item Management | 370034 |
| LOCATION.fmx | 2.194 | Location Maintenance | 373055 |
| LOGIX_INT.fmx | 10.5 | Form for LOGIX Interface | 378653 |
| OF_INT.sql | 5.63 | Oracle Financials interface | 373170 |
| OMS.sql | 5.233 | Order package | 373054 |
| OMS.sql | 5.234 | Order package | 373055 |
| OMS.sql | 5.235 | Order package | 370558 |
| OMS.sql | 5.237 | Order package | 378263 |
| OMS.sql | 5.236 | Order package | 373170 |
| ORDERS.fmx | 2.431 | Order Screen | 373055 |
| ORDERS.fmx | 2.432 | Order Screen | 370558 |
| ORDERS.fmx | 2.434 | Order Screen | 373170 |
| ORDERS.fmx | 2.435 | Order Screen | 370557 |
| ORDERS.fmx | 2.436 | Order Screen | 377872 |
| ORDERS.fmx | 2.433 | Order Screen | 375128 |
| ORDERS_WIDE.fmx | 1.30 | Orders Screen | 373055 |
| ORDERS_WIDE.fmx | 1.31 | Orders Screen | 370558 |
| ORDERS_WIDE.fmx | 1.32 | Orders Screen | 370034 |
| ORDERS_WIDE.fmx | 1.33 | Orders Screen | 377448 |
| ORDERS_WIDE.fmx | 1.34 | Orders Screen | 370557 |
| ORION.mmx | 1.51 | Orion Menu | 370034 |
| PAR.sql | 5.108 | Paragon Interface | 373058 |
| PAR.sql | 5.109 | Paragon Interface | 376771 |
| PAR_INT.fmx | 10.42 | Paragon Interface form | 373058 |
| PLANNING.fmx | 1.114 | Planning Screen | 374383 |
| PLANNING.fmx | 1.116 | Planning Screen | 378264 |
| RATE.sql | 5.159 | Rates Tariff database package | 373170 |
| RATE.sql | 5.160 | Rates Tariff database package | 378222 |
| ROUTES_MAINT.fmx | 2.50 | Fixed Routes Maintenance | 373088 |
| STATIC_DATA_MAINT.fmx | 1.27 | Static Data Maintenance Screen | 373058 |
| T_SCH_ORD_AUDIT.sql | 5.18 | Trigger for SCH_ORD_AUDIT | 370558 |
| T_SCH_ORD_PNL.sql | 5.16 | Trigger | 373170 |
| TDL_PORTAL_LABEL.rep | 1.1 | Portal Label | 377811 |
| TRG_ORG_CUSTOMER_SCREENING_UID.sql | 1.2 | Trigger | 373170 |
| TRG_SCH_ORD_EARLY_DEL.sql | 1.2 | Trigger | 376771 |
| TRG_SCH_ORD_OR3.sql | 1.2 | Trigger | 370558 |
| TRG_SCH_ORD_TRANSPORT.sql | 1.3 | Trigger | 370034 |
| TRG_SCH_TRIP_XML_GEN.sql | 5.17 | Trigger | 354359 |
| TRG_SCH_TRIP_XML_GEN.sql | 5.18 | Trigger | 373091 |
| TRG_SCH_TRIP_XML_GEN.sql | 5.20 | Trigger | 373631 |
| TRG_SCH_TRIP_XML_GEN.sql | 5.21 | Trigger | 378264 |
| TRG_SHA_XML.sql | 5.26 | Trigger | 377123 |
| TRG_SHA_XML_GEN.sql | 5.10 | Trigger | 373091 |
| TRG_SHA_XML_GEN.sql | 5.12 | Trigger | 373631 |
| TRG_SHA_XML_GEN.sql | 5.13 | Trigger | 378264 |
| TRG_SOI_XML.sql | 5.21 | Trigger | 370034 |
| TRG_STS_XML_GEN.sql | 5.11 | Trigger | 373631 |
| TRG_STS_XML_GEN.sql | 5.8 | Trigger | 354359 |
| TRG_STS_XML_GEN.sql | 5.9 | Trigger | 373091 |
| TRIP_OVERVIEW.fmx | 1.63 | Trip Waterfall | 378053 |
| TRIP_PLAN.fmx | 1.276 | Trip Planning Screen | 374383 |
| TRIP_PLAN.fmx | 1.278 | Trip Planning Screen | 378264 |
| TRIP_SHEET.rep | 1.6 | Trip sheet report | 378030 |
| TRIP_SHEET.rep | 1.7 | Trip sheet report | 378284 |
| TRIPSUM.fmx | 2.441 | Trip Manipulation screen | 374383 |
| TRIPSUM.fmx | 2.442 | Trip Manipulation screen | 377947 |
| TRIPSUM.fmx | 2.444 | Trip Manipulation screen | 378264 |
| TRM.sql | 5.199 | Trip manipulation package | 373055 |
| TRM.sql | 5.201 | Trip manipulation package | 375194 |
| TRM.sql | 5.200 | Trip manipulation package | 378414 |
| V_ORD_AUDIT.sql | 1.4 | View | 370560 |
| V_ORD_ORDER_LINE.sql | 1.2 | View | 370560 |
| V_ORD_ORDER_LOCATION.sql | 1.1 | View | 370560 |
| V_ORD_ORDER_STATUS.sql | 1.2 | View | 370560 |
| V_ORD_REQUIREMENT.sql | 1.7 | View | 370560 |
ADDITIONAL CHANGES
WCS
There are no WCS changes required.
EPOD/T2A
There are no ePOD/T2A changes required.
T2A
An T2A change is required for the following logs:
- Log 370034 - v4.0.0.0
PORTAL/TTM
A Portal change is required for the following logs:
- Log 378203 - v9.00.002
EDI
There are no EDI changes required.
