PATCH C-TMS P035: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 142: Line 142:
|'''Summary of Call'''|| HAM - Connected View Interfaces
|'''Summary of Call'''|| HAM - Connected View Interfaces
|-
|-
|'''Detail of Fix''' || New version 2.43 of TripOrder.xsd will need to be installed by for the EDI files for interfacing with ConnectedView.                                                                                              
|'''Detail of Fix''' || New version 2.43 of TripOrder.xsd will need to be installed by for the EDI files for interfacing with ConnectedView.


The EDI processes for ConnectedView should exist with triggers, parameters and report processes without a location or a customer but for a cost centre.                                                                
The EDI processes for ConnectedView should exist with triggers, parameters and report processes without a location or a customer but for a cost centre.


ORD:                                                                                                           
ORD:                                                                                                           


Flow Type: ORD_XML_OUT
Flow Type: ORD_XML_OUT


Trigger STATUS: UNSCHEDULED                                                                                   
Trigger STATUS: UNSCHEDULED                                                                                   


Parameters:                                                                                                   
Parameters:                                                                                                   
ALLOW_MULTI_CUSTOMER = Y                               
ALLOW_MULTI_CUSTOMER = Y                               
INCLUDE_ORDER_STATUS = Y                               
INCLUDE_ORDER_STATUS = Y                               
SEND_HEADER_UPDATES = Y                                 
SEND_HEADER_UPDATES = Y                                 
SEND_LINE_ITEMS = Y                                                                                           
SEND_LINE_ITEMS = Y                                                                                           


Line 167: Line 170:
Parameters:                                                                                                   
Parameters:                                                                                                   


PACK_EVENT = Y                                        
PACK_EVENT = Y  
                                     
SEND_LINE_ITEMS = Y
SEND_LINE_ITEMS = Y


Line 180: Line 184:


ALLOW_MULTI_CUSTOMER = Y
ALLOW_MULTI_CUSTOMER = Y
INCLUDE_ITEM_DELIVER = Y                               
INCLUDE_ITEM_DELIVER = Y                               
INCLUDE_NONCON_CODES = Y                               
INCLUDE_NONCON_CODES = Y                               
INCLUDE_REASON_CODES = Y                               
INCLUDE_REASON_CODES = Y                               
INCLUDE_REASON_TYPE = Y                                 
INCLUDE_REASON_TYPE = Y                                 
INCLUDE_SIGNATURE = Y                                   
INCLUDE_SIGNATURE = Y                                   
PODS_POCS = Y                                           
PODS_POCS = Y                                           
SEND_LINE_ITEMS = Y                                                                                           
SEND_LINE_ITEMS = Y                                                                                           


Line 247: Line 258:
|'''Summary of Call'''|| HAM - Changes to WMS Despatch (CITD)
|'''Summary of Call'''|| HAM - Changes to WMS Despatch (CITD)
|-
|-
|'''Detail of Fix''' || The EDI processes for LOAD and CITD messages will need to have a new EDI parameter called OUTBASE_INDICATOR set to Y to enable the new functionality.                                                                    
|'''Detail of Fix''' || The EDI processes for LOAD and CITD messages will need to have a new EDI parameter called OUTBASE_INDICATOR set to Y to enable the new functionality.


When the parameter is Y, the LOAD and CITD messages will be split by outbase for the same TMS trip to create separate WMS loads based on the outbase indicator.
When the parameter is Y, the LOAD and CITD messages will be split by outbase for the same TMS trip to create separate WMS loads based on the outbase indicator.
Line 253: Line 264:
Note that any orders that are not going to an outbase for a customer that is using the van fleet will not be included in a file for the outbase and these orders will be included in a file for the TMS trip itself without an outbase indicator.                                                                           
Note that any orders that are not going to an outbase for a customer that is using the van fleet will not be included in a file for the outbase and these orders will be included in a file for the TMS trip itself without an outbase indicator.                                                                           


The customers and fixed routes will need to have the new 'Van Fleet' flag set to Y to enable the new functionality.                                                                                              
The customers and fixed routes will need to have the new 'Van Fleet' flag set to Y to enable the new functionality.


The outbases will be identified as RDC locations that exist with an 'OUTBASE_INDICATOR' decoded value for 'REFERENCE'.
The outbases will be identified as RDC locations that exist with an 'OUTBASE_INDICATOR' decoded value for 'REFERENCE'.


