XFM0012 XF Command - Revision history

Anw: Anw moved page XFM0012 to XFM0012 XF Command

2025-11-27T10:27:53Z

Anw moved page XFM0012 to XFM0012 XF Command

← Older revision	Revision as of 12:27, 27 November 2025
(No difference)

Anw: Categorisation

2025-11-11T15:01:26Z

Categorisation

← Older revision		Revision as of 17:01, 11 November 2025
Line 189:		Line 189:

	'''Process Code (XFMonitor XFM0020)***''' As a rule outbound proceses require a specifed Process Code, the required values are listed above.		'''Process Code (XFMonitor XFM0020)***''' As a rule outbound proceses require a specifed Process Code, the required values are listed above.
	[[Category:EDI]]		<noinclude>[[Category:EDI]]</noinclude>

Anw: Categorisation

2025-11-11T14:56:53Z

Categorisation

← Older revision		Revision as of 16:56, 11 November 2025
Line 189:		Line 189:

	'''Process Code (XFMonitor XFM0020)***''' As a rule outbound proceses require a specifed Process Code, the required values are listed above.		'''Process Code (XFMonitor XFM0020)***''' As a rule outbound proceses require a specifed Process Code, the required values are listed above.
			[[Category:EDI]]

Anw: Split into separate pages

2025-07-01T12:27:27Z

Split into separate pages

Show changes

Anw: Minor formatting change

2025-06-18T08:16:06Z

Minor formatting change

← Older revision		Revision as of 10:16, 18 June 2025
Line 7:		Line 7:
	!Field Name\|\|Description\|\|Options\|\|Generic Value		!Field Name\|\|Description\|\|Options\|\|Generic Value
	\|-		\|-
	\|Package Id **\|\|The unique identifier for this message type – note, you will need to remember this for further setup\|\|10 character free text field\|\|Defined by the client		\|''Package Id **''\|\|The unique identifier for this message type – note, you will need to remember this for further setup\|\|10 character free text field\|\|Defined by the client
	\|-		\|-
	\|Inbound/Outbound/Local **\|\|Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations)\|\|Check box\|\|Defined by the message type		\|''Inbound/Outbound/Local **''\|\|Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations)\|\|Check box\|\|Defined by the message type
	\|-		\|-
	\|Package SQL Code **\|\|The programming instruction to determine which package the EDI will call\|\|Defined by the hard coding of the program\|\|Defined by the message type		\|''Package SQL Code **''\|\|The programming instruction to determine which package the EDI will call\|\|Defined by the hard coding of the program\|\|Defined by the message type
	\|}		\|}
	==='''Command Values'''===		==='''Command Values'''===
	Below is a table of the current commands		Below is a table of the current commands


	'''NB these will increase as new messages are added to the system as required'''		'''NB these will increase as new messages are added to the system as required'''
Line 47:		Line 46:
	\|-		\|-
	\|Stock Snapshot (Include both customer and system rotations and SAP storage locations)(F/S 230465)\|\|Outbound\|\|Additional rotation level dp_edigen_out_st_bal.generate_detail_data dp_edigen_out_st_bal.write_flat_file_dtl This process writes a SD01 and SD02 lines – the SD02 record is a rotation level record.		\|Stock Snapshot (Include both customer and system rotations and SAP storage locations)(F/S 230465)\|\|Outbound\|\|Additional rotation level dp_edigen_out_st_bal.generate_detail_data dp_edigen_out_st_bal.write_flat_file_dtl This process writes a SD01 and SD02 lines – the SD02 record is a rotation level record.
	\|-
	\|}		\|}


	'''Carrier Interface Messages'''		'''Carrier Interface Messages'''
Line 70:		Line 67:
	\|-		\|-
	\|CARR – Carrier Collection Message\|\|Outbound\|\|dp_edigen_out_carr_conf.write_flat_file		\|CARR – Carrier Collection Message\|\|Outbound\|\|dp_edigen_out_carr_conf.write_flat_file
	\|-
	\|}		\|}



	'''Configurable EDI''' '''Inbound'''		'''Configurable EDI''' '''Inbound'''
Line 105:		Line 99:
	\|-		\|-
	\|WLE Held Stock\|\|Dynamic Held Stock Upload\|\|dp_conf_edi_in.wle_held_stock_xfm		\|WLE Held Stock\|\|Dynamic Held Stock Upload\|\|dp_conf_edi_in.wle_held_stock_xfm
	\|-
	\|}		\|}


	'''Outbound '''		'''Outbound '''
Line 118:		Line 110:
	\|-		\|-
	\|Stock Inventory Balances\|\|Outbound\|\|?		\|Stock Inventory Balances\|\|Outbound\|\|?
	\|-
	\|}		\|}


	'''FTP Packages'''		'''FTP Packages'''

Anw: Split into separate pages

2025-06-17T13:58:44Z

Split into separate pages

@@ Line 12: / Line 12: @@
 |-
 |Package SQL Code **||The programming instruction to determine which package the EDI will call||Defined by the hard coding of the program||Defined by the message type
 |}

Anw: Split into separate pages

2025-06-17T13:56:36Z

Split into separate pages

New page

This screen is used to dictate which package is called for each flow. The package id field is user definable, but the ‘Package SQL Code’ is predetermined by the package format.

Once you have entered the package id and the package SQL code, you must then specify whether it is an inbound or outbound flow.

<center>[[Image:EDI-005a.PNG]]</center>
{| class="wikitable" border="1"
!Field Name||Description||Options||Generic Value
|-
|Package Id **||The unique identifier for this message type – note, you will need to remember this for further setup||10 character free text field||Defined by the client
|-
|Inbound/Outbound/Local **||Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations)||Check box||Defined by the message type
|-
|Package SQL Code **||The programming instruction to determine which package the EDI will call||Defined by the hard coding of the program||Defined by the message type
|}