B2B Gateway

Back Next

Example of an inbound interface file for EDIFACT messages

The inbound interface file for EDIFACT messages contains a root element, message type element, delimiters, loop elements, segment elements, and data elements.

The root element for an inbound interface file is specified as

to identify the message as an EDIFACT message. In this example, the message type element

<TS_ORDERS>

identifies the message as message type ORDERS.

<interchange>
	<delimiters>
		<field_separator>+</field_separator>
		<segment_separator>'</segment_separator>
		<composite_separator>:</composite_separator>
		<escape_character>?</escape_character>
	</delimiters>
	<UNA>
		<R01>:</R01>
		<R02>+</R02>
		<R03>.</R03>
		<R04>?</R04>
		<R05> </R05>
		<R06>'</R06>
	</UNA>
	<UNB>
		<R01>
			<R01>UNOC</R01>
			<R02>3</R02>
		</R01>
		<R02>
			<R01>380948745PLA001</R01>
			<R02>ZZZ</R02>
		</R02>
		<R03>
			<R01>0607047800019</R01>
			<R02>14</R02>
		</R03>
		<R04>
			<R01>160525</R01>
			<R02>1606</R02>
		</R04>
		<R05>50105153010903</R05>
		<R07>ORDERS</R07>
	</UNB>
	<TS_ORDERS>
		<UNH>
			<R01>1</R01>
			<R02>
				<R01>ORDERS</R01>
				<R02>D</R02>
				<R03>97A</R03>
				<R04>UN</R04>
			</R02>
		</UNH>
		<BGM>
			<R01>
				<R01>105</R01>
			</R01>
			<R02>
				<R01>?+4201138193</R01>
			</R02>
			<R03>9</R03>
		</BGM>
		<DTM>
			<R01>
				<R01>4</R01>
				<R02>20160425</R02>
				<R03>102</R03>
			</R01>
		</DTM>
		<DTM>
			<R01>
				<R01>2</R01>
				<R02>20160509</R02>
				<R03>102</R03>
			</R01>
		</DTM>
		<DTM>
			<R01>
				<R01>137</R01>
				<R02>20160525</R02>
				<R03>102</R03>
			</R01>
		</DTM>
		<LOOP_2>
			<NAD>
				<R01>SU</R01>
				<R02>
					<R01>1110003840</R01>
					<R02></R02>
					<R03>92</R03>
				</R02>
			</NAD>
		</LOOP_2>
		<LOOP_2>
			<NAD>
				<R01>BY</R01>
				<R02>
					<R01>887243</R01>
					<R02></R02>
					<R03>91</R03>
				</R02>
			</NAD>
		</LOOP_2>
		<LOOP_2>
			<NAD>
				<R01>ST</R01>
				<R02>
					<R01>893186</R01>
					<R02></R02>
					<R03>91</R03>
				</R02>
			</NAD>
		</LOOP_2>
		<LOOP_7>
			<CUX>
				<R01>
					<R01>2</R01>
					<R02>PLN</R02>
					<R03>9</R03>
				</R01>
			</CUX>
		</LOOP_7>
		<LOOP_28>
			<LIN>
				<R01>1001</R01>
				<R02></R02>
				<R03>
					<R01></R01>
					<R02>VP</R02>
				</R03>
			</LIN>
			<PIA>
				<R01>5</R01>
				<R02>
					<R01>?+04705201</R01>
					<R02>BP</R02>
				</R02>
			</PIA>
			<PIA>
				<R01>5</R01>
				<R02>
					<R01>1 Handsets</R01>
					<R02>EN</R02>
				</R02>
			</PIA>
		</LOOP_28>
		<UNS>
			<R01>S</R01>
		</UNS>
		<UNT>
			<R01>13</R01>
			<R02>72</R02>
		</UNT>
	</TS_ORDERS>
	<UNZ>
		<R01>1</R01>
		<R02>50105153010903</R02>
	</UNZ>
</interchange>

If you trace through the hierarchy of the interface file, you can see that there are multiple interchanges. The hierarchy reflects the structure of the relevant message type, the schema, and the type of information that the customer sent.

You can pass the data from this interface file to a backend system for further processing.

Interface files for EDI X12 and EDIFACT messages

Download Guide

Watch

Comments

Cloud B2B Gateway Homepage