EDI Maintenance - Revision history

Anw: Added Webservice API EDI processes

2026-03-06T09:22:08Z

Added Webservice API EDI processes

← Older revision		Revision as of 11:22, 6 March 2026
Line 407:		Line 407:

	A list of applicable report values is shown here: [[EDI Process Report Values]].		A list of applicable report values is shown here: [[EDI Process Report Values]].

			=== EDI Trip Order XML Webservices Configuration ===
			{{:EDI Trip Order XML Webservices Configuration}}

Anw: /* Creating Processes */ Updated

2026-03-06T08:56:56Z

Creating Processes: Updated

← Older revision		Revision as of 10:56, 6 March 2026
Line 228:		Line 228:
	\|-		\|-
	\|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API		\|DP_EXPORT_EVENTS.PROCESS_XML_OUTBOUND_API
	\|		\|The Trip/Order XML Outbound process. This should be named "API_EVENTS"
	\|-		\|-
	\|DP_FINANCE.D365_EXPORT		\|DP_FINANCE.D365_EXPORT

Anw: Minor formatting change

2025-07-31T15:03:59Z

Minor formatting change

← Older revision		Revision as of 17:03, 31 July 2025
Line 178:		Line 178:

	There are many processes, mostly for a very specific reason or bespoke processes. A list of processes follows. Note that this list if evolving and may not be complete:		There are many processes, mostly for a very specific reason or bespoke processes. A list of processes follows. Note that this list if evolving and may not be complete:
	{\| class="wikitable"		{\| class="wikitable apt-searchable" border="1"
	!Process		!'''Process'''
	!Notes		!'''Notes'''
	\|-		\|-
	\|ACC.GENERATE_WAREHOUSE_CHARGES		\|ACC.GENERATE_WAREHOUSE_CHARGES

Anw: Updated

2025-07-31T13:33:27Z

Updated

Show changes

Anw: Updated

2025-07-30T10:37:31Z

Updated

← Older revision		Revision as of 12:37, 30 July 2025
Line 26:		Line 26:
	!Field !! Description		!Field !! Description
	\|-		\|-
	\|Process Name\|\| This should indicate the nature of the job so it may be identified in the screen. Required.		\|''Process Name''\|\| This should indicate the nature of the job so it may be identified in the screen. Required.
	\|-		\|-
	\|Filename Format\|\| This indicates how any files created or required by the process are names, for outbound files, the system will add the system date and time to ensure a unique filename is always generated. Required.		\|''Filename Format''\|\| This indicates how any files created or required by the process are names, for outbound files, the system will add the system date and time to ensure a unique filename is always generated. Required.
	\|-		\|-
	\|Customer\|\| Enter the Customer required using the Drop Down List. Optional.		\|''Customer''\|\| Enter the Customer required using the Drop Down List. Optional.
	\|-		\|-
	\|Cost Centre Code\|\| The cost centre code may be used when the process is checking parameter values and may be matched to orders or trips to identify if the process should be running. Required.		\|''Cost Centre Code''\|\| The cost centre code may be used when the process is checking parameter values and may be matched to orders or trips to identify if the process should be running. Required.
	\|-		\|-
	\|~~Direction\|~~\| The ~~direction is defined as outbound or inbound. This will indicate if the process in bringing~~ data ~~into C-TMS or sending data out of C-TMS~~. ~~Required~~.		\|''Location''
			\|The location may be used to specify selection of data from a particular location code. A lookup is provided.
	\|-		\|-
	\|~~Flow Type~~\|\| This ~~indicates~~ the ~~type~~ of ~~process, there are several different options discussed later~~. Required.		\|''Direction''\|\| The direction is defined as outbound or inbound. This will indicate if the process in bringing data into C-TMS or sending data out of C-TMS. Required.
	\|-		\|-
	\|~~Frequency~~ Type\|\| ~~Frequency type~~ indicates ~~how often~~ the process ~~is run~~, are ~~regular interval or specific time~~. Required.		\|''Flow Type''\|\| This indicates the type of process, there are several different options discussed later. Required.
	\|-		\|-
	\|~~Interval Length~~\|~~\| Interval length~~ indicates the regular interval. Required.		\|''Frequency Type''
			\|Frequency type indicates how often the process is run, are regular interval or specific time. Required.
	\|-		\|-
	\|~~Send DEL Message~~ \|~~\| If this box~~ is ~~checked then this can create an ARR message when the actual arrive times are fully entered~~		\|''Process Time''
			\|Only available if selecting ''Frequency Type'' of ''Specific Time''. The time at which the process is to run.
	\|-		\|-
	\|~~Send ARR Message~~ \|~~\| If this box is checked then this can create a DEL message when~~ the ~~order~~ to ~~deliver quantities are fully entered~~		\|''(Day Selection)''
			\|Only available if selecting ''Frequency Type'' of ''Specific Time''. Check ''All Days'', or check the days on which you want the process to run.
	\|-		\|-
	\|~~Delivery Folder~~ \|~~\| When~~ the ~~file has been created this is~~ the ~~directory that~~ the ~~file will sit in until it has been picked up~~		\|''Interval Length''
			\|Only available if selecting ''Frequency Type'' of ''Regular Interval''. Interval length indicates the regular interval. Enter the number , and then the unit (''Seconds, Minutes, Hours, Days, Monthly''). Required.
	\|-		\|-
	\|~~Archive Folder~~ \|\| ~~When~~ the ~~file has been picked up by the relevant source successfully the file gets moved to this directory~~		\|''Interval Length''\|\| Interval length indicates the regular interval. Required.
	\|-		\|-
	\|~~Failures folder~~ \|\| ~~The directory of any files that failed to upload~~		\|''Send DEL Message''\|\| If this box is checked then this can create an ARR message when the actual arrive times are fully entered
	\|-		\|-
	\|~~Acknowledgment Folder~~ \|\| ~~The directory for an acknowledgment~~ message to ~~sent to~~		\|''Send ARR Message''\|\| If this box is checked then this can create a DEL message when the order to deliver quantities are fully entered
	\|-		\|-
	\|Send ACK? \|\| The box is checked if the Acknowledgment of an inbound flow is requested. The Acknowledgment will then been sent to folder to be picked up by the relevant source		\|''Delivery Folder''\|\| When the file has been created this is the directory that the file will sit in until it has been picked up
			\|-
			\|''Archive Folder'' \|\| When the file has been picked up by the relevant source successfully the file gets moved to this directory
			\|-
			\|''Failures folder'' \|\| The directory of any files that failed to upload
			\|-
			\|''Acknowledgment Folder'' \|\| The directory for an acknowledgment message to sent to
			\|-
			\|''Send ACK?'' \|\| The box is checked if the Acknowledgment of an inbound flow is requested. The Acknowledgment will then been sent to folder to be picked up by the relevant source
	\|}		\|}

