Using the LogiNext Carrier Interface - Revision history

Anw: Minor change

2025-10-29T08:40:07Z

Minor change

← Older revision		Revision as of 10:40, 29 October 2025
Line 1:		Line 1:
	~~{{Incomplete}}~~

	This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.		This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.

Anw: Amended to reflect current implementation, confirmed by @cak 29/10/2025

2025-10-29T08:39:30Z

Amended to reflect current implementation, confirmed by @cak 29/10/2025

← Older revision		Revision as of 10:39, 29 October 2025
Line 101:		Line 101:
	** The Delivery Type is set by the first order that is planned onto the trip.		** The Delivery Type is set by the first order that is planned onto the trip.
	** The structure is sent, without any real details except locations to be visited. There will be no orders on these template trips at this time.		** The structure is sent, without any real details except locations to be visited. There will be no orders on these template trips at this time.
	** {{~~Warning~~}}~~'''TBC:''' Are~~ the trips in the fixed schedule ~~already~~ assigned to LogiNext carrier, ~~at status TENDERED, with a~~ driver and vehicle ~~already set?~~		** {{Note}}Currently the trips in the fixed schedule are not pre-assigned to a LogiNext carrier, and no driver and vehicle is preset.
	* Or manually create a trip and assign to a LogiNext carrier.		* Or manually create a trip and assign to a LogiNext carrier.
	** Select the Delivery Type of the trip from the drop-down list. The list will display only those values that have been configured in the decode list for LogiNext use. No manual entry is allowed.		** Select the Delivery Type of the trip from the drop-down list. The list will display only those values that have been configured in the decode list for LogiNext use. No manual entry is allowed.
Line 140:		Line 140:

	{{Warning}}This interface from LogiNext is currently not in use.		{{Warning}}This interface from LogiNext is currently not in use.
			LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.

	LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.		LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.
Line 157:		Line 158:
	* ANY rejections (or cancellations - see later) will be visible in the Trip list in the Planning screen - the truck icon will be RED.		* ANY rejections (or cancellations - see later) will be visible in the Trip list in the Planning screen - the truck icon will be RED.
	* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.		* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.
			LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.

	LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.		LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.
Line 193:		Line 195:
	If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, LogiNext will be informed of the items on the order, replacing all items and updating the information against them.		If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, LogiNext will be informed of the items on the order, replacing all items and updating the information against them.

	{{~~Warning}}'''TBC:'''~~		{{Note\|* Items messages are not sent to LogiNext after the trip has been set to EN ROUTE
			* There is no "Final send" before cut-off - this was part of the original design, but removed during development with the agreement of the customer.}}
	* Items messages ~~being~~ sent after ~~cutoff?~~
	* Carrier systems updating/not updating?
	* "Final send" before cut-off?

	== Execution ==		== Execution ==
	~~{{Warning}}'''TBC:'''~~ When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.		When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.

	Whilst being executed by the carrier, the carrier systems will pass messages to the LogiNext system around the events that have occurred during the execution. These will be passed onto CTMS and broadly result in the following processing:		Whilst being executed by the carrier, the carrier systems will pass messages to the LogiNext system around the events that have occurred during the execution. These will be passed onto CTMS and broadly result in the following processing:
Line 216:		Line 215:
	** The actual collection time will be noted.		** The actual collection time will be noted.
	** If this is the first order not picked up on this trip, the trip will be set to status EN-ROUTE.		** If this is the first order not picked up on this trip, the trip will be set to status EN-ROUTE.
	** ~~{{Warning}}'''TBC:'''~~ The order will be set as status FAILED.		** The order will be set as status FAILED.
	* Delivered - the carrier has declared that the transport booking has been delivered in full to the delivery location.		* Delivered - the carrier has declared that the transport booking has been delivered in full to the delivery location.
	** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.		** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.
Line 231:		Line 230:
	** The actual delivery time will be noted.		** The actual delivery time will be noted.

	{{Warning}}~~'''TBC:'''~~ Ad Hoc ~~Orders~~		{{Warning}}Ad Hoc Collections (i.e. non-planned collections of empties during a job) are not being executed by the carriers, and no interface exists to process these. This may be added in a later phase.

	*What and ~~how? Very little mention of this~~ in ~~the FS~~.

	{{Note}}		{{Note}}