This outbase indicator will be a single character to be included in the TMS trip to replace the first digit of the trip number (e.g. MAN-A0123456 instead of MAN-00123456).                                                                                              
This outbase indicator will be a single character to be included in the TMS trip to replace the first digit of the trip number (e.g. MAN-A0123456 instead of MAN-00123456).


This decoded value must exist to enable the new functionality.
This decoded value must exist to enable the new functionality.
Line 272: Line 283:
|'''Summary of Call'''|| HAM - Item & Master Pallet Labels
|'''Summary of Call'''|| HAM - Item & Master Pallet Labels
|-
|-
|'''Detail of Fix''' || The new package label format will be available for configuration.                                                                                 
|'''Detail of Fix''' || The new package label format will be available for configuration


The new pallet label format will be available for configuration.                                                                                   
The new pallet label format will be available for configuration.                                                                                   
Line 444: Line 455:
|}
|}
-->
-->
== Customer Ref:  ==
 
== Customer Ref: 360403 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 360403
|-
|'''Summary of Call'''|| VDA4933 and VDA4933 additional matches
|-
|'''Detail of Fix''' || When a 4987 matches to more than one 4933 on the same delivery stop, replace the orders on the trip
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: LOTS ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 360459
|-
|'''Summary of Call'''|| Send address to LOTS in ORD event
|-
|'''Detail of Fix''' || Change to allow address details and contacts to be sent to LOTS
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Reason Code ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 361188
|-
|'''Summary of Call'''|| Cancelled Item - Reason Code
|-
|'''Detail of Fix''' || Only create SD reason codes for all items on an order when no items sent and none returned.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: Encrypted sources ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 361652
|-
|'''Summary of Call'''|| Release PL_VERSION
|-
|'''Detail of Fix''' || Release package to assist with version control checks.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: 362482 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 362482
|-
|'''Summary of Call'''|| Email Information - populated fields
|-
|'''Detail of Fix''' || Amendment to XML outbound generation so contact details not based on comments being null but on email address being populated.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: Performance Improvements ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 362723
|-
|'''Summary of Call'''|| Performance Improvements
|-
|'''Detail of Fix''' || Reduced the number of times that the standard journeys are assessed for the 'from' location of the orders when calculating payments.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Invoice Format ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 363373
|-
|'''Summary of Call'''|| Incorrect Invoice format
|-
|'''Detail of Fix''' || Changes to the BL numbers and the frequency reported- no longer at order level but at gate level within the shipment and invoice
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: INC30189216 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 363421
|-
|'''Summary of Call'''|| File has order header but no details
|-
|'''Detail of Fix''' || When determining if an order is to be included in Zetes file extend test for 'SL' reason code items to exclude the 'X' items that have been split off
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: INC30418115 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 364473
|-
|'''Summary of Call'''|| Report showing wrong data
|-
|'''Detail of Fix''' || Amendment to ITEM_MOVEMENTS_EXTRACT_2 to correct to population of POD confirmed date (column T) on so uses scan date
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: Decode Amendment ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 364696
|-
|'''Summary of Call'''|| Change decode names
|-
|'''Detail of Fix''' || Amendment to shipment extract to use Parts decode where appropriate
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Scheduling Engine ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 359457
|-
|'''Summary of Call'''|| Scheduling Engine Single Network
|-
|'''Detail of Fix''' || Ensure when roll back performed inside of loop that it is not then also performed outside of the loop.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: Portal ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 359518
|-
|'''Summary of Call'''|| Portal not reporting shortages
|-
|'''Detail of Fix''' || Changed EPOD interface to ensure quantity set before reason added and also ensure order details sent to LOTS on delivery message.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Empties Changes ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 362440
|-
|'''Summary of Call'''|| Rqmts change for Credit acc on empties
|-
|'''Detail of Fix''' || Changes to the finance functionality based on the Empties not providing the references we expected
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Split Order scanning ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 362828
|-
|'''Summary of Call'''|| Split order scanning delivery trips
|-
|'''Detail of Fix''' || Change to split scanning, to prevent orders being planned on empty stops
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
   
 
== Customer Ref: Support ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 364191
|-
|'''Summary of Call'''|| Debrief issue
|-
|'''Detail of Fix''' || Changes to the shipment extract and removal of validate order when rating a completed trip
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: Trunk Scripts Main ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 364910
|-
|'''Summary of Call'''|| Trunk Scripts added into main stream
|-
|'''Detail of Fix''' || Trunk scripts for Paragon added into main code stream
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Collection dates/times ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 365051
|-
|'''Summary of Call'''|| Validate order collection dates/times
|-
|'''Detail of Fix''' || The just in time orders will only have their collection date/time windows assessed when the order status is INVALID, VALID or UNSCHEDULED.
 
