PATCH CTMS P036: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 303: | Line 303: | ||
|} | |} | ||
--> | --> | ||
== Customer Ref: | |||
== Customer Ref: Invoicing == | |||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
|''' | |width="30%"|'''OBS Log Number:'''|| 362735 | ||
|- | |- | ||
|''' | |'''Summary of Call'''|| Invoice rejected | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Detail of Fix''' || Changes to allow the XML file to deal with special characters without causing issues for invoicing | ||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC30622188 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 365637 | |||
|- | |||
|'''Summary of Call'''|| Not able to split without adding volume | |||
|- | |||
|'''Detail of Fix''' || Amendment to the OMS packages called when splitting and order to prevent an error when calculation of the remaining volume/weight has a divide by 0. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: MCS == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 366165 | |||
|- | |||
|'''Summary of Call'''|| HAM - MCS Item History / Splitting | |||
|- | |||
|'''Detail of Fix''' || The item history will be retained when the item is split to a new order and given a prefix of X to exclude the item from further scanning. The validation of the pallets being despatched will enable other depots and trips to be assessed. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: MCS == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 366346 | |||
|- | |||
|'''Summary of Call'''|| HAM - MCS Despatch Logging | |||
|- | |||
|'''Detail of Fix''' || Added some additional info messages for load status changes. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: No ref == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 366711 | |||
|- | |||
|'''Summary of Call'''|| HAM - Pallet Build validation fix | |||
|- | |||
|'''Detail of Fix''' || Pallet building validation has been fixed to that, under new pallet building validation rules, packages passing through different final delivery depots (ROCs) can no longer be palletised together. | |||
This also fixes the suggestion of pallets when an item is scanned. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Despatch Validation == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 367006 | |||
|- | |||
|'''Summary of Call'''|| HAM - Despatch Pallet Validation | |||
|- | |||
|'''Detail of Fix''' || A pallet cannot be despatched on a trip that is going to be unloaded at a different depot than the planned depot. | |||
This validation will also apply to the despatch of loose packages. | |||
Note that system parameter MCS_DESPATCH_TO_PLAN will prevent any pallets or packages being despatched on any but the planned trip when it is active. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: MCS == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 367068 | |||
|- | |||
|'''Summary of Call'''|| HAM - MCS Damages errors | |||
|- | |||
|'''Detail of Fix''' || Only validates if the package or pallet exists for DAMAGES using MCS instead of assessing it as part of the despatch process. | |||
Updates the trip items with the same reason code as the damaged order items. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: POD Generation == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 367400 | |||
|- | |||
|'''Summary of Call'''|| POD Generation Extract query | |||
|- | |||
|'''Detail of Fix''' || The POD Generation Extract will produce the file more efficiently. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC31146492 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 367549 | |||
|- | |||
|'''Summary of Call'''|| Order failed with duplicate key error | |||
|- | |||
|'''Detail of Fix''' || Amendment to order validation process so when called from INT_ERR_ORD the correct EDI process is used for setting global and process parameters. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Internal == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 367610 | |||
|- | |||
|'''Summary of Call'''|| Sched Engine Trunks - multiple legs | |||
|- | |||
|'''Detail of Fix''' || Changes to allow trunk scheduling regardless of delivery windows | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Auditing == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368117 | |||
|- | |||
|'''Summary of Call'''|| Auditing of WCS msg send | |||
|- | |||
|'''Detail of Fix''' || Add user / trip / order info to audit when messages are sent to WCS | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: EDI == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368178 | |||
|- | |||
|'''Summary of Call'''|| Duplicate EDI Order Validation | |||
|- | |||
|'''Detail of Fix''' || The inbound EDI orders will either allow duplicate orders or not allow duplicate orders based on the system parameter OMS_UNIQUE_EXT_REF and the EDI parameter 4000. This EDI parameter will be optional | |||
The EDI parameter 4000 will be optional and it will have a default value of N. | |||
The duplicate order check will be performed when EDI files are processed or reprocessed in the Interface Errors screen when they have failed. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC31401083 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368473 | |||
|- | |||
|'''Summary of Call'''|| Merge branch into mainline version | |||
|- | |||
|'''Detail of Fix''' || Amendment to initialise variable that was causing first DU qty on first line of Paragon extract to be incorrect. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Inventory Transaction == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368963 | |||
|- | |||
|'''Summary of Call'''|| Inventory Transaction - Scanned Trunks | |||
|- | |||
|'''Detail of Fix''' || The scanned trunk trip information will be displayed for the Inventory Transaction extract. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: MCS == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 369066 | |||
|- | |||
|'''Summary of Call'''|| HAM-MCS-Damage parcels are still planned | |||
|- | |||
|'''Detail of Fix''' || A new system parameter called MCS_EXCEPTIONS_DAMAGED is available to mark items as DAMAGED at despatch and receipt when a MCS user loads or unloads with a reason code to indicate an exception to the plan. | |||
The advised reason code will still be stored for the item for the scan but the comment will be DAMAGED instead of the description of the reason code. | |||
This new functionality will be active when this system parameter is set to Y. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: MCS == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 369066 | |||
|- | |||
|'''Summary of Call'''|| HAM-MCS-Damage parcels are still planned | |||
|- | |||
|'''Detail of Fix''' || If a package or a pallet is not despatched, it will not be available to scan on receipt at the next depot or for any onward trips. | |||
A damaged item will not be available for pallet building. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC31644327 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 369154 | |||
|- | |||
|'''Summary of Call'''|| Not generated LOAD messages for H61 | |||
|- | |||
|'''Detail of Fix''' || The LOAD and CITD files can be create for an outbase and without an outbase. | |||
If the EDI parameter OUTBASE_INDICATOR is set to Y and the trip contains an order (or orders) for an outbase (or outbases) and orders not for an outbase, separate files will be produced for each outbase and for the orders without an outbase. | |||
If the EDI parameter OUTBASE_INDICATOR is set to Y and the trip does not contain an order for an outbase (or outbases) and does contain orders not for an outbase, a single file will be produced for the orders without an outbase. | |||
If the EDI parameter OUTBASE_INDICATOR is set to N and the trip contains an order (or orders) for an outbase (or outbases) and orders not for an outbase, a single file will be produced for the orders without an outbase. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC31776738 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 369623 | |||
|- | |||
|'''Summary of Call'''|| Invalid content in EDI file | |||
|- | |||
|'''Detail of Fix''' || Amendment to Microlise outbound file generation to ensure variable to build the shipment detail value can accommodate the combined order field values. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Delivery Extract == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 370161 | |||
|- | |||
|'''Summary of Call'''|| POD Delivery Extract | |||
|- | |||
|'''Detail of Fix''' || Amend date handling so dates outside expected range do not cause errors. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: No ref == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 365630 | |||
|- | |||
|'''Summary of Call'''|| Mainline version of branch 365197 | |||
|- | |||
|'''Detail of Fix''' || Mainline changes for Forecast quantities | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC30925539 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 366646 | |||
|- | |||
|'''Summary of Call'''|| Trips not having preadvised values | |||
|- | |||
|'''Detail of Fix''' || Changes to the schedule format to allow the change of month to be calcualted correctly | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: INC31394604 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368392 | |||
|- | |||
|'''Summary of Call'''|| Not able to run Revenue Check Report | |||
|- | |||
|'''Detail of Fix''' || Re-work on data selection query to improve speed of generating the Revenue check report. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: no ref == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 366240 | |||
|- | |||
|'''Summary of Call'''|| Add Detail Tab and Audit log | |||
|- | |||
|'''Detail of Fix''' || Amendment to order update trigger to audit change to order comments | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: N/A == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368228 | |||
|- | |||
|'''Summary of Call'''|| Cages scanned on trips query | |||
|- | |||
|'''Detail of Fix''' || Master data fields added to the Extract parameters for ASSET_HISTORY to allow report to query on particulare trip id. Will allow extract to be take of assets being scanned into an RDC during a specified arrive time frame. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: NO REF == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 361965 | |||
|- | |||
|'''Summary of Call'''|| Rebook Functionality Error | |||
|- | |||
|'''Detail of Fix''' || Changes to re-book in Orders screen to allow unscheduling when POC flag has been set | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Collection Trip == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368474 | |||
|- | |||
|'''Summary of Call'''|| Amend to collection trip WCS send | |||
|- | |||
|'''Detail of Fix''' || Ability to prevent collection pre-advices | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Inventory Trans == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 367200 | |||
|- | |||
|'''Summary of Call'''|| DUN Inventory Transactions - Scan Data | |||
|- | |||
|'''Detail of Fix''' || The DUN Inventory Transactions export will include order items that have been planned on a trip or scanned on a trip. | |||
Items that are scanned on different trunk trips are not always back-planned on a trip but need to be included for the scanned trip for which they do not exist. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Customer Ref: Packing == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''OBS Log Number:'''|| 368406 | |||
|- | |||
|'''Summary of Call'''|| Issues with packing orders | |||
|- | |||
|'''Detail of Fix''' || The packed quantity on the order lines will be audited. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |} | ||