Line 247:		Line 244:

	[[File:LogiNext-Audit-Trip.png\|800x800px]]		[[File:LogiNext-Audit-Trip.png\|800x800px]]

	~~{{Warning}}'''TBC:''' Following:~~

	Additional information regarding the change of status times, changes of order quantities, etc, which are triggered by the LogiNext interface, can also be viewed on the following standard Audit screens:		Additional information regarding the change of status times, changes of order quantities, etc, which are triggered by the LogiNext interface, can also be viewed on the following standard Audit screens:

Anw: Minor formatting change

2025-07-08T13:21:25Z

Minor formatting change

← Older revision		Revision as of 15:21, 8 July 2025
Line 3:		Line 3:
	This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.		This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.

	=== Overview ===		== Overview ==
	The process automates the interface to and from LogiNext enabled carriers, providing an interface for:		The process automates the interface to and from LogiNext enabled carriers, providing an interface for:

Line 12:		Line 12:
	LogiNext is a 4PL system operated by K+N. They do not offer transport themselves, they offer transport services from other carriers on their behalf. As such, LogiNext is ALSO sending messages to and from those carriers' systems in order to offer orders, confirm acceptance, get debrief information, just like the interface between CTMS and LogiNext systems.		LogiNext is a 4PL system operated by K+N. They do not offer transport themselves, they offer transport services from other carriers on their behalf. As such, LogiNext is ALSO sending messages to and from those carriers' systems in order to offer orders, confirm acceptance, get debrief information, just like the interface between CTMS and LogiNext systems.

	=== Configuration ===		= Configuration =

	==== System Parameters ====		== System Parameters ==
	A system level system parameter “LOGINEXT_ENDPOINT” which will contain the endpoint address for LogiNext.		A system level system parameter “LOGINEXT_ENDPOINT” which will contain the endpoint address for LogiNext.

Line 27:		Line 27:
	[[File:LogiNext-SysParams.png\|800x800px]]		[[File:LogiNext-SysParams.png\|800x800px]]

	==== Decodes ====		== Decodes ==
	A new decode will be created for the delivery types and will be available to be maintained in the [[Imports]] screen, Decodes tab.		A new decode will be created for the delivery types and will be available to be maintained in the [[Imports]] screen, Decodes tab.

Line 37:		Line 37:
	[[File:LogiNext-Decodes.png\|800x800px]]		[[File:LogiNext-Decodes.png\|800x800px]]

	==== Resources ====		== Resources ==
	The LogiNext enabled carriers can be indicated through the flag against the carrier, which is enabled through the [[Resources]] screen, ''Carriers'' tab.		The LogiNext enabled carriers can be indicated through the flag against the carrier, which is enabled through the [[Resources]] screen, ''Carriers'' tab.

	[[File:LogiNext-Carriers.png\|800x800px]]		[[File:LogiNext-Carriers.png\|800x800px]]

	==== Reason Codes ====		== Reason Codes ==
	Reason codes will need to be created to record activity against orders. These can be maintained through the [[Business Data Maintenance\|Business Data]] screen, Reason Codes tab.		Reason codes will need to be created to record activity against orders. These can be maintained through the [[Business Data Maintenance\|Business Data]] screen, Reason Codes tab.

Line 64:		Line 64:
	[[File:LogiNext-ReasonCodes.png\|800x800px]]		[[File:LogiNext-ReasonCodes.png\|800x800px]]

	==== EDI ====		== EDI ==
	A new EDI process will be created to process outbound messages to LogiNext. This is maintained in the [[EDI Maintenance]] screen.		A new EDI process will be created to process outbound messages to LogiNext. This is maintained in the [[EDI Maintenance]] screen.

Line 91:		Line 91:
	\|}		\|}

	=== Operation ===		= Operation =

	==== Planning ====		== Planning ==
	Orders will arrive drip-fed throughout the intervening days, from external systems.		Orders will arrive drip-fed throughout the intervening days, from external systems.

