CTMS 11.0 ER022-086 - Revision history

StylesC at 12:53, 20 January 2017

2017-01-20T12:53:42Z

@@ Line 5: / Line 5: @@
 |ERNumber=ER022-086
 }}
 {{ERTableHeader}}
@@ Line 159: / Line 172: @@
 <td>Indicates if CC/Customer Completed settings are in use. The existing validation will be performed.</td>
 </tr>
 </table>
 <noinclude>
 [[Category:{{#var:System}} ER]]
 </noinclude>

StylesC at 12:51, 20 January 2017

2017-01-20T12:51:50Z

@@ Line 137: / Line 137: @@
 }}
 {{ERTableFooter}}
 {{ERTableHeader}}

StylesC at 12:35, 20 January 2017

2017-01-20T12:35:23Z

← Older revision		Revision as of 14:35, 20 January 2017
Line 137:		Line 137:
	}}		}}
	{{ERTableFooter}}		{{ERTableFooter}}


	{{ERTableHeader}}		{{ERTableHeader}}
Line 151:		Line 150:
	}}		}}
	{{ERTableFooter}}		{{ERTableFooter}}

	<noinclude>		<noinclude>
	[[Category:{{#var:System}} ER]]		[[Category:{{#var:System}} ER]]
	</noinclude>		</noinclude>

StylesC at 12:34, 20 January 2017

2017-01-20T12:34:21Z

← Older revision		Revision as of 14:34, 20 January 2017
Line 42:		Line 42:
	Unloading Reasons: The order items must have a corresponding reason code for the loading activity at the delivery location.		Unloading Reasons: The order items must have a corresponding reason code for the loading activity at the delivery location.

	Stops: All of the trip stops must have actual arrival		Stops: All of the trip stops must have actual arrival and departure times.
	and departure times.

	Stop Activity: All of the trip stops with orders		Stop Activity: All of the trip stops with orders assigned to them must have actual arrival and departure times.
	assigned to them must have actual arrival and
	departure times.

	Technical Details:		Technical Details:
Line 141:		Line 138:
	{{ERTableFooter}}		{{ERTableFooter}}


			{{ERTableHeader}}
			{{ERTableRow
			\|TRM.sql
			\|Trip Management Package
			\|5.150
			\|339881
			\|-
			\|3
			\|Added new functions for .net ctms system.
			\|Dave Meir
			}}
			{{ERTableFooter}}
	<noinclude>		<noinclude>
	[[Category:{{#var:System}} ER]]		[[Category:{{#var:System}} ER]]
	</noinclude>		</noinclude>

StylesC: Created page with " {{#vardefine:System|CTMS}} {{ERHeader |SystemVersion=CTMS 11.0 |ERNumber=ER022-086 }} {{ERTableHeader}} {{ERTableRow |DATA_ADM_SYSTEM_PARAM_340206...."

2017-01-20T12:29:54Z

Created page with " {{#vardefine:System|CTMS}} {{ERHeader |SystemVersion=CTMS 11.0 |ERNumber=ER022-086 }} {{ERTableHeader}} {{ERTableRow |DATA_ADM_SYSTEM_PARAM_340206...."

New page

{{#vardefine:System|CTMS}}
{{ERHeader
|SystemVersion=CTMS 11.0
|ERNumber=ER022-086
}}

{{ERTableHeader}}
{{ERTableRow
|DATA_ADM_SYSTEM_PARAM_340206.sql
|Data Script
|1.1
|340206
|-
|3
|A new process will be available to automatically update trips to a status of 'COMPLETED'.

This process will be activated by a new system parameter called 'TRM_COMPLETED_SETTINGS' being set to 'Y' for the cost centre of the trip.

The process will not include the existing validation but it will include new validation that can be configured by customer or by cost centre based on the order.

There are 8 new tick boxes that can be configured in the 'Customers' maintenance screen for the customer and/or the cost centre.

These tick boxes will be used to activate the required level of validation that will be required to automatically complete the trips that have a current status of 'PLANNED', 'TENDERED',' ACCEPTED' or 'EN-ROUTE' as they are updated.

A new EDI process can be setup to automatically complete the trips and a range of schedules can be specified to select the trips.

There are 8 new validation checks that can be performed and the flags for the customer will take precedence over the flags for the cost centre when the orders on the trips are assessed.

Note that if the same flag for the customer is not set but it is for the cost centre then that piece of validation will be active.

POC Signature: The order must have a signatory at the loading location and a date for its capture.

POC Quantities: The order lines must have an actual despatched quantity.

Load Reasons: The order items must have a corresponding reason code for the loading activity at the collection location.

POD Signature: The order must have a signatory at the unloading location and a date for its capture.

POD Quantities: The order lines must have an actual delivered quantity.

Unloading Reasons: The order items must have a corresponding reason code for the loading activity at the delivery location.

Stops: All of the trip stops must have actual arrival
and departure times.

Stop Activity: All of the trip stops with orders
assigned to them must have actual arrival and
departure times.

Technical Details:
A new EDI process called 'AUTO_COMPLETE_TRIPS' can be setup as follows:

Direction: Outbound
Cost Centre: As appropriate
Location: As appropriate
Flow Type: PROCESS

Delivery Folder: /webint/{DATABASE}/export
Archive Folder: /webint/{DATABASE}/export
Failures Folder: /webint/{DATABASE}/export

Report Values:
Title: Package Name
Name: PROCESS
Name: Value: TRM.P_AUTO_COMPLETE

Title: Process Name
Name: p_process_name
Value: AUTO_COMPLETE_TRIPS

Parameters:

Param: SCHED_MINUS
Value: -7

Param: SCHED_PLUS
Value: 7
|Dave Meir
}}
{{ERTableRow
|DATA_ADM_SYSTEM_PARAM_CONFIG_340206.sql
|Data Script
|1.1
|"
|"
|"
|"
|"
}}
{{ERTableRow
|AT_REV_COST_CENTRE_340206.sql
|Alter Table Script
|1.1
|"
|"
|"
|"
|"
}}
{{ERTableRow
|AT_ORG_CUSTOMER_340206.sql
|Alter table Script
|1.1
|"
|"
|"
|"
|"
}}
{{ERTableRow
|TRM.sql
|Trip Management Package
|5.151
|"
|"
|"
|"
|"
}}
{{ERTableRow
|INT_XML_MIC.sql
|Microlise Interface Package
|5.139
|"
|"
|"
|"
|"
}}
{{ERTableRow
|CUST_COST.fmx
|Customer/Cost Centre Form
|2.107
|"
|"
|"
|"
|"
}}
{{ERTableFooter}}

<noinclude>
[[Category:{{#var:System}} ER]]
</noinclude>