A user context will be set when validating the just in time orders for the cost centre of the order unless the calling process has already done so (e.g. Paragon planning).
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: Packaging and Service ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 359779
|-
|'''Summary of Call'''|| Current packaging and Service charge ext
|-
|'''Detail of Fix''' || Report type OWN_CHRGS already in Oracle reporting suite for the packaging charges. Options added to ORS for
 
1) Service Capture (SRVCS_CAPT)
 
2) Services including sliding charges (ACC_SRVCS)
 
3) Accounts (ACC_ACCOUNT).
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: 361243 ==
{| width="100%"
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''  || '''Reporter:'''
|-
|-
|'''Summary of Call'''||  
|width="30%"|'''OBS Log Number:'''|| 361243
|-
|'''Summary of Call'''|| Export the cost per route
|-
|-
|'''Detail of Fix''' ||
|'''Detail of Fix''' || Add the fields for business data 'Fixed costs by route' to extract suite under type RTE_COSTS.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
|}
|}




Revision as of 13:41, 13 November 2019





Aptean Logo.png







OBS Logistics Ltd

Release Notes

CALIDUS TMS

12th Nov 2019 - 1.0
Reference: P035











































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: Actuals

OBS Log Number: 359621
Summary of Call Ensure all actuals are debriefed
Detail of Fix Ensure all actual weights and volumes are populated before a trip can be set to COMPLETED
Set-up and Configuration No set-up/configuration required


Customer Ref: Despatch

OBS Log Number: 362667
Summary of Call Vehicle Despatch Report
Detail of Fix Add depot to parameters
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0030580

OBS Log Number: 358425
Summary of Call GSN: Create a new report
Detail of Fix The new export Inventory Transactions will need authorisation for the appropriate user groups.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0030824

OBS Log Number: 358506
Summary of Call GSN: Modify ASN interface
Detail of Fix Override collection location on ASN1 dependant on new WS_COLLECT_LOCATION parameter and partnership setting for store.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 358670
Summary of Call HAM - Connected View Interfaces
Detail of Fix New version 2.43 of TripOrder.xsd will need to be installed by for the EDI files for interfacing with ConnectedView.

The EDI processes for ConnectedView should exist with triggers, parameters and report processes without a location or a customer but for a cost centre.

ORD:

Flow Type: ORD_XML_OUT

Trigger STATUS: UNSCHEDULED

Parameters:

ALLOW_MULTI_CUSTOMER = Y

INCLUDE_ORDER_STATUS = Y

SEND_HEADER_UPDATES = Y

SEND_LINE_ITEMS = Y

The order message will be sent for the despatching source depot for the creation and amendment of the orders at the depot.

PACK:

Flow Type: ORD_XML_OUT

Parameters:

PACK_EVENT = Y

SEND_LINE_ITEMS = Y


The pack message will be sent for the despatching source depot for the packing of the orders at the depot.

POCPOD:

Flow Type: TRIP_XML

Parameters:

ALLOW_MULTI_CUSTOMER = Y

INCLUDE_ITEM_DELIVER = Y

INCLUDE_NONCON_CODES = Y

INCLUDE_REASON_CODES = Y

INCLUDE_REASON_TYPE = Y

INCLUDE_SIGNATURE = Y

PODS_POCS = Y

SEND_LINE_ITEMS = Y

The POC messages will be sent for the loading at the source location for the collection orders.

The POD messages will be sent for the unloading at the delivery location for the delivery orders.

This trip may be for a depot that may be an outbase for the van fleet.

The EDI processes also should exist for the LOAD, CITD and electronic manifest messages.

The load message will be sent for the despatching source depot.

The CITD message will be sent for the despatching source depot.

An electronic manifest message will be sent for the despatching delivery depot for the parcel carrier.

This depot may be an outbase for the van fleet.

These EDI parameters can be configured to match the mapping of the files by any external processing for transfer to the source systems for the orders and carriers.

New version 2.43 of TripOrder.xsd will be required for the messages for ConnectedView to be mapped.

This version contains the ORDER_STATUS element at the end of the ORDER_HEADER segment.

Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031664