Line 113:		Line 113:
	** As amendments are made (orders added or removed from the trip), these amendments are sent through to the carrier.		** As amendments are made (orders added or removed from the trip), these amendments are sent through to the carrier.

	=== Tendering the Trip to the Carrier ===		== Tendering the Trip to the Carrier ==
	In order to pass the trip over to the Carrier for acknowledgement and acceptance, TENDER the trip.		In order to pass the trip over to the Carrier for acknowledgement and acceptance, TENDER the trip.
	* This is accomplished through setting the status of the trip to TENDERED status. This is not covered in detail in this guide - see [[Planning]] and [[Trip Overview (Waterfall)]] for more information.		* This is accomplished through setting the status of the trip to TENDERED status. This is not covered in detail in this guide - see [[Planning]] and [[Trip Overview (Waterfall)]] for more information.
Line 119:		Line 119:
	* You will not be able to change to TENDERED status without a driver and vehicle.		* You will not be able to change to TENDERED status without a driver and vehicle.

	=== Interface to LogiNext ===		== Interface to LogiNext ==
	When transport bookings are sent to LogiNext, they are combined at the delivery location (the stop number).		When transport bookings are sent to LogiNext, they are combined at the delivery location (the stop number).

Line 133:		Line 133:
	The transport bookings will be organised in the sequence they are organised on the trip in CTMS, through means of a route message through to LogiNext, which will tell LogiNext which transport bookings are to be done on this route, and in which order.		The transport bookings will be organised in the sequence they are organised on the trip in CTMS, through means of a route message through to LogiNext, which will tell LogiNext which transport bookings are to be done on this route, and in which order.

	==== Acceptance by the Carrier ====		== Acceptance by the Carrier ==
	LogiNext will indicate successful acknowledgement of the transport bookings (the stops on the trip).		LogiNext will indicate successful acknowledgement of the transport bookings (the stops on the trip).

Line 162:		Line 162:
	{{Warning}}This interface from LogiNext is currently not in use.		{{Warning}}This interface from LogiNext is currently not in use.

	==== Planning Amendments by You ====		== Planning Amendments by You ==
	Planning manually can change what is passed to LogiNext carriers, adding or removing stops/orders, or even removing the trips completely. Each of these changes will send the details through to LogiNext for acceptance.		Planning manually can change what is passed to LogiNext carriers, adding or removing stops/orders, or even removing the trips completely. Each of these changes will send the details through to LogiNext for acceptance.

Line 184:		Line 184:
	* Status change to DELETED: If the carrier of the trip is found to be a LogiNext-enabled carrier, all transport bookings for this trip will be deleted from LogiNext.		* Status change to DELETED: If the carrier of the trip is found to be a LogiNext-enabled carrier, all transport bookings for this trip will be deleted from LogiNext.

	==== Tag to Asset ====		== Tag to Asset ==
	Tag to Asset is the process of recording the picking of the product to be shipped on orders into transport units (e.g. temp-controlled boxes).		Tag to Asset is the process of recording the picking of the product to be shipped on orders into transport units (e.g. temp-controlled boxes).

Line 199:		Line 199:
	* "Final send" before cut-off?		* "Final send" before cut-off?

	==== Execution ====		== Execution ==
	{{Warning}}'''TBC:''' When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.		{{Warning}}'''TBC:''' When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.

Line 241:		Line 241:
	* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.		* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.

	=== Auditing ===		= Auditing =

	==== User Auditing ====		== User Auditing ==
	Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be displayed in RED.		Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be displayed in RED.

Line 256:		Line 256:
	* New Order screen - Audit tab.		* New Order screen - Audit tab.

	==== System Auditing ====		== System Auditing ==
	The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.		The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.

	{{:Interface Errors - LogiNext Details}}		{{:Interface Errors - LogiNext Details}}

Anw: ER047-005 - 528318 - Added LogiNext information

2025-07-08T11:36:32Z

ER047-005 - 528318 - Added LogiNext information

← Older revision		Revision as of 13:36, 8 July 2025
Line 20:		Line 20:

	The above 2 parameters will be able to be viewed but not modified in the System parameters screen. These will be configured by your implementation teams from Aptean and LogiNext.		The above 2 parameters will be able to be viewed but not modified in the System parameters screen. These will be configured by your implementation teams from Aptean and LogiNext.




	A new carrier level system parameter ALLOW_TRP_DEL_TYPE_UPDATE which will control the updating of the Delivery Type in the Planning screen.		A new carrier level system parameter ALLOW_TRP_DEL_TYPE_UPDATE which will control the updating of the Delivery Type in the Planning screen.