Line 63:		Line 76:
	!Field !! Description		!Field !! Description
	\|-		\|-
	\|Process Time \|\| This option is only visible if the Frequency Type has been set to ‘Specific Time’. The user can simply enter the time that the flow should be run. Also the checkboxes can be flagged for the required days of the week		\|''Process Time''\|\| This option is only visible if the Frequency Type has been set to ‘Specific Time’. The user can simply enter the time that the flow should be run. Also the checkboxes can be flagged for the required days of the week
	\|-		\|-
	\|Status \|\| This is not an editable field and tells the user if the Flow is running or has been stopped		\|''Status''\|\| This is not an editable field and tells the user if the Flow is running or has been stopped
	\|-		\|-
	\|Last Run Date \|\| This tells the user the Date and time the process last ran		\|''Last Run Date''\|\| This tells the user the Date and time the process last ran
	\|-		\|-
	\|Next Run Date \|\| This is the date and time the flow is due to run next		\|''Next Run Date''\|\| This is the date and time the flow is due to run next
	\|-		\|-
	\|'''Start''' / '''Stop''' Buttons \|\| Stops and starts the process flow. Please note that only the user that started the process can stop it		\|'''Start''' / '''Stop''' Buttons \|\| Stops and starts the process flow. Please note that only the user that started the process can stop it

Anw: Updated list of EDI flows

2024-06-06T07:36:35Z

Updated list of EDI flows

← Older revision		Revision as of 09:36, 6 June 2024
Line 77:		Line 77:
	The flow types available to select are listed below:		The flow types available to select are listed below:
	* EXPORT		* EXPORT
	* FORD_EDI_IN		* FORD_EDI_IN - bespoke EDI process
	* MILE_XML		* MILE_XML
	* MILK_ROUND		* MILK_ROUND - generation of milk rounds
	* ORD_COLL_XML		* ORD_COLL_XML
	* ORD_OR3		* ORD_OR3
	* ORD_XML		* ORD_XML
	* ORD_XML_OUT		* ORD_XML_OUT
	* ORS		* ORS - run an ORS report
	* PLUTO_ACTUALS		* PLUTO_ACTUALS
	* POD_XML		* POD_XML
	* PROCESS		* PROCESS - trigger a process
	* PULSE_ORDERS		* PULSE_ORDERS
	* REPORT		* REPORT - run a report
	* SCN		* SCN
	* SESSION_XML		* SESSION_XML - import sessions
	* STS_XML		* STS_XML
	* TRACK_IMPORT		* TRACK_IMPORT
	* TRIP_ORD_XML		* TRIP_ORD_XML
	* TRIP_XML		* TRIP_XML
	* UNISON_FLAT		* UNISON_FLAT - Legacy WMS flat-file import process

	For running specific extracts and processes, PROCESS should be used. For automatically running reports, use the REPORTS type.		For running specific extracts and processes, PROCESS should be used. For automatically running reports, use the REPORTS type.

Anw: Updated list of EDI flows

2024-06-05T11:23:32Z

Updated list of EDI flows

@@ Line 75: / Line 75: @@
-The flow types available to select are listed below.
+The flow types available to select are listed below:
+* EXPORT
-<center>[[Image:edi_maint_2.png]]</center>
+* FORD_EDI_IN
+* MILE_XML
 For running specific extracts and processes, PROCESS should be used. For automatically running reports, use the REPORTS type.

Anw: Merged from training document

2024-05-21T14:49:03Z

Merged from training document

Show changes

Anw: Minor correction

2024-05-14T09:30:48Z

Minor correction

← Older revision		Revision as of 11:30, 14 May 2024
Line 1:		Line 1:
	~~MAINTENANCE - EDI Interface~~

	The EDI interface screen is accessed from the Interface menu.		The EDI interface screen is accessed from the Interface menu.

Anw: EDI MAINT moved to EDI Maintenance

2024-05-14T09:28:04Z

EDI MAINT moved to EDI Maintenance

← Older revision	Revision as of 11:28, 14 May 2024
(No difference)