OBS Log Number: 359252
Summary of Call GSN: Retain FORECAST Value from ASN2
Detail of Fix Set new forecast figures on ASN1 only and send to paragon in preference to planned.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359656
Summary of Call HAM - Microlise Interface
Detail of Fix Changes to the Microlise interface
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359660
Summary of Call HAM - Changes to WMS Despatch (CITD)
Detail of Fix The EDI processes for LOAD and CITD messages will need to have a new EDI parameter called OUTBASE_INDICATOR set to Y to enable the new functionality.

When the parameter is Y, the LOAD and CITD messages will be split by outbase for the same TMS trip to create separate WMS loads based on the outbase indicator.

Note that any orders that are not going to an outbase for a customer that is using the van fleet will not be included in a file for the outbase and these orders will be included in a file for the TMS trip itself without an outbase indicator.

The customers and fixed routes will need to have the new 'Van Fleet' flag set to Y to enable the new functionality.

The outbases will be identified as RDC locations that exist with an 'OUTBASE_INDICATOR' decoded value for 'REFERENCE'.

This outbase indicator will be a single character to be included in the TMS trip to replace the first digit of the trip number (e.g. MAN-A0123456 instead of MAN-00123456).

This decoded value must exist to enable the new functionality.

Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359661
Summary of Call HAM - Item & Master Pallet Labels
Detail of Fix The new package label format will be available for configuration

The new pallet label format will be available for configuration.

The pallet label printing will be to a laser printer for a PDF document or to a label printer for a Zebra label format.

The new MCS_PALLET_LABEL_FORMAT system parameter will be used to store the Zebra pallet label format.

If this system parameter is not specified, the existing PDF pallet label format will be used.

The supporting information of the new package label will need to be implemented for the carrier tracking and routing.

Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359663
Summary of Call HAM - Create Items when order packed
Detail of Fix Order items will be created for the tracking references when the carrier labels are printed for the van fleet routes.

These order items will be made available as trip items for scanning using MCS in the active depots.

The deletion of tracking references will delete the corresponding order items when the order is unpacked, repacked or unscheduled without retaining pack data.

The corresponding trip items will also be deleted when the order items are deleted.

Any trip items that have been palletised or added to AWB/Consignments in the depots will be removed from the pallets and AWB/Consignments.

Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359664
Summary of Call HAM - Scheduling Engine
Detail of Fix Changes to the Scheduling Engine and Paragon for Van Fleet
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359667
Summary of Call HAM - MCS Control Parameters
Detail of Fix Changed the location screen to display the mcs parameters in a new tab.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359668
Summary of Call HAM - Trip Barcode on Reports
Detail of Fix The HC Shunt Sheet, HC Trip Sheet and HCR Loading Sheet reports will include a barcode for the TRIP ID in format 39 for scanning using MCS.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359670
Summary of Call HAM - MCS General Changes
Detail of Fix Read system params into MCS and hide AWB number.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359671
Summary of Call HAM - MCS Project specific changes
Detail of Fix Pallet Building and Pallet Closure changes.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 359674
Summary of Call HAM - MCS Trans-Ship
Detail of Fix Added Trans Ship functionality for MCS.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0031943

OBS Log Number: 362625
Summary of Call HAM - Item & Master Pallet Label 2
Detail of Fix Amended the reprinting of the label format.

The Service Type will display the carrier service level or the order service level to ensure that a service is displayed depending on the type of routing that has been performed to schedule the order.

Set-up and Configuration No set-up/configuration required


Customer Ref: Inventory Transactions

OBS Log Number: 364431
Summary of Call Inventory Transactions Store Scan Change
Detail of Fix The StoreScan section included extra columns as per the other scan sections. The depot and user columns have been removed from the extract.
Set-up and Configuration No set-up/configuration required


Customer Ref: PO 44010884813

OBS Log Number: 362811
Summary of Call Webservice Label Change
Detail of Fix Changes to Labels
Set-up and Configuration No set-up/configuration required



SUPPORT INCIDENTS

Customer Ref: 360403

OBS Log Number: 360403
Summary of Call VDA4933 and VDA4933 additional matches
Detail of Fix When a 4987 matches to more than one 4933 on the same delivery stop, replace the orders on the trip
Set-up and Configuration No set-up/configuration required


Customer Ref: LOTS

OBS Log Number: 360459
Summary of Call Send address to LOTS in ORD event
Detail of Fix Change to allow address details and contacts to be sent to LOTS
Set-up and Configuration No set-up/configuration required


Customer Ref: Reason Code

OBS Log Number: 361188
Summary of Call Cancelled Item - Reason Code
Detail of Fix Only create SD reason codes for all items on an order when no items sent and none returned.
Set-up and Configuration No set-up/configuration required