Line 62:		Line 59:
	* SD - Successfully Delivered		* SD - Successfully Delivered
	* SC - Successfully Collected		* SC - Successfully Collected



	In addition, all reason codes expected to be used by the carrier must be set up here. This must be manually done, through comparison with LogiNext and the Carriers' expected reason codes.		In addition, all reason codes expected to be used by the carrier must be set up here. This must be manually done, through comparison with LogiNext and the Carriers' expected reason codes.
Line 106:		Line 101:
	** The Delivery Type is set by the first order that is planned onto the trip.		** The Delivery Type is set by the first order that is planned onto the trip.
	** The structure is sent, without any real details except locations to be visited. There will be no orders on these template trips at this time.		** The structure is sent, without any real details except locations to be visited. There will be no orders on these template trips at this time.
			** {{Warning}}'''TBC:''' Are the trips in the fixed schedule already assigned to LogiNext carrier, at status TENDERED, with a driver and vehicle already set?
	* Or manually create a trip and assign to a LogiNext carrier.		* Or manually create a trip and assign to a LogiNext carrier.
	** Select the Delivery Type of the trip from the drop-down list. The list will display only those values that have been configured in the decode list for LogiNext use. No manual entry is allowed.		** Select the Delivery Type of the trip from the drop-down list. The list will display only those values that have been configured in the decode list for LogiNext use. No manual entry is allowed.
Line 143:		Line 139:
	* When all orders are acknowledged, the trip audit will show this.		* When all orders are acknowledged, the trip audit will show this.

	{{Warning}}This interface is not ~~currently~~ in use.		{{Warning}}This interface from LogiNext is currently not in use.

	LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.		LogiNext will pass this on to the carrier (the delivery associate). The carrier will indicate acceptance or non-acceptance of the transport bookings.
Line 161:		Line 157:
	* ANY rejections (or cancellations - see later) will be visible in the Trip list in the Planning screen - the truck icon will be RED.		* ANY rejections (or cancellations - see later) will be visible in the Trip list in the Planning screen - the truck icon will be RED.
	* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.		* ALL success and failures of messages to and from LogiNext are shown in the the LogiNext Auditing tab of the EDI Interface Errors screen. This will also show the reasons why this has happened. See later for details on checking this audit screen.



	LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.		LogiNext will inform the carrier of the stops on the trip and how they are to be executed. The carrier will resource the trip (identifying the driver and actual vehicle) and send this information to LogiNext, which will be forwarded on to CTMS. CTMS will update the information on the trip.
Line 199:		Line 193:
	If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, LogiNext will be informed of the items on the order, replacing all items and updating the information against them.		If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, LogiNext will be informed of the items on the order, replacing all items and updating the information against them.

	{{Warning}}		{{Warning}}'''TBC:'''

	* Items messages being sent after cutoff?		* Items messages being sent after cutoff?
Line 206:		Line 200:

	==== Execution ====		==== Execution ====
	{{Warning}}When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.		{{Warning}}'''TBC:''' When sent to and accepted by the carrier, the carrier will begin the execution around half an hour before the departure of the trip.

	Whilst being executed by the carrier, the carrier systems will pass messages to the LogiNext system around the events that have occurred during the execution. These will be passed onto CTMS and broadly result in the following processing:		Whilst being executed by the carrier, the carrier systems will pass messages to the LogiNext system around the events that have occurred during the execution. These will be passed onto CTMS and broadly result in the following processing:
Line 222:		Line 216:
	** The actual collection time will be noted.		** The actual collection time will be noted.
	** If this is the first order not picked up on this trip, the trip will be set to status EN-ROUTE.		** If this is the first order not picked up on this trip, the trip will be set to status EN-ROUTE.
			** {{Warning}}'''TBC:''' The order will be set as status FAILED.
	* Delivered - the carrier has declared that the transport booking has been delivered in full to the delivery location.		* Delivered - the carrier has declared that the transport booking has been delivered in full to the delivery location.
	** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.		** Each item on the order will be marked with the quantity as delivered, with an item history that says that this item has been successfully delivered by the carrier.
