ER CTMS 048-025: Difference between revisions

From Calidus HUB
(Created page with "<!-- MEDIA LANDSCAPE YES --> {{#vardefine:System|CTMS}} {{#vardefine:SystemVers|12.0}} {{#vardefine:ERPatch|048}} {{#vardefine:ERNumber|025}} {{ERHeader |SystemVersion={{#var:System}} {{#var:SystemVers}} |ERNumber=ER {{#var:System}} {{#var:ERPatch}}-{{#var:ERNumber}} }} {| class="wikitable" border="1" width="100%" |- bgcolor="silver" !Module !! Program Name !! Ver !! Call/Iss !! Client Ref !! Pr'ty !! Remarks |- |DATA_ADM_SYSTEM_PARAM_810540.sql |Data Script |1.1 |810...")
 
No edit summary
Line 17: Line 17:
|1.1
|1.1
|810540
|810540
|
|&#45;
|
|1
|
|The system parameter ‘LOOKUP_FOR_ROUTE_CODES’ has a new value of ‘V’ to enable the route code to be validated from the list of values.
The orders will be provided with a, ‘ORDER_WMS_STATUS’, ‘RUN_NUMBER’ and a ‘DROP_NO’ by MuleSoft to be used in the scheduling engine.
The WMS status will control the type of automatic scheduling that will be performed:
Pre-invoiced (‘Open’) orders will refer to the advised run number and drop number to find a route for the trip and the validation of the route will not apply. The advised drop number will be used instead of the drop number of the route details for the location for the run number.
Post-invoiced (‘Invoiced’) orders will search for the next available route and the validation of the route will apply. The advised drop number will be used instead of the drop number of the route details for the location for the run number.
The next available route will be found for an order that does not have a ‘RUN_NUMBER’, for example for a rebooked order.
|-
|-
|DATA_IMP_DECODE_ENTRY_810540.sql
|DATA_IMP_DECODE_ENTRY_810540.sql

Revision as of 16:44, 22 January 2026




Aptean Logo.png


EMERGENCY RELEASE - CTMS 12.0


RELNOTE ER CTMS 048-025

Module Program Name Ver Call/Iss Client Ref Pr'ty Remarks
DATA_ADM_SYSTEM_PARAM_810540.sql Data Script 1.1 810540 - 1 The system parameter ‘LOOKUP_FOR_ROUTE_CODES’ has a new value of ‘V’ to enable the route code to be validated from the list of values.

The orders will be provided with a, ‘ORDER_WMS_STATUS’, ‘RUN_NUMBER’ and a ‘DROP_NO’ by MuleSoft to be used in the scheduling engine. The WMS status will control the type of automatic scheduling that will be performed: Pre-invoiced (‘Open’) orders will refer to the advised run number and drop number to find a route for the trip and the validation of the route will not apply. The advised drop number will be used instead of the drop number of the route details for the location for the run number. Post-invoiced (‘Invoiced’) orders will search for the next available route and the validation of the route will apply. The advised drop number will be used instead of the drop number of the route details for the location for the run number. The next available route will be found for an order that does not have a ‘RUN_NUMBER’, for example for a rebooked order.

DATA_IMP_DECODE_ENTRY_810540.sql Data Script 1.1 " " " "
DATA_ORS_MASTER_DATA_810540.sql Data Script 1.1 " " " "
DATA_REP_REPORT_810540.sql Data Script 1.1 " " " "
DATA_REP_REPORT_PARAM_810540.sql Data Script 1.1 " " " "
T_SCH_ORD_AUDIT.sql Trigger 5.22 " " " "
DP_3PL_SCHED.sql 3PL Scheduling Engine Package 5.49 " " " "
DP_CSV6.sql CSV Export Package 1.48 " " " "
DP_CTMS_IMPORT.sql API Import Package 5.64 " " " "
DP_ORS_FUNCS.sql ORS Functions Package 5.41 " " " "
TRM.sql Trip Management Package 5.242 " " " "
PLANNING.fmx Planning Screen 1.172 " " " "


New Parameters
Parameter Name Config Level Setting Value Result
LOOKUP_FOR_ROUTE_CODES SYSTEM N A button for the list of values for the route codes for the trip will not be displayed in the Planning screen.
LOOKUP_FOR_ROUTE_CODES SYSTEM V A button for the list of values for the route codes for the trip will be displayed in the Planning screen and a valid route code must be entered.
LOOKUP_FOR_ROUTE_CODES SYSTEM Y A button for the list of values for the route codes for the trip will be displayed in the Planning screen.