PATCH WMS P040: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 151: | Line 151: | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
Line 181: | Line 182: | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
Line 199: | Line 199: | ||
|} | |} | ||
--> | --> | ||
== | |||
{| width="100%" | == Aptean Log Number: 01594443 == | ||
|- | {| width="100%" | ||
|width="30%"|''' | |- | ||
|- | |width="30%"|'''Summary of Call'''|| DPD Integration | ||
|'''Summary of Call'''|| | |- | ||
|- | |'''Detail of Fix''' || DPB format - Ensure minimum default weight calculated correctly. | ||
|'''Detail of Fix''' || | |||
|- | Change weight display to be 3dp rather than 2dp. | ||
|'''Set-up and Configuration''' || | |||
|} | No longer report order level Del Delivery value, only take value from owner level field. | ||
Hardcode Terms of Del flag for Channel Isle orders to DAP, regardless of customer. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01597529 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| DPD Integration | |||
|- | |||
|'''Detail of Fix''' || Add new owner level rule DHPF (DHEG Packing Functionality) rule | |||
If set, the generated pack records will be left open and the order will not be marked as 'Pack Complete'. Otherwise standard logic will apply. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01593039 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Unhandled exception during location upload | |||
|- | |||
|'''Detail of Fix''' || The configurable EDI process to upload locations into the warehouse will default the bonded flag to N should one not be provided. | |||
The location use type will be mandatory to ensure that the locations are identified correctly. | |||
Any validation messages or error messages will be available for the user to review. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01592509 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Runtime Error | |||
|- | |||
|'''Detail of Fix''' || Fixed POD packages to prevent null values in CY_JB_ID. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01600121 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Bay Diary Issue | |||
|- | |||
|'''Detail of Fix''' || Fixed Bay Diary when changing Direction and Booking Type. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01600511 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Despatch Note | |||
|- | |||
|'''Detail of Fix''' || Amendments to the queries have been made to separate the main query to use order number or route/load and to assess if ranges have been entered. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01612964 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Can not run ORS report if DELIVERY DESCRIPTION field is included | |||
|- | |||
|'''Detail of Fix''' || The columns 'Del Description' and 'Pack Complete' will be updated using a database script with the correct database names for the 'ORDER' report. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01626368 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Despatch note - WES format | |||
|- | |||
|'''Detail of Fix''' || The WES despatch note has been changed. | |||
The orders will be printed in order number sequence then by pick list number sequence. | |||
This sequence will be used when printing a range of order numbers or by route/load. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01594474 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Despatch error | |||
|- | |||
|'''Detail of Fix''' || Amendments to the WCS shipment pallet despatch process and the despatch confirmation process. | |||
Extra auditing of packing and shipment activity by users in C-WMS screens has been included to track when users delete records. | |||
The 'Despatch Confirmation' screen has been changed to prevent the user updating the despatch details or despatching stock that exists on a shipment pallet - the manual confirmation process and shipment pallet process will be kept separate to ensure that the users operate by a single method. | |||
The user will be warned that there is stock for an order on a shipment pallet when the query is run for the selection criteria. | |||
The user will be informed that there is stock for an order on a shipment pallet when the 'Details' screen is opened. | |||
The user will be able to 'Deassign' the palletised orders when prompted upon quering the 'Despatch Confirmation' screen, or via a new 'Deassign Order' button. | |||
This button will be available in the 'Options' when the user has used a route/load as part of the selection criteria. | |||
The user will then not be able to amend the despatch details until the order is depalletised. | |||
Unsuccessfully despatch details will be rolled back for the user to review the reason why. | |||
The despatched quantities will not be initialised in the 'Despatch Confirmation' screen or its 'Details' screen. | |||
However, the user can amend the despatched quantities in the 'Details' screen with a reason code but only when the order does not exist on a shipment pallet. | |||
The other despatched quantities will be set when the user confirms the despatch. | |||
The stock that exists on a shipment pallet must be despatched in the 'Shipment Pallet Maintenance' screen or using WCS. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01631775 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Despatch (PDP) Message | |||
|- | |||
|'''Detail of Fix''' || Fix error when order packed into more than 10 separate packs | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01629653 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Storage charges on owners CCH & FPL | |||
|- | |||
|'''Detail of Fix''' || The rent charges were being generated for 'old' transactions because the same pallet had been used to receive stock for different owners and stock codes. | |||
When the ownership of the stock on the pallet was changed the 'old' transactions are then assessed because they still exist for the new owner and stock code and the stock for the new pallet now requires rent to be charged. | |||
The change of ownership will now reset the date of receipt for the new stock to be when the change was made rather than when the original pallet was received. | |||
Then the 'old' transactions will be omitted from the current rent cycle. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01630419 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Goods Receipt Confirmation | |||
|- | |||
|'''Detail of Fix''' || The 'Expected Num Pallets' will not be recalculated based on the current received quantity. | |||
They can then be compared against the 'On Hand Pallets'. | |||
Once all stock has been received, the 'Confirm Receipt' button will be displayed. | |||
If not all stock is received, the 'Confirm' option in the tree can be used. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01636204 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| WHS0552 - Stock take cycle template | |||
|- | |||
|'''Detail of Fix''' || The stock take template can be created without a partner code for the owner code. | |||
The lists of values for the owner code will use the name of the owner code itself. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00216435 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Allocation incorrectly assigning master seq value (from testing 01719785 ) | |||
|- | |||
|'''Detail of Fix''' || Add new stock level trigger to populate serial numbering field to 2 (do not use serial numbers) if field is blank | |||
Add new script to populate stock codes whose serial numbering field is blank but exist against owners which are setup to use serial numbering | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00216586 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| EDI - GRMK message not being generated after Receipt confirmation on the portal | |||
|- | |||
|'''Detail of Fix''' || Portal GRN putaway process now generates the GRMK confirmation message when owner set to run at either receipt and or put-away stages. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01630989 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Stock is held but does not appear on transactions reports | |||
|- | |||
|'''Detail of Fix''' || The stock movement screen WHS0700 has been changed to ensure that the entered audit number is only accepted for the type of movement for which it was created. | |||
For example, a specified pallet or stock movement then cannot be confirmed as a location movement. | |||
This will prevent the user unexpectedly moving all stock in a location as part of an intended pallet or stock movement. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01596068 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Kitting release issue | |||
|- | |||
|'''Detail of Fix''' || Re-work of Stock Kits Assembly confirmation process. | |||
Stop users from assigning kitting orders to pick waves and packs. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00209798 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Packing screen not refreshing - plus extra emails for shipment pallets | |||
|- | |||
|'''Detail of Fix''' || The dispatch confirmation process has been changed to inform and prevent the user dispatching orders that have been packed onto shipment pallets. | |||
Users will be informed that the order has stock on a shipment pallet and the user will have the option to deassign a palletised order from a route/load should the rest of the orders need to be dispatched manually. | |||
The dispatched quantities will not be defaulted to the picked quantities in the Despatch Confirmation screen to ensure that running totals can be maintained for the orders that have been packed onto shipment pallets. | |||
These quantities will be set for the manual dispatch confirmation when it is started. | |||
The user will still be able to amend the dispatched quantities in the screen prior to dispatch confirmation by entering a reason code for the quantity to be dispatched. | |||
An email can be sent for an error message during the dispatch confirmation process of the shipment pallets using RDT. | |||
A resolution email will also be sent should the problem be resolved, for example, a database lock has been released and the process could be resubmitted. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01640552 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| SH1 CANC message not being delivered | |||
|- | |||
|'''Detail of Fix''' || The sales order will be updated with new values for its ordered quantities, weights and volumes when the sales order lines are entered, amended or cancelled. | |||
If the sales order is fully cancelled by cancelling all its order lines or by cancelling the order itself, a 'CANC' message will be generated for a 'GEN_CANC' outbound EDI process. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01729103 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Despatch note BR2 | |||
|- | |||
|'''Detail of Fix''' || The BR2 despatch note will accommodate up to 25 characters for the Pallet ID from the Picking Container ID or the Customer Pallet ID. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01612851 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Line type 8 allocation issue | |||
|- | |||
|'''Detail of Fix''' || For line type 8 orders, when finding valid rotations, ignore pallets linked to outstanding moves, which when complete will remove the pallet | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00219596 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| WMS Carrier code - 4 characters, should be restricted to 3 | |||
|- | |||
|'''Detail of Fix''' || A new field called 'Carrier Code Length' can be set in the 'Company Maintenance' screen. | |||
This field can be used to set a maximum length for any new carrier codes that are created in the 'Carrier Maintenance' screen. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01638573 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| EDI Issue | |||
|- | |||
|'''Detail of Fix''' || Amended package validation and data update. Issue is when many orders for many owners uploaded in single file. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01739343 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| GRN Upload | |||
|- | |||
|'''Detail of Fix''' || The POD format of the pre-advised GRNs will validate that the customer pallets are not duplicated within the file for different products and for the same product. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01622531 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Movement by location | |||
|- | |||
|'''Detail of Fix''' || The catch weight is not mandatory for Pallet movements and Location-Pallet movements when not using a catch-weighted product. | |||
Pallet movements and Location-Pallet movements can be created and confirmed with catch-weighted products and non-catch-weighted products. | |||
The movements can only be processed for the correct type of movement as per a previous development. | |||
The movements can be confirmed as a whole or by line. | |||
An error with a ROWID is not displayed in the later versions than 4.60 of WHS0700. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00214541 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Incomplete location-pallet movements of consolidated pallets in manual Stock Movements. | |||
|- | |||
|'''Detail of Fix''' || The Stock Movement screen will move the bulk pallets and the consolidated pallets as part of stock, pallet and location movements. | |||
Location movements can also consolidate the pallets and retain existing pallets. | |||
Held stock will be moved to the new pallet in the new location. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01630333 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Stock Adjustment | |||
|- | |||
|'''Detail of Fix''' || Amend 'free' case and unit calculations to include committed values. As created by line type 4 and 5 order lines | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01743592 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| SH1 kit item not fly kitted | |||
|- | |||
|'''Detail of Fix''' || Amend EDI fly kitting validation, so that negative stock warehouse values do not affect 'available' stock calculations. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 01595176 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Deals Issue | |||
|- | |||
|'''Detail of Fix''' || Both CVS and PDF version of the report are amended so that if an order is amended and or returned, it shows the correct values, regardless whether a discount has been applied to the order or not. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00215291 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Missing stock code on ASN from EDI upload | |||
|- | |||
|'''Detail of Fix''' || The format of the GRN pre-advice file supports groups of J021, J031 and J041 lines. | |||
Serial numbers will be extracted for the J041 lines and they will be made available to attach to the customer pallets on receipt. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Aptean Log Number: 00232005 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Final serial number not being returned | |||
|- | |||
|'''Detail of Fix''' || Ensures that the correct number of serial numbers are selected when the VAPS rule is active. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||