Line 236:		Line 231:
	** The actual delivery time will be noted.		** The actual delivery time will be noted.

	{{Warning}}Ad Hoc Orders		{{Warning}}'''TBC:''' Ad Hoc Orders

	*What and how? Very little mention of this in the FS.		*What and how? Very little mention of this in the FS.
Line 249:		Line 244:

	==== User Auditing ====		==== User Auditing ====
	Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be ~~underlined~~ in ~~red. This is as per the current trip screen processes and requires no amendment~~.		Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be displayed in RED.

	[[File:LogiNext-Audit-Trip.png\|800x800px]]		[[File:LogiNext-Audit-Trip.png\|800x800px]]

	{{Warning}}		{{Warning}}'''TBC:''' Following:

	Additional information regarding the change of status times, changes of order quantities, etc, which are triggered by the LogiNext interface, can also be viewed on the following standard Audit screens:		Additional information regarding the change of status times, changes of order quantities, etc, which are triggered by the LogiNext interface, can also be viewed on the following standard Audit screens:
Line 264:		Line 259:
	The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.		The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.

	~~[[File~~:~~LogiNext-Audit-~~Interface-~~Errors.png\|800x800px]]~~		{{:Interface Errors - LogiNext Details}}

	~~The screen will display the details of all records from the new~~ LogiNext ~~audit detail described above.~~

	~~You can filter the search using the search criteria in the top of the tab page and clicking '''Search'''.~~

	~~You can reprocess the currently highlighted record by pressing the '''Reprocess''' button, this will then invoke the reprocessing function~~

	~~Only failed outbound messages will be available to be reprocessed and an error will be shown if any other type of record is selected for reprocessing.~~

	~~{{Note~~}}~~You will not be able to edit data in this screen any errors with trips should be rectified in the planning screen.~~

Anw: ER047-005 - 528318 - Added LogiNext information

2025-07-08T11:24:47Z

ER047-005 - 528318 - Added LogiNext information

Show changes

Anw: In progress

2025-07-08T08:31:24Z

In progress

Show changes

Anw: In progress

2025-07-07T15:02:39Z

In progress

New page

{{Incomplete}}

This guide is intended to show the features, configuration and operation of the LogiNext carrier interface within CTMS.

=== Overview ===
The process automates the interface to and from LogiNext enabled carriers, providing an interface for:

* Tendering Trips.
* Acceptance of orders on trips.
* Execution of trips.
* Automatic debrief of trips from information entered into LogiNext systems.

=== Configuration ===

==== System Parameters ====
A system level system parameter “LOGINEXT_ENDPOINT” which will contain the endpoint address for LogiNext.

A new system level system parameter “LOGINEXT_API_TOKEN” which will contain the API token for LogiNext.

The above 2 parameters will be able to be viewed but not modified in the System parameters screen.

A new carrier level system parameter ALLOW_TRP_DEL_TYPE_UPDATE which will control the updating of the Delivery Type in the Planning screen.

The above parameter will be available for modification in the System parameters screen.

==== Decodes ====
A new decode will be created for the delivery types and will be available to be maintained in the imports screen decodes tab.

==== Resources ====
The LogiNext enabled carriers can be indicated through the flag agaist the carrier, which is enabled through the Resources screen, Carriers tab.

==== Reason Codes ====
Reason codes will need to be created to record activity against orders. These will be at item level for the following.

* SI - INSCANNED
* SO - OUTSCANNED
* HO - HANDEDOVER
* OC – CLOSED
* OACK – Order Acknowledged
* OA – Order Accepted
* OR – Order Rejected
* OC – Order Cancelled

==== EDI ====
A new EDI process will be created to process outbound messages to LogiNext.

[[File:LogiNext-EDI-Maintenance.png|800x800px]]

The flow will have a flow type of “PROCESS” and will run at regular intervals – in the above example the flow is set to run every 2 minutes.

The flow will have report values which specify the process being called.

[[File:LogiNext-EDI-Maintenance2.png|800x800px]]

=== Operation ===

==== Planning ====
When creating a trip, the carrier is identified. This may be a LogiNext carrier.