Customer Ref: Encrypted sources

OBS Log Number: 361652
Summary of Call Release PL_VERSION
Detail of Fix Release package to assist with version control checks.
Set-up and Configuration No set-up/configuration required


Customer Ref: 362482

OBS Log Number: 362482
Summary of Call Email Information - populated fields
Detail of Fix Amendment to XML outbound generation so contact details not based on comments being null but on email address being populated.
Set-up and Configuration No set-up/configuration required


Customer Ref: Performance Improvements

OBS Log Number: 362723
Summary of Call Performance Improvements
Detail of Fix Reduced the number of times that the standard journeys are assessed for the 'from' location of the orders when calculating payments.
Set-up and Configuration No set-up/configuration required


Customer Ref: Invoice Format

OBS Log Number: 363373
Summary of Call Incorrect Invoice format
Detail of Fix Changes to the BL numbers and the frequency reported- no longer at order level but at gate level within the shipment and invoice
Set-up and Configuration No set-up/configuration required


Customer Ref: INC30189216

OBS Log Number: 363421
Summary of Call File has order header but no details
Detail of Fix When determining if an order is to be included in Zetes file extend test for 'SL' reason code items to exclude the 'X' items that have been split off
Set-up and Configuration No set-up/configuration required


Customer Ref: INC30418115

OBS Log Number: 364473
Summary of Call Report showing wrong data
Detail of Fix Amendment to ITEM_MOVEMENTS_EXTRACT_2 to correct to population of POD confirmed date (column T) on so uses scan date
Set-up and Configuration No set-up/configuration required


Customer Ref: Decode Amendment

OBS Log Number: 364696
Summary of Call Change decode names
Detail of Fix Amendment to shipment extract to use Parts decode where appropriate
Set-up and Configuration No set-up/configuration required


Customer Ref: Scheduling Engine

OBS Log Number: 359457
Summary of Call Scheduling Engine Single Network
Detail of Fix Ensure when roll back performed inside of loop that it is not then also performed outside of the loop.
Set-up and Configuration No set-up/configuration required


Customer Ref: Portal

OBS Log Number: 359518
Summary of Call Portal not reporting shortages
Detail of Fix Changed EPOD interface to ensure quantity set before reason added and also ensure order details sent to LOTS on delivery message.
Set-up and Configuration No set-up/configuration required


Customer Ref: Empties Changes

OBS Log Number: 362440
Summary of Call Rqmts change for Credit acc on empties
Detail of Fix Changes to the finance functionality based on the Empties not providing the references we expected
Set-up and Configuration No set-up/configuration required


Customer Ref: Split Order scanning

OBS Log Number: 362828
Summary of Call Split order scanning delivery trips
Detail of Fix Change to split scanning, to prevent orders being planned on empty stops
Set-up and Configuration No set-up/configuration required


Customer Ref: Support

OBS Log Number: 364191
Summary of Call Debrief issue
Detail of Fix Changes to the shipment extract and removal of validate order when rating a completed trip
Set-up and Configuration No set-up/configuration required


Customer Ref: Trunk Scripts Main

OBS Log Number: 364910
Summary of Call Trunk Scripts added into main stream
Detail of Fix Trunk scripts for Paragon added into main code stream
Set-up and Configuration No set-up/configuration required


Customer Ref: Collection dates/times

OBS Log Number: 365051
Summary of Call Validate order collection dates/times
Detail of Fix The just in time orders will only have their collection date/time windows assessed when the order status is INVALID, VALID or UNSCHEDULED.

A user context will be set when validating the just in time orders for the cost centre of the order unless the calling process has already done so (e.g. Paragon planning).

Set-up and Configuration No set-up/configuration required


Customer Ref: Packaging and Service

OBS Log Number: 359779
Summary of Call Current packaging and Service charge ext
Detail of Fix Report type OWN_CHRGS already in Oracle reporting suite for the packaging charges. Options added to ORS for

1) Service Capture (SRVCS_CAPT)

2) Services including sliding charges (ACC_SRVCS)

3) Accounts (ACC_ACCOUNT).

Set-up and Configuration No set-up/configuration required


Customer Ref: 361243

OBS Log Number: 361243
Summary of Call Export the cost per route
Detail of Fix Add the fields for business data 'Fixed costs by route' to extract suite under type RTE_COSTS.
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.


Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=PATCH_C-TMS_P035&oldid=8090’