艾默生Emerson EDI需求分析

艾默生Emerson是一家全球领先的工程技术和解决方案提供商。该公司总部位于美国，成立于1890年，经过多年的发展，已经发展成为一个多元化的跨国企业，业务遍及工业、商业和消费者市场。艾默生提供各种产品和服务，包括自动化解决方案、商业与工业自动化技术、控制技术、测量仪器、流体控制、电力系统、通信网络、加热、通风和空调系统等。

艾默生Emerson致力于帮助客户优化生产效率、提高能源效率、改善设备可靠性，并且致力于可持续发展。该公司的产品和解决方案广泛应用于各个领域，包括工业制造、化工、石油与天然气、电力、制药、食品与饮料等。

本文将为大家介绍艾默生Emerson EDI项目中需要传输的业务单据类型，了解如何通过知行之桥EDI系统与艾默生Emerson建立EDI连接。

艾默生Emerson EDI 需求分析

报文标准：X12

X12标准是由美国国家标准协会(ANSI)于1979年特许的认可标准委员会X12(也称为ASC X12)开发和维护的。供应商与艾默生Emerson之间传输的业务单据都需要遵循这个标准。

业务类型：

EDI 810 Invoice发票（V1.0）
EDI 850 Purchase Order 采购订单（V5.1）
EDI 855 PO Acknowledgement采购订单确认 (V1.0)
EDI 856 Advanced Ship Notice提前发货通知 (V3.0)
EDI 860 Purchase Order Change采购订单变更 (V1.0)
EDI 997 Functional Acknowledgement功能性确认 (V1.0)

以下是一个810发票示例报文:

ISA|00|          |00|          |ZZ|EMR            |ZZ|ABCCO          |081202|1311|<|00502|230414746|0|T|>~
GS|PO|EMR1601000|ABCCO|20081201|1311170|249641407|X|005020~
ST|850|762443921~
BEG|00|BK|16011111666|25|20081101|EMR123456ABC|NA||||03~
CUR|BY|CAD|1.025||||AAY|20081115|112500~
REF|06||160~
REF|S3|EMR850V5.1~
FOB|DF|||01|EXW|ZZ|Freight Term Named Place|BY|INCO2000 EXM~
ITD||||||||||||NET30~
N9|L1|PO Header Instructions to Supplier~
MTX|OTH|HEADER INSTRUCTIONS TO SUPPLIER|HEADER INSTRUCTIONS TO SUPPLIER, CONTINUED IF NEEDED~
N1|VN|ABC SUPPLIER|93|160123456~
N2|SUPPLIER NAME CONTINUED~
N3|ADDRESS LINE 1|ADDRESS LINE 2~
N3|ADDRESS LINE 3|ADDRESS LINE 4~
N4|APODACA||66600|MX|93|X160S|NLE~
PER|SU|Supplier Contact Name|TE|314-555-2345|FX|314-555-1234|EM|contact.name@supplier.com~
N1|SO|EMERSON DIVISION NAME|93|160SO~
N2|SOLD-TO NAME CONTINUED~
N3|SO ADDRESS LINE 1|SO ADDRESS LINE 2~
N3|SO ADDRESS LINE 3|SO ADDRESS LINE 4~
N4|SAINT LOUIS||63136|US|93|X160SO|MO~
PER|BD|Sold-To Contact Name|TE|314-555-4567|FX|314-555-3456|EM|contact.name@soldto.com~
N1|BT|EMERSON DIVISION NAME|93|160BT~
N2|BILL-TO NAME CONTINUED~
N3|BT ADDRESS LINE 1|BT ADDRESS LINE 2~
N3|BT ADDRESS LINE 3|BT ADDRESS LINE 4~
N4|SAINT CHARLES||63104|US|93|X160BT|MO~
PER|BD|BillTo Contact Name|TE|314-555-6789|FX|314-555-5678|EM|contact.name@billto.com~
N1|CA|FED EX~
PO1|1|5|EA|3.15|UM|SW|EMR456789|VX|SUPP456789|BE|1.1~
PID|F||||EMERSON ITEM DESCRIPTION TEXT~
MEA|WT|U|50|LB~
TC2|A|HTS123~
TC2|Z|E122~
TD4|HAZ|||Hazardous Class Description Text~
MTX|ORI|DETAIL LINE INSTRUCTIONS TO SUPPLIER|DETAIL LINE INSTRUCTIONS TO SUPPLIER, CONTINUED IF NEEDED~
TXI|ZZ|||||1~
N1|ST|EMERSON DIVISION NAME|93|160ST~
N2|SHIP-TO NAME CONTINUED~
N3|ST ADDRESS LINE 1|ST ADDRESS LINE 2~
N3|ST ADDRESS LINE 3|ST ADDRESS LINE 4~
N4|SAINT PETERS||63376|US|93|X160ST|MO~
REF|4C|Location123~
REF|KE|Kanban456~
PER|BD|Ship-To Contact Name|TE|636-555-1234|FX|636-555-2345|EM|contact.name@shipto.com~
PER|RQ|Buyer Name~
SCH|5|EA|||112|20081210||010|20081209|||1S~
PO1|2|10|EA|5.25|UM|SW|EMR567890|VX|SUPP567890|BE|2.2~
PID|F||||EMERSON ITEM DESCRIPTION TEXT~
MEA|WT|U|12|LB~
TC2|A|HTS123~
TC2|Z|E122~
TD4|HAZ|||Hazardous Class Description Text~
MTX|ORI|DETAIL LINE INSTRUCTIONS TO SUPPLIER|DETAIL LINE INSTRUCTIONS TO SUPPLIER, CONTINUED IF NEEDED~
TXI|ZZ|||||1~
N1|ST|EMERSON DIVISION NAME|93|160ST~
N2|SHIP-TO NAME CONTINUED~
N3|ST ADDRESS LINE 1|ST ADDRESS LINE 2~
N3|ST ADDRESS LINE 3|ST ADDRESS LINE 4~
N4|SAINT PETERS||63376|US|93|X160ST|MO~
REF|4C|Location123~
REF|KE|Kanban456~
PER|BD|Ship-To Contact Name|TE|636-555-1234|FX|636-555-2345|EM|contact.name@shipto.com~
PER|RQ|Buyer Name~
SCH|7|EA|||112|20081215||||||2S1~
N1|ST|EMERSON DIVISION NAME|93|160ST~
N2|SHIP-TO NAME CONTINUED~
N3|ST ADDRESS LINE 1|ST ADDRESS LINE 2~
N3|ST ADDRESS LINE 3|ST ADDRESS LINE 4~
N4|SAINT PETERS||63376|US|93|X160ST|MO~
REF|4C|Location123~
REF|KE|Kanban456~
PER|BD|Ship-To Contact Name|TE|636-555-1234|FX|636-555-2345|EM|contact.name@shipto.com~
PER|RQ|Buyer Name~
SCH|3|EA|||112|20081220||||||2S2~
CTT|1~
SE|76|762443921~
GE|1|249641407~
IEA|1|230414746~