The planning screen will be amended to allow the update of the DEL_TYPE on the trip if the system parameter is currently active, for LogiNext carriers.

The Delivery type on Trip Detail Tab of the Planning screen will be changed to a drop down which will display the values from the new decoded data.

A change will also be made to the TRM package to allocate the decoded type when the first order is added to the trip, if no decode is found the delivery type of the order will be used.

The user will only be allowed to select a value from the list – no manual entry will be allowed.

==== Tag to Asset ====
The Tag to Asset process will be amended to allow T2A scanning at TENDERED status without raising errors.

==== Execution ====
When the status of a trip is changed, a trigger will fire. The trigger will be amended in the following way:

* Status move from PLANNED to TENDERED, if the carrier of the trip is found to be a LogiNext enabled carrier and there is not a currently unprocessed message to the same type for the same trip a new control record will be created to record the status change, the event type of this record will be set to TRP. This will be the only trip message sent to LogiNext.
* Status move from TENDERED back to PLANNED, if the carrier of the trip is found to be a LogiNext enabled carrier and there is not a currently unprocessed message to the same type for the same trip a new control record will be created to record the status change. The event type of this record will be set to TRPC.
* Status move to DELETED, if the carrier of the trip is found to be a LogiNext enabled carrier and there is not a currently unprocessed message to the same type for the same trip a series or ORDR control records will be created to record the status change and the order being removed from the trip

==== Amendment ====
When the details of a trip are changed, a further trigger will fire The trigger will be amended in the following way:

* If the carrier of a trip is changed from a LogiNext enabled carrier to a non-LogiNext enabled carrier, a control record will also be written to indicate the carrier change as all orders associated with the trip will need to be cancelled. The event type of this record will be set to TRPC.
* If the carrier changed from a non LogiNext carrier to a LogiNext carrier a control record will be created indicating the trip should be processed and sent to LogiNext. The event type of this record will be set to TRP.
* If the carrier of the trip is changed to a different LogiNext carrier a control record will be created indicating the trip should be processed and sent to LogiNext. The event type of this record will be set to TRPX.

'''Note'''. Any changes made to a trip or its orders after the trip has been set to EN-ROUTE status will not be communicated to LogiNext this must be done by calling the control tower to inform them of the changes.

When the orders are added to or removed from a trip a trigger will fire, the trigger will be amended in the following way:

* If an order is added to a LogiNext trip before the status of the trip is changed to EN-ROUTE a control record will be created to send the order details to LogiNext. The event type of this record will be set to ORDA.
* If an order is removed from a LogiNext trip, a control record will be written to indicate the order is cancelled. An order record will be sent to LogiNext in this case. The event type of this record will be set to ORDR.
* If all orders are removed from a trip, a control record will also be written to indicate the status change, as all orders associated with the trip will need to be cancelled. The event type of this record will be set to TRPC.

When planned orders are amended a trigger will fire, the trigger will be amended in the following way:

* If an item is removed from an order, an item is added to an order or the quantities are changed on any item on an order, a control record will be written to indicate the order has been amended and an order update record will be sent to LogiNext in this case. The event type of this record will be set to ORDC.

In all cases the trip will be checked to ascertain if a LogiNext message is required.

==== Planning Updates ====

=== Auditing ===

==== User Auditing ====
Any errors are recorded in the processing of the LogiNext trips, these will be displayed in the Comments/Errors tab and the truck icon in the trip tree will be underlined in red. This is as per the current trip screen processes and requires no amendment.

[[File:LogiNext-Audit-Trip.png|800x800px]]

==== System Auditing ====
The detailed system auditing can be seen in the Interface Errors screen, on the LogiNext tab.

[[File:LogiNext-Audit-Interface-Errors.png|800x800px]]

The screen will display the details of all records from the new LogiNext audit detail described above.

The user can filter the search using the search criteria in the top of the tab page and clicking '''Search'''.

The user can reprocess the currently highlighted record by pressing the '''Reprocess''' button, this will then invoke the reprocessing function

Only failed outbound messages will be available to be reprocessed and an error will be shown if any other type of record is selected for reprocessing.

The user will not be able to edit data in this screen any errors with trips should be rectified in the planning screen.