PATCH WMS 810 P034
OBS Logistics Ltd
Release Notes
CALIDUS WMS
3rd Dec 2019 - 1.0
Reference: P034
Contents
- 1 SUMMARY INTRODUCTION
- 2 CHANGE REQUESTS
- 2.1 Customer Ref: EDI inputs - XML
- 2.2 Customer Ref: Bay diary update
- 2.3 Customer Ref: PO No 106447
- 2.4 Customer Ref: WREQ0033019
- 2.5 Customer Ref: PO012775
- 2.6 Customer Ref: PO012775
- 2.7 Customer Ref: CRA desp
- 2.8 Customer Ref: CEN009 / 354069
- 2.9 Customer Ref: Back Orders
- 2.10 Customer Ref: Pick Conf
- 3 SUPPORT INCIDENTS
- 4 TID CHANGES
- 5 OBSL PRODUCT DEVELOPMENT
- 6 MODULES DELIVERED
- 7 ADDITIONAL CHANGES
SUMMARY INTRODUCTION
INTRODUCTION
The main aim of this document is to provide CALIDUS WMS 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: EDI inputs - XML
| OBS Log Number: | 346685 |
| Summary of Call | EDI data inputs - XML format |
| Detail of Fix | New XML flows. Need the process and common setting up manually. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Bay diary update
| OBS Log Number: | 360828 |
| Summary of Call | Bay diary update - order special inst. |
| Detail of Fix | Change to pass text fields from/to bay diary. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: PO No 106447
| OBS Log Number: | 361842 |
| Summary of Call | CR: Intelligent Shipper integration |
| Detail of Fix | Create new outbound Intelligent shipper API
Create outbound API call to get packing information Take inbound message, and generate a pdf label from information. Convert this label into a zebra compatible file and send to printer. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: WREQ0033019
| OBS Log Number: | 362007 |
| Summary of Call | GSN: Change to Fresh Ordering process |
| Detail of Fix | PO processing amendments for the fresh produce ordering |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: PO012775
| OBS Log Number: | 364827 |
| Summary of Call | CRA Despatch Conf EDI Format |
| Detail of Fix | The 'CRA' format of the despatch confirmation EDI file includes data for these columns:
1 Source Pallet ID (SSCC) 2 Stock Code 3 Destination Pallet (ID (SSCC) 4 Sales Order Number 5 Case Quantity 6 Use By Date The delimiter for the CSV file will be a comma by default but the EDI process can specify an alternative separator. The case quantity is the packed quantity on the destination pallet ID which is the pack reference. Therefore, unpacked dispatch details will not have a case quantity. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: PO012775
| OBS Log Number: | 364943 |
| Summary of Call | New sales order .csv format (copy GBB) |
| Detail of Fix | Script to amend the EDI map data for the SOP CSV file layout in the GBB format to extend the size of field 3 (P/o or Ref) from 14 to 20 chars. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: CRA desp
| OBS Log Number: | 365648 |
| Summary of Call | CRA desp message - temp release |
| Detail of Fix | Release of temp package for CRA despatch message format |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: CEN009 / 354069
| OBS Log Number: | 358594 |
| Summary of Call | Further changes to POD label format |
| Detail of Fix | Remove stock bar code and tweak field sizes. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Back Orders
| OBS Log Number: | 362117 |
| Summary of Call | Updates to the back order report |
| Detail of Fix | Amend the Order SW / Detail ORS report to add 4 new fields.
Original ordered cases and units and original despatched cases and units. This represents what was originally ordered and despatched against the order the back order is linked against. |
| Set-up and Configuration | No set-up/configuration required |
Customer Ref: Pick Conf
| OBS Log Number: | 363585 |
| Summary of Call | Packing at pick confirmation |
| Detail of Fix | New owner rule MPPC will create pack records when a sales order is confirmed as picked manually.
An unpacked despatch details will be appended to an open pack number for the sales order should any picking have been performed using RDT. |
| Set-up and Configuration | No set-up/configuration required |
SUPPORT INCIDENTS
Customer Ref:
| OBS Log Number: | Reporter: |
| Summary of Call | |
| Detail of Fix | |
| Set-up and Configuration | No set-up/configuration required |
TID CHANGES
OBS Log Number:
| Cust Ref: | Reporter: |
| Summary of Call | |
| Detail of Fix | |
| Set-up and Configuration |
OBSL PRODUCT DEVELOPMENT
OBS Log Number:
| Reporter: | |
| Summary of Call | |
| Detail of Fix | |
| Set-up and Configuration | No set-up/configuration required |
MODULES DELIVERED
| Module Name | Version No | Description | Log Number |
|---|---|---|---|
ADDITIONAL CHANGES
WCS
A WCS change is required for the following logs:
- Log
OR
There are no WCS changes required.
EPOD/T2A
An ePOD/T2A change is required for the following logs:
- Log
OR
There are no ePOD/T2A changes required.
MCS
An MCS change is required for the following logs:
- Log
OR
There are no MCS changes required.
PORTAL/TTM
A Portal change is required for the following logs:
- Log
OR
There are no Portal changes required.
EDI
An EDI change is required for the following logs:
- Log
OR
There are no EDI changes required.