EDI报文每一行开头（2-3个字符组成）叫做segment节点，代表了特定的业务含义，例如BEG代表报文的开始以及一些主信息，DTM代表时间信息，N1代表实体信息（ship-to、ship-from、bill-to等等）。企业需要获取的业务数据被分门别类地存放在这些字符中，通过数据元素分隔符分隔开来。

对供应商而言，处理这样的文件并非易事，因此需要专业的EDI软件产品对这些数据进行格式转换，从而使数据更加清晰可读。

知行之桥EDI系统实现艾默生Emerson EDI 需求

建立EDI 连接通道

知行之桥EDI系统支持目前国际通用的大多数传输协议，如AS2、OFTP、SFTP等。用户可以通过相应的MFT（可控文件传输）端口，进行可视化的配置。

报文格式转换

由于艾默生Emerson使用的是X12报文标准，在知行之桥EDI系统中，只需要使用X12端口即可一键实现X12报文与XML文件的格式互换。

我们以上文提到的EDI 850采购订单为例，在实际的业务逻辑中，供应商需要接收来自艾默生Emerson的EDI 850，提取其中的业务数据以便进行后续处理。在知行之桥EDI系统中，处理流程如下：

1.创建一个X12端口

2.配置基本信息

将X12端口命名为EDI_To_XML，表示文件的转换是由EDI报文转换为XML，转换类型也需要按照如图所示的方式勾选。

需要注意的是，数据元素分隔符默认为星号，艾默生Emerson的EDI报文中使用管道符号作为其数据元素分隔符，因此需要在X12端口的高级设置选项卡下进行配置。

3.配置 00502 schemas

艾默生Emerson使用的X12报文标准的版本号为00502，用户需要在知行之桥EDI系统的安装目录下，找到 www->app_data->x12_schemas在这里配置00502的schemas。如果用户本地并没有这个文件，可以联系知行软件进行获取。

4.实现X12报文到XML的格式转换

在X12端口的输入选项卡下，点击更多上传文件，即可上传上文中提供的EDI 850报文。

在X12端口的输出选项卡下即可查看文件处理效果：

<Interchange Delimiters=":|.  ~" xmlns="http://www.rssbus.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Meta>
<!--Authorization Information Qualifier-->
<ISA01><!--No Authorization Information Present (No Meaningful Information in I02)-->00</ISA01>
<!--Authorization Information-->
<ISA02>          </ISA02>
<!--Security Information Qualifer-->
<ISA03>00</ISA03>
<!--Security Information-->
<ISA04>          </ISA04>
<!--Interchange ID Qualifier-->
<ISA05><!--Mutually Defined-->ZZ</ISA05>
<!--Interchange Sender ID-->
<ISA06>EMR            </ISA06>
<!--Interchange ID Qualifier-->
<ISA07><!--Mutually Defined-->ZZ</ISA07>
<!--Interchange Receiver ID-->
<ISA08>ABCCO          </ISA08>
<!--Interchange Date-->
<ISA09>081202</ISA09>
<!--Interchange Time-->
<ISA10>1311</ISA10>
<!--Interchange Control Standards Identifier-->
<ISA11>&lt;</ISA11>
<!--Interchange Control Version Number Code-->
<ISA12><!--Standards Approved for Publication by ASC X12 Procedures Review Board through October 2004-->00502</ISA12>
<!--Inter Control Number-->
<ISA13>230414746</ISA13>
<!--Acknowlegment Requested Code-->
<ISA14>0</ISA14>
<!--Interchange Usage Indicator Code-->
<ISA15><!--Test Data-->T</ISA15>
<!--Component Element Separator-->
<ISA16>&gt;</ISA16>
</Meta>
<FunctionalGroup>
<Meta>
<!--Functional Identifier Code-->
<GS01><!--Purchase Order (850)-->PO</GS01>
<!--Application Sender&apos;s Code-->
<GS02>EMR1601000</GS02>
<!--Application Receiver&apos;s Code-->
<GS03>ABCCO</GS03>
<!--Date-->
<GS04>20081201</GS04>
<!--Time-->
<GS05>1311170</GS05>
<!--Group Control Number-->
<GS06>249641407</GS06>
<!--Responsible Agency Code-->
<GS07><!--Accredited Standards Committee X12-->X</GS07>
<!--Version / Release / Industry Identifier Code-->
<GS08><!--Standards Approved for Publication by ASC X12 Procedures Review Board through October 2004-->005020</GS08>
</Meta>
<TransactionSet>
<TX-00502-850 type="TransactionSet">
<Meta>
<!--Transaction Set Identifier Code-->
<ST01><!--Purchase Order-->850</ST01>
<!--Transaction Set Control Number-->
<ST02>762443921</ST02>
</Meta>
<!--Beginning Segment for Purchase Order-->
<BEG type="Segment">
<!--Transaction Set Purpose Code-->
<BEG01><!--Original-->00</BEG01>
<!--Purchase Order Type Code-->
<BEG02><!--Blanket Order (Quantity Firm)-->BK</BEG02>
<!--Purchase Order Number-->
<BEG03>16011111666</BEG03>
<!--Release Number-->
<BEG04>25</BEG04>
<!--Date-->
<BEG05>20081101</BEG05>
<!--Contract Number-->
<BEG06>EMR123456ABC</BEG06>
<!--Acknowledgment Type-->
<BEG07>NA</BEG07>
<!--Invoice Type Code-->
<BEG08/>
<!--Contract Type Code-->
<BEG09/>
<!--Purchase Category-->
<BEG10/>
<!--Security Level Code-->
<BEG11><!--Company Confidential, Restricted (Need to Know)-->03</BEG11>
</BEG>
<!--Currency-->
<CUR type="Segment">
<!--Entity Identifier Code-->
<CUR01><!--Buying Party (Purchaser)-->BY</CUR01>
<!--Currency Code-->
<CUR02>CAD</CUR02>
<!--Exchange Rate-->
<CUR03>1.025</CUR03>
<!--Entity Identifier Code-->
<CUR04/>
<!--Currency Code-->
<CUR05 xsi:nil="true"/>
<!--Currency Market/Exchange Code-->
<CUR06/>
<!--Date/Time Qualifier-->
<CUR07><!--Rate Date-->AAY</CUR07>
<!--Date-->
<CUR08>20081115</CUR08>
<!--Time-->
<CUR09>112500</CUR09>
</CUR>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--System Number-->06</REF01>
<!--Reference Identification-->
<REF02 xsi:nil="true"/>
<!--Description-->
<REF03>160</REF03>
</REF>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Specification Number-->S3</REF01>
<!--Reference Identification-->
<REF02>EMR850V5.1</REF02>
</REF>
<!--F.O.B. Related Instructions-->
<FOB type="Segment">
<!--Shipment Method of Payment-->
<FOB01>DF</FOB01>
<!--Location Qualifier-->
<FOB02/>
<!--Description-->
<FOB03 xsi:nil="true"/>
<!--Transportation Terms Qualifier Code-->
<FOB04><!--Incoterms-->01</FOB04>
<!--Transportation Terms Code-->
<FOB05><!--Ex Works-->EXW</FOB05>
<!--Location Qualifier-->
<FOB06><!--Mutually Defined-->ZZ</FOB06>
<!--Description-->
<FOB07>Freight Term Named Place</FOB07>
<!--Risk of Loss Code-->
<FOB08><!--Risk of Loss in Transit to Destination is Buyer&apos;s-->BY</FOB08>
<!--Description-->
<FOB09>INCO2000 EXM</FOB09>
</FOB>
<!--Terms of Sale/Deferred Terms of Sale-->
<ITD type="Segment">
<!--Terms Type Code-->
<ITD01/>
<!--Terms Basis Date Code-->
<ITD02/>
<!--Terms Discount Percent-->
<ITD03 xsi:nil="true"/>
<!--Terms Discount Due Date-->
<ITD04 xsi:nil="true"/>
<!--Terms Discount Days Due-->
<ITD05 xsi:nil="true"/>
<!--Terms Net Due Date-->
<ITD06 xsi:nil="true"/>
<!--Terms Net Days-->
<ITD07 xsi:nil="true"/>
<!--Terms Discount Amount-->
<ITD08 xsi:nil="true"/>
<!--Terms Deferred Due Date-->
<ITD09 xsi:nil="true"/>
<!--Deferred Amount Due-->
<ITD10 xsi:nil="true"/>
<!--Percent of Invoice Payable-->
<ITD11 xsi:nil="true"/>
<!--Description-->
<ITD12>NET30</ITD12>
</ITD>
<N9Loop1 type="Loop">
<!--Extended Reference Information-->
<N9 type="Segment">
<!--Reference Identification Qualifier-->
<N901><!--Letters or Notes-->L1</N901>
<!--Reference Identification-->
<N902>PO Header Instructions to Supplier</N902>
</N9>
<!--Text-->
<MTX type="Segment">
<!--Note Reference Code-->
<MTX01><!--Other Instructions-->OTH</MTX01>
<!--Textual Data-->
<MTX02>HEADER INSTRUCTIONS TO SUPPLIER</MTX02>
<!--Textual Data-->
<MTX03>HEADER INSTRUCTIONS TO SUPPLIER, CONTINUED IF NEEDED</MTX03>
</MTX>
</N9Loop1>
<N1Loop1 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Vendor-->VN</N101>
<!--Name-->
<N102>ABC SUPPLIER</N102>
<!--Identification Code Qualifier-->
<N103><!--Code assigned by the organization originating the transaction set-->93</N103>
<!--Identification Code-->
<N104>160123456</N104>
</N1>
<!--Additional Name Information-->
<N2 type="Segment">
<!--Name-->
<N201>SUPPLIER NAME CONTINUED</N201>
</N2>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ADDRESS LINE 1</N301>
<!--Address Information-->
<N302>ADDRESS LINE 2</N302>
</N3>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ADDRESS LINE 3</N301>
<!--Address Information-->
<N302>ADDRESS LINE 4</N302>
</N3>
<!--Geographic Location-->
<N4 type="Segment">
<!--City Name-->
<N401>APODACA</N401>
<!--State or Province Code-->
<N402 xsi:nil="true"/>
<!--Postal Code-->
<N403>66600</N403>
<!--Country Code-->
<N404>MX</N404>
<!--Location Qualifier-->
<N405><!--Sender&apos;s Location Code-->93</N405>
<!--Location Identifier-->
<N406>X160S</N406>
<!--Country Subdivision Code-->
<N407>NLE</N407>
</N4>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Supplier Contact-->SU</PER01>
<!--Name-->
<PER02>Supplier Contact Name</PER02>
<!--Communication Number Qualifier-->
<PER03><!--Telephone-->TE</PER03>
<!--Communication Number-->
<PER04>314-555-2345</PER04>
<!--Communication Number Qualifier-->
<PER05><!--Facsimile-->FX</PER05>
<!--Communication Number-->
<PER06>314-555-1234</PER06>
<!--Communication Number Qualifier-->
<PER07><!--Electronic Mail-->EM</PER07>
<!--Communication Number-->
<PER08>contact.name@supplier.com</PER08>
</PER>
</N1Loop1>
<N1Loop1 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Sold To If Different From Bill To-->SO</N101>
<!--Name-->
<N102>EMERSON DIVISION NAME</N102>
<!--Identification Code Qualifier-->
<N103><!--Code assigned by the organization originating the transaction set-->93</N103>
<!--Identification Code-->
<N104>160SO</N104>
</N1>
<!--Additional Name Information-->
<N2 type="Segment">
<!--Name-->
<N201>SOLD-TO NAME CONTINUED</N201>
</N2>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>SO ADDRESS LINE 1</N301>
<!--Address Information-->
<N302>SO ADDRESS LINE 2</N302>
</N3>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>SO ADDRESS LINE 3</N301>
<!--Address Information-->
<N302>SO ADDRESS LINE 4</N302>
</N3>
<!--Geographic Location-->
<N4 type="Segment">
<!--City Name-->
<N401>SAINT LOUIS</N401>
<!--State or Province Code-->
<N402 xsi:nil="true"/>
<!--Postal Code-->
<N403>63136</N403>
<!--Country Code-->
<N404>US</N404>
<!--Location Qualifier-->
<N405><!--Sender&apos;s Location Code-->93</N405>
<!--Location Identifier-->
<N406>X160SO</N406>
<!--Country Subdivision Code-->
<N407>MO</N407>
</N4>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Buyer Name or Department-->BD</PER01>
<!--Name-->
<PER02>Sold-To Contact Name</PER02>
<!--Communication Number Qualifier-->
<PER03><!--Telephone-->TE</PER03>
<!--Communication Number-->
<PER04>314-555-4567</PER04>
<!--Communication Number Qualifier-->
<PER05><!--Facsimile-->FX</PER05>
<!--Communication Number-->
<PER06>314-555-3456</PER06>
<!--Communication Number Qualifier-->
<PER07><!--Electronic Mail-->EM</PER07>
<!--Communication Number-->
<PER08>contact.name@soldto.com</PER08>
</PER>
</N1Loop1>
<N1Loop1 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Bill-to-Party-->BT</N101>
<!--Name-->
<N102>EMERSON DIVISION NAME</N102>
<!--Identification Code Qualifier-->
<N103><!--Code assigned by the organization originating the transaction set-->93</N103>
<!--Identification Code-->
<N104>160BT</N104>
</N1>
<!--Additional Name Information-->
<N2 type="Segment">
<!--Name-->
<N201>BILL-TO NAME CONTINUED</N201>
</N2>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>BT ADDRESS LINE 1</N301>
<!--Address Information-->
<N302>BT ADDRESS LINE 2</N302>
</N3>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>BT ADDRESS LINE 3</N301>
<!--Address Information-->
<N302>BT ADDRESS LINE 4</N302>
</N3>
<!--Geographic Location-->
<N4 type="Segment">
<!--City Name-->
<N401>SAINT CHARLES</N401>
<!--State or Province Code-->
<N402 xsi:nil="true"/>
<!--Postal Code-->
<N403>63104</N403>
<!--Country Code-->
<N404>US</N404>
<!--Location Qualifier-->
<N405><!--Sender&apos;s Location Code-->93</N405>
<!--Location Identifier-->
<N406>X160BT</N406>
<!--Country Subdivision Code-->
<N407>MO</N407>
</N4>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Buyer Name or Department-->BD</PER01>
<!--Name-->
<PER02>BillTo Contact Name</PER02>
<!--Communication Number Qualifier-->
<PER03><!--Telephone-->TE</PER03>
<!--Communication Number-->
<PER04>314-555-6789</PER04>
<!--Communication Number Qualifier-->
<PER05><!--Facsimile-->FX</PER05>
<!--Communication Number-->
<PER06>314-555-5678</PER06>
<!--Communication Number Qualifier-->
<PER07><!--Electronic Mail-->EM</PER07>
<!--Communication Number-->
<PER08>contact.name@billto.com</PER08>
</PER>
</N1Loop1>
<N1Loop1 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Carrier-->CA</N101>
<!--Name-->
<N102>FED EX</N102>
</N1>
</N1Loop1>
<PO1Loop1 type="Loop">
<!--Baseline Item Data-->
<PO1 type="Segment">
<!--Assigned Identification-->
<PO101>1</PO101>
<!--Quantity-->
<PO102>5</PO102>
<!--Unit or Basis for Measurement Code-->
<PO103><!--Each-->EA</PO103>
<!--Unit Price-->
<PO104>3.15</PO104>
<!--Basis of Unit Price Code-->
<PO105><!--Price per Unit of Measure-->UM</PO105>
<!--Product/Service ID Qualifier-->
<PO106><!--Stock Number-->SW</PO106>
<!--Product/Service ID-->
<PO107>EMR456789</PO107>
<!--Product/Service ID Qualifier-->
<PO108><!--Vendor&apos;s Specification Number-->VX</PO108>
<!--Product/Service ID-->
<PO109>SUPP456789</PO109>
<!--Product/Service ID Qualifier-->
<PO110><!--Buyer&apos;s Engineering Change Level Number-->BE</PO110>
<!--Product/Service ID-->
<PO111>1.1</PO111>
</PO1>
<PIDLoop1 type="Loop">
<!--Product/Item Description-->
<PID type="Segment">
<!--Item Description Type-->
<PID01>F</PID01>
<!--Product/Process Characteristic Code-->
<PID02/>
<!--Agency Qualifier Code-->
<PID03/>
<!--Product Description Code-->
<PID04 xsi:nil="true"/>
<!--Description-->
<PID05>EMERSON ITEM DESCRIPTION TEXT</PID05>
</PID>
<!--Measurements-->
<MEA type="Segment">
<!--Measurement Reference ID Code-->
<MEA01><!--Weights-->WT</MEA01>
<!--Measurement Qualifier-->
<MEA02><!--Weight per Unit-->U</MEA02>
<!--Measurement Value-->
<MEA03>50</MEA03>
<!--Composite Unit of Measure-->
<MEA04 type="Composite">
<!--Unit or Basis for Measurement Code-->
<MEA0401><!--Pound-->LB</MEA0401>
</MEA04>
</MEA>
</PIDLoop1>
<!--Commodity-->
<TC2 type="Segment">
<!--Commodity Code Qualifier-->
<TC201><!--Harmonized Tariff Schedule of the United States Annotated-->A</TC201>
<!--Commodity Code-->
<TC202>HTS123</TC202>
</TC2>
<!--Commodity-->
<TC2 type="Segment">
<!--Commodity Code Qualifier-->
<TC201><!--Mutually defined-->Z</TC201>
<!--Commodity Code-->
<TC202>E122</TC202>
</TC2>
<!--Carrier Details (Special Handling, or Hazardous Materials, or Both)-->
<TD4 type="Segment">
<!--Special Handling Code-->
<TD401><!--Hazardous Cargo-->HAZ</TD401>
<!--Hazardous Material Code Qualifier-->
<TD402/>
<!--Hazardous Material Class Code-->
<TD403 xsi:nil="true"/>
<!--Description-->
<TD404>Hazardous Class Description Text</TD404>
</TD4>
<!--Text-->
<MTX type="Segment">
<!--Note Reference Code-->
<MTX01><!--Order Instructions-->ORI</MTX01>
<!--Textual Data-->
<MTX02>DETAIL LINE INSTRUCTIONS TO SUPPLIER</MTX02>
<!--Textual Data-->
<MTX03>DETAIL LINE INSTRUCTIONS TO SUPPLIER, CONTINUED IF NEEDED</MTX03>
</MTX>
<!--Tax Information-->
<TXI type="Segment">
<!--Tax Type Code-->
<TXI01><!--Mutually Defined-->ZZ</TXI01>
<!--Monetary Amount-->
<TXI02 xsi:nil="true"/>
<!--Percentage as Decimal-->
<TXI03 xsi:nil="true"/>
<!--Tax Jurisdiction Code Qualifier-->
<TXI04/>
<!--Tax Jurisdiction Code-->
<TXI05 xsi:nil="true"/>
<!--Tax Exempt Code-->
<TXI06><!--Yes (Tax Exempt)-->1</TXI06>
</TXI>
<N1Loop3 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Ship To-->ST</N101>
<!--Name-->
<N102>EMERSON DIVISION NAME</N102>
<!--Identification Code Qualifier-->
<N103><!--Code assigned by the organization originating the transaction set-->93</N103>
<!--Identification Code-->
<N104>160ST</N104>
</N1>
<!--Additional Name Information-->
<N2 type="Segment">
<!--Name-->
<N201>SHIP-TO NAME CONTINUED</N201>
</N2>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ST ADDRESS LINE 1</N301>
<!--Address Information-->
<N302>ST ADDRESS LINE 2</N302>
</N3>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ST ADDRESS LINE 3</N301>
<!--Address Information-->
<N302>ST ADDRESS LINE 4</N302>
</N3>
<!--Geographic Location-->
<N4 type="Segment">
<!--City Name-->
<N401>SAINT PETERS</N401>
<!--State or Province Code-->
<N402 xsi:nil="true"/>
<!--Postal Code-->
<N403>63376</N403>
<!--Country Code-->
<N404>US</N404>
<!--Location Qualifier-->
<N405><!--Sender&apos;s Location Code-->93</N405>
<!--Location Identifier-->
<N406>X160ST</N406>
<!--Country Subdivision Code-->
<N407>MO</N407>
</N4>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Shipment Destination Code-->4C</REF01>
<!--Reference Identification-->
<REF02>Location123</REF02>
</REF>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Ending Kanban Serial Number-->KE</REF01>
<!--Reference Identification-->
<REF02>Kanban456</REF02>
</REF>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Buyer Name or Department-->BD</PER01>
<!--Name-->
<PER02>Ship-To Contact Name</PER02>
<!--Communication Number Qualifier-->
<PER03><!--Telephone-->TE</PER03>
<!--Communication Number-->
<PER04>636-555-1234</PER04>
<!--Communication Number Qualifier-->
<PER05><!--Facsimile-->FX</PER05>
<!--Communication Number-->
<PER06>636-555-2345</PER06>
<!--Communication Number Qualifier-->
<PER07><!--Electronic Mail-->EM</PER07>
<!--Communication Number-->
<PER08>contact.name@shipto.com</PER08>
</PER>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Requestor-->RQ</PER01>
<!--Name-->
<PER02>Buyer Name</PER02>
</PER>
<!--Line Item Schedule-->
<SCH type="Segment">
<!--Quantity-->
<SCH01>5</SCH01>
<!--Unit or Basis for Measurement Code-->
<SCH02><!--Each-->EA</SCH02>
<!--Entity Identifier Code-->
<SCH03/>
<!--Name-->
<SCH04 xsi:nil="true"/>
<!--Date/Time Qualifier-->
<SCH05><!--Buyers Dock-->112</SCH05>
<!--Date-->
<SCH06>20081210</SCH06>
<!--Time-->
<SCH07 xsi:nil="true"/>
<!--Date/Time Qualifier-->
<SCH08><!--Requested Ship-->010</SCH08>
<!--Date-->
<SCH09>20081209</SCH09>
<!--Time-->
<SCH10 xsi:nil="true"/>
<!--Request Reference Number-->
<SCH11 xsi:nil="true"/>
<!--Assigned Identification-->
<SCH12>1S</SCH12>
</SCH>
</N1Loop3>
</PO1Loop1>
<PO1Loop1 type="Loop">
<!--Baseline Item Data-->
<PO1 type="Segment">
<!--Assigned Identification-->
<PO101>2</PO101>
<!--Quantity-->
<PO102>10</PO102>
<!--Unit or Basis for Measurement Code-->
<PO103><!--Each-->EA</PO103>
<!--Unit Price-->
<PO104>5.25</PO104>
<!--Basis of Unit Price Code-->
<PO105><!--Price per Unit of Measure-->UM</PO105>
<!--Product/Service ID Qualifier-->
<PO106><!--Stock Number-->SW</PO106>
<!--Product/Service ID-->
<PO107>EMR567890</PO107>
<!--Product/Service ID Qualifier-->
<PO108><!--Vendor&apos;s Specification Number-->VX</PO108>
<!--Product/Service ID-->
<PO109>SUPP567890</PO109>
<!--Product/Service ID Qualifier-->
<PO110><!--Buyer&apos;s Engineering Change Level Number-->BE</PO110>
<!--Product/Service ID-->
<PO111>2.2</PO111>
</PO1>
<PIDLoop1 type="Loop">
<!--Product/Item Description-->
<PID type="Segment">
<!--Item Description Type-->
<PID01>F</PID01>
<!--Product/Process Characteristic Code-->
<PID02/>
<!--Agency Qualifier Code-->
<PID03/>
<!--Product Description Code-->
<PID04 xsi:nil="true"/>
<!--Description-->
<PID05>EMERSON ITEM DESCRIPTION TEXT</PID05>
</PID>
<!--Measurements-->
<MEA type="Segment">
<!--Measurement Reference ID Code-->
<MEA01><!--Weights-->WT</MEA01>
<!--Measurement Qualifier-->
<MEA02><!--Weight per Unit-->U</MEA02>
<!--Measurement Value-->
<MEA03>12</MEA03>
<!--Composite Unit of Measure-->
<MEA04 type="Composite">
<!--Unit or Basis for Measurement Code-->
<MEA0401><!--Pound-->LB</MEA0401>
</MEA04>
</MEA>
</PIDLoop1>
<!--Commodity-->
<TC2 type="Segment">
<!--Commodity Code Qualifier-->
<TC201><!--Harmonized Tariff Schedule of the United States Annotated-->A</TC201>
<!--Commodity Code-->
<TC202>HTS123</TC202>
</TC2>
<!--Commodity-->
<TC2 type="Segment">
<!--Commodity Code Qualifier-->
<TC201><!--Mutually defined-->Z</TC201>
<!--Commodity Code-->
<TC202>E122</TC202>
</TC2>
<!--Carrier Details (Special Handling, or Hazardous Materials, or Both)-->
<TD4 type="Segment">
<!--Special Handling Code-->
<TD401><!--Hazardous Cargo-->HAZ</TD401>
<!--Hazardous Material Code Qualifier-->
<TD402/>
<!--Hazardous Material Class Code-->
<TD403 xsi:nil="true"/>
<!--Description-->
<TD404>Hazardous Class Description Text</TD404>
</TD4>
<!--Text-->
<MTX type="Segment">
<!--Note Reference Code-->
<MTX01><!--Order Instructions-->ORI</MTX01>
<!--Textual Data-->
<MTX02>DETAIL LINE INSTRUCTIONS TO SUPPLIER</MTX02>
<!--Textual Data-->
<MTX03>DETAIL LINE INSTRUCTIONS TO SUPPLIER, CONTINUED IF NEEDED</MTX03>
</MTX>
<!--Tax Information-->
<TXI type="Segment">
<!--Tax Type Code-->
<TXI01><!--Mutually Defined-->ZZ</TXI01>
<!--Monetary Amount-->
<TXI02 xsi:nil="true"/>
<!--Percentage as Decimal-->
<TXI03 xsi:nil="true"/>
<!--Tax Jurisdiction Code Qualifier-->
<TXI04/>
<!--Tax Jurisdiction Code-->
<TXI05 xsi:nil="true"/>
<!--Tax Exempt Code-->
<TXI06><!--Yes (Tax Exempt)-->1</TXI06>
</TXI>
<N1Loop3 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Ship To-->ST</N101>
<!--Name-->
<N102>EMERSON DIVISION NAME</N102>
<!--Identification Code Qualifier-->
<N103><!--Code assigned by the organization originating the transaction set-->93</N103>
<!--Identification Code-->
<N104>160ST</N104>
</N1>
<!--Additional Name Information-->
<N2 type="Segment">
<!--Name-->
<N201>SHIP-TO NAME CONTINUED</N201>
</N2>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ST ADDRESS LINE 1</N301>
<!--Address Information-->
<N302>ST ADDRESS LINE 2</N302>
</N3>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ST ADDRESS LINE 3</N301>
<!--Address Information-->
<N302>ST ADDRESS LINE 4</N302>
</N3>
<!--Geographic Location-->
<N4 type="Segment">
<!--City Name-->
<N401>SAINT PETERS</N401>
<!--State or Province Code-->
<N402 xsi:nil="true"/>
<!--Postal Code-->
<N403>63376</N403>
<!--Country Code-->
<N404>US</N404>
<!--Location Qualifier-->
<N405><!--Sender&apos;s Location Code-->93</N405>
<!--Location Identifier-->
<N406>X160ST</N406>
<!--Country Subdivision Code-->
<N407>MO</N407>
</N4>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Shipment Destination Code-->4C</REF01>
<!--Reference Identification-->
<REF02>Location123</REF02>
</REF>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Ending Kanban Serial Number-->KE</REF01>
<!--Reference Identification-->
<REF02>Kanban456</REF02>
</REF>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Buyer Name or Department-->BD</PER01>
<!--Name-->
<PER02>Ship-To Contact Name</PER02>
<!--Communication Number Qualifier-->
<PER03><!--Telephone-->TE</PER03>
<!--Communication Number-->
<PER04>636-555-1234</PER04>
<!--Communication Number Qualifier-->
<PER05><!--Facsimile-->FX</PER05>
<!--Communication Number-->
<PER06>636-555-2345</PER06>
<!--Communication Number Qualifier-->
<PER07><!--Electronic Mail-->EM</PER07>
<!--Communication Number-->
<PER08>contact.name@shipto.com</PER08>
</PER>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Requestor-->RQ</PER01>
<!--Name-->
<PER02>Buyer Name</PER02>
</PER>
<!--Line Item Schedule-->
<SCH type="Segment">
<!--Quantity-->
<SCH01>7</SCH01>
<!--Unit or Basis for Measurement Code-->
<SCH02><!--Each-->EA</SCH02>
<!--Entity Identifier Code-->
<SCH03/>
<!--Name-->
<SCH04 xsi:nil="true"/>
<!--Date/Time Qualifier-->
<SCH05><!--Buyers Dock-->112</SCH05>
<!--Date-->
<SCH06>20081215</SCH06>
<!--Time-->
<SCH07 xsi:nil="true"/>
<!--Date/Time Qualifier-->
<SCH08/>
<!--Date-->
<SCH09 xsi:nil="true"/>
<!--Time-->
<SCH10 xsi:nil="true"/>
<!--Request Reference Number-->
<SCH11 xsi:nil="true"/>
<!--Assigned Identification-->
<SCH12>2S1</SCH12>
</SCH>
</N1Loop3>
<N1Loop3 type="Loop">
<!--Party Identification-->
<N1 type="Segment">
<!--Entity Identifier Code-->
<N101><!--Ship To-->ST</N101>
<!--Name-->
<N102>EMERSON DIVISION NAME</N102>
<!--Identification Code Qualifier-->
<N103><!--Code assigned by the organization originating the transaction set-->93</N103>
<!--Identification Code-->
<N104>160ST</N104>
</N1>
<!--Additional Name Information-->
<N2 type="Segment">
<!--Name-->
<N201>SHIP-TO NAME CONTINUED</N201>
</N2>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ST ADDRESS LINE 1</N301>
<!--Address Information-->
<N302>ST ADDRESS LINE 2</N302>
</N3>
<!--Party Location-->
<N3 type="Segment">
<!--Address Information-->
<N301>ST ADDRESS LINE 3</N301>
<!--Address Information-->
<N302>ST ADDRESS LINE 4</N302>
</N3>
<!--Geographic Location-->
<N4 type="Segment">
<!--City Name-->
<N401>SAINT PETERS</N401>
<!--State or Province Code-->
<N402 xsi:nil="true"/>
<!--Postal Code-->
<N403>63376</N403>
<!--Country Code-->
<N404>US</N404>
<!--Location Qualifier-->
<N405><!--Sender&apos;s Location Code-->93</N405>
<!--Location Identifier-->
<N406>X160ST</N406>
<!--Country Subdivision Code-->
<N407>MO</N407>
</N4>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Shipment Destination Code-->4C</REF01>
<!--Reference Identification-->
<REF02>Location123</REF02>
</REF>
<!--Reference Information-->
<REF type="Segment">
<!--Reference Identification Qualifier-->
<REF01><!--Ending Kanban Serial Number-->KE</REF01>
<!--Reference Identification-->
<REF02>Kanban456</REF02>
</REF>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Buyer Name or Department-->BD</PER01>
<!--Name-->
<PER02>Ship-To Contact Name</PER02>
<!--Communication Number Qualifier-->
<PER03><!--Telephone-->TE</PER03>
<!--Communication Number-->
<PER04>636-555-1234</PER04>
<!--Communication Number Qualifier-->
<PER05><!--Facsimile-->FX</PER05>
<!--Communication Number-->
<PER06>636-555-2345</PER06>
<!--Communication Number Qualifier-->
<PER07><!--Electronic Mail-->EM</PER07>
<!--Communication Number-->
<PER08>contact.name@shipto.com</PER08>
</PER>
<!--Administrative Communications Contact-->
<PER type="Segment">
<!--Contact Function Code-->
<PER01><!--Requestor-->RQ</PER01>
<!--Name-->
<PER02>Buyer Name</PER02>
</PER>
<!--Line Item Schedule-->
<SCH type="Segment">
<!--Quantity-->
<SCH01>3</SCH01>
<!--Unit or Basis for Measurement Code-->
<SCH02><!--Each-->EA</SCH02>
<!--Entity Identifier Code-->
<SCH03/>
<!--Name-->
<SCH04 xsi:nil="true"/>
<!--Date/Time Qualifier-->
<SCH05><!--Buyers Dock-->112</SCH05>
<!--Date-->
<SCH06>20081220</SCH06>
<!--Time-->
<SCH07 xsi:nil="true"/>
<!--Date/Time Qualifier-->
<SCH08/>
<!--Date-->
<SCH09 xsi:nil="true"/>
<!--Time-->
<SCH10 xsi:nil="true"/>
<!--Request Reference Number-->
<SCH11 xsi:nil="true"/>
<!--Assigned Identification-->
<SCH12>2S2</SCH12>
</SCH>
</N1Loop3>
</PO1Loop1>
<CTTLoop1 type="Loop">
<!--Transaction Totals-->
<CTT type="Segment">
<!--Number of Line Items-->
<CTT01>1</CTT01>
</CTT>
</CTTLoop1>
</TX-00502-850>
</TransactionSet>
</FunctionalGroup>
</Interchange>

转换后的XML文件中，可以直观的看到业务含义与业务数据的对应关系。至此我们成功实现了格式转换。知行之桥EDI系统还支持将上述XML文件进一步转换为 Excel、CSV、Json以及数据库XML等格式的文件，支持与企业内部业务系统集成，从而最大程度上实现数据的自动化处理。

扩展阅读：Emerson EDI官网获取EDI规范以及EDI示例报文

更多 EDI 信息，请参阅: EDI 是什么？

阅读原文：艾默生Emerson EDI需求分析