http://www.edibasics.co.uk/
http://www.edibasics.co.uk/
EDI Messages
EDI Messages
1.11.1 OthOther Per Pictictureures: ss: sourource dce doc Edoc Edi Geni Generaeral prel presesentantationtion
Edi Messages to sap Idocs: Edi Messages to sap Idocs: EDI EDI m meessssaaggee SSttaannddaarrdd SAP SAP M Meessssaaggee SSAAP P IIddoocc CCoommmmeennttss D
Deellffoor r IInn EEDDIIFFAACCTT DEDEII!!"" DDEEFF##$$%%&& D
Deell''iit t IInn EEDDIIFFAACCTT ""EE(())IITT ""EE(())IITT%%&& iif f kkaannbbaan n oor r ttrraannssppoorrt t nnuu**bbeer r D
Deell''iit t IInn EEDDIIFFAACCTT DDEEII!!"" DDEEFF##$$%%&&
IIf f nno o kkaannbbaan n oor r ttrraannssppoorrtt nu*ber
nu*ber D
Deessaadd+ + ##uutt EEDDIIFFAACCTT DEDE""AADD,, DDEE,,$$--%% IInn++ooiic c IInn EEDDIIFFAACCTT II!!,,##IICC II!!,,##IICC%%&& D
Deelliinns s IInn ##DDEETTTTEE DEDEII!!"" DDEEFF##$$%%&& C
Caallddeel l IInn ##DDEETTTTEE ""EE(())IITT ""EE(())IITT%%&& A+iep #u
A+iep #utt #DETTE#DETTE DE"AD,DE"AD, DE,DE,$-%$-% IInn++ooiic c oouutt ##DDEETTTTEE II!!,,##IICC II!!,,##IICC%%&& 0
011%%2 2 IInn ,,DDAA DDEEII!!"" DDEEFF##$$%%&& 0
011&&2 2 IInn ,,DDAA ""EE(())IITT ""EE(())IITT%%&& 0
011&& IInn ,,DDAA DDEE""AADD,, DDEE,,$$--%% Integrate custo*er de*and
Integrate custo*er de*and EDI EDI m meessssaaggee SSttaannddaarrdd SAP SAP M Meessssaaggee SSAAP P IIddoocc CCoommmmeennttss D
Deellffoor r IInn EEDDIIFFAACCTT DEDEII!!"" DDEEFF##$$%%&& D
Deell''iit t IInn EEDDIIFFAACCTT ""EE(())IITT ""EE(())IITT%%&& iif f kkaannbbaan n oor r ttrraannssppoorrt t nnuu**bbeer r D
Deell''iit t IInn EEDDIIFFAACCTT DDEEII!!"" DDEEFF##$$%%&&
IIf f nno o kkaannbbaan n oor r ttrraannssppoorrtt nu*ber
nu*ber D
Deessaadd+ + ##uutt EEDDIIFFAACCTT DEDE""AADD,, DDEE,,$$--%% IInn++ooiic c IInn EEDDIIFFAACCTT II!!,,##IICC II!!,,##IICC%%&& D
Deelliinns s IInn ##DDEETTTTEE DEDEII!!"" DDEEFF##$$%%&& C
Caallddeel l IInn ##DDEETTTTEE ""EE(())IITT ""EE(())IITT%%&& A+iep #u
A+iep #utt #DETTE#DETTE DE"AD,DE"AD, DE,DE,$-%$-% IInn++ooiic c oouutt ##DDEETTTTEE II!!,,##IICC II!!,,##IICC%%&& 0
011%%2 2 IInn ,,DDAA DDEEII!!"" DDEEFF##$$%%&& 0
011&&2 2 IInn ,,DDAA ""EE(())IITT ""EE(())IITT%%&& 0
In case of 7)3 the custo*er send edi *essage con+erted in idoc DEI!" for the forecast.
DA de+elops standards and best practices to ser+e the needs of co*panies within the 8er*an auto*oti+e industr4. The ,DA has de+eloped o+er thirt4 *essages to *eet the need of co*panies such as ,93 Audi3 osch3 Continental and Dai*ler A8.
A list of ,DA docu*ent standards is pro+ided below:
4902 Transport Label Barcode-enabled incl. VDA 4913
4905 Call of
4905/2 Call of – Delivery nstr!ction "#dette $essa%e D&L'()
4906 nvoice
4907 *e+ittance Advice
4908 Credit Advice
4911 ,rices
4912 Delivery 'ote incl. VDA 4913
4913 Delivery 'ote
4914 #dette specication or le transer 4915 Detailed Call #f "/T)
4916 Call #f /!st-in-se0!ence
4918 Veicle dentication and Transport Data
4919 Veicle Arrival and Depart!re 'otication 4920 2orardin% nstr!ction
4921 Delivery Data
4922 2orardin% nstr!ction incl. VDA 4913 4923 &n0!iry "#dette $essa%e &'*5)
4924 #fer6!otation "#dette $essa%e #22&**)
4925 ,!rcase #rder
4926 Ac7noled%e+ent o #rder "#dette $essa%e *&,#*D) 4927 &0!ip+ent (tate+ent and &0!ip+ent $ove+ent
4929 Delivery 'ote "#dette $essa%e AV&8,) 4932 nvoice "#dette-'acrict 'V#C)
4951 &n%ineerin% Data $essa%e "&'DAT) 4970 Delivery 2orecast
4971 Collection #rder
4972 Dispatc 'ote e: ;or7s6,lant 4973 Veicle Arrival
4974 Veicle Depart!re
4975 Can%e 6 nor+ation 'ote
4976 Can%e 6 nor+ation Conr+ation
4977 Da+a%e 'ote
4978 *epair (tart 6 &nd 'ote 4979 *eady or Dispatc 'ote 4980 Loadin% nstr!ctions
Mapping A!"I ;&< to "A= Message T4pe and IDoc T4pe:
<%0 Motor carrier ship*ent infor*ation
The logical *essage is ">=M!T or IFTMI!3 the IDoc t4pe ">=M!T%.
<&0 Transportation carrier ship*ent status *essage
The logical *essage is T$;"TA3 the IDoc t4pe T$;"TA%&. Inbound processing is supported.
%0 "hipping instructions
The logical *essage is ">=M!T or IFTMI!3 the IDoc t4pe ">=M!T%.
?&% In+oice or billing docu*ent @also ??%3 EDI B Inbound I!,#IC posting configuration The logical *essage is I!,#IC3 the IDoc t4pe I!,#IC%&.
?&< Credit and debit ad+ice
The logical *essages are C$EAD, or DEAD,3 the IDoc t4pes =E;$<%%& and =E;$<%%<.
?<% =a4*ent order and credit ad+ice
For the pa4*ent order3 the logical *essage is =A-E;T @$EMAD,3 the IDoc t4pes =E;$<%%& and =E;$<%%<.
For the credit ad+ice @E$" B E+aluated $eceipt "ettle*ent3 the logical *essage is 8",E$F3 the IDoc t4pe 8",E$F%&.
?< ockbo
?% Deli+er4 schedule @A
The logical *essage is DEI!" @fro* the EDI standard #DETTE or DEF#$3 the IDoc t 4pe is DEF#$%&.
?< =rice catalog @also ?13 ???3 ??1
The logical *essage is =$ICAT3 the IDoc t4pe =$ICAT%&. #utbound processing is supported.
?0 enefit enroll*ent and *aintenance
The logical *essage is E!$E=3 the IDoc t4pe E!EFIT&. #utbound processing is supported.
?0% $euest
The logical *essage is $E(#TE3 the IDoc t4pes #$DE$"%& to #$DE$"%0.
?0 (uotation
The logical *essage is (#TE"3 the IDoc t4pes #$DE$"%& to #$DE$"%0. #utbound processing is supported.
?2% =urchase order or order @also ?2
The logical *essage is #$DE$"3 the IDoc t4pes #$DE$"%& to #$DE$"%0.
?2< "tock and sale data
The logical *essage is =$#ACT3 the IDoc t4pe =$#ACT%&.
?22 #rdering or order response @also ?G2
?2G Transport and shipping notification @A"! B Ad+anced "hip !otification
For transport in the "A= application3 the logical *essage is ">=M!T or ">=AD,3 the IDoc t4pes ">=M!T%& to ">=M!T%.
For deli+er4 in the "A= application3 the logical *essage is DE"AD,3 the IDoc t4pes are DE"AD,%& @epires or DE,$-%& and DE,$-%<.
?G% #rdering or order *odification @also ?G
The logical *essage is #$DC>83 the IDoc t4pes #$DE$"%& to #$DE$"%0.
?G& Credit ad+ice @E$" B E+aluated $eceipt "ettle*ent The logical *essage is 8",E$F3 the IDoc t4pe 8",E$F%&.
?G< deli+er4 schedule @FA
The logical *essage is DEI!" @fro* the EDI standard #DETTE or DE)IT3 the IDoc t4pe is DEF#$%&.
?G0 Tet *essage
The logical *essage is T;T$A93 the IDoc t4pe T;T$A9%&. Inbound processing is supported.
10% "hipping order and stock order
The logical *essage is ">=#$D or 9>"#$D3 the ID#C t4pe DE,$-%&.
102 "hipping confir*ation and stock confir*ation
The logical *essage is ">=C#! or 9>"C#!3 the IDoc t4pe DE,$-%&.
11 Functional Acknowledg*ent
This is a technical confir*ation. This is not echanged +ia an indi+idual *essage but the status report for IDoc processing. The status +alues used are:
H<<H "hipping #3 acknowledg*ent has 4et to co*e H&GH Functional Acknowledg*ent positi+e
H&H Functional Acknowledg*ent negati+e
The status +alues H&0H and H&2H are a+ailable for the Interchange Acknowledg*ent accordingl4.
=lease check these so*e *apping EDIFACT B Message T4pe/IDoc T4pe. EDIFACT Description Message/IDoc Type CREADV Credit Advice Message CREADV/PEXR2001 CREEXT Etended Credit Advice CREADV/PEXR2001 CREM!" M#$tip$e Credit Advice CREADV/PEXR2001
C!%DEC C#sto&s Dec$aration Message EXPI'V/IMPI'V
EXPI'V01/IMPI'V01
C!%RE% C#sto&s Response Message TXTRA(/TXTRA(01 DE)ADV De*it Advice Message DE)ADV/PEXR2001 DE)M!" M#$tip$e De*it Advice DE)ADV/PEXR2002 DE"F+R De$ivery %c,ed#$e Message DE"I'%/DE"F+R01
-"A)/FA). DE"F+R/DE"F+R01 DE"IT #st In Ti&e Message DE"I'%/DE"F+R01
-"A)/FA). DE"F+R/DE"F+R01
DE%ADV Despatc, Advice DE%ADV/DE%ADV01
DE"VR/DE"VR01
%PM'T/%PM'T02
DIRDE) Direct De*it Message DIRDE)/FI'%TA01 FI'%TA Financia$ %ate&ent FI'%TA/FI'%TA01 F!'AC F#nctiona$ Ac3no4$edge&ent %tat#s report/EDID%
%TAT!%/%%TAT01
IFTMI' Transport Instr#ctions IFTMI'/DE"VR01
IFTMI'/%PM'T02
IMPDEF EDI I&p$e&entation 5#ide$ine %RECD/%RECD01 De6inition Message %ID+C/%ID+C01
I'V+IC Invoice I'V+IC/I'V+IC01
I'VRPT Inventory Report PR+ACT/PR+ACT01 +RDC5 P#rc,ase +rder C,ange Re7#est +RDC5/+RDER%01 +RDER% P#rc,ase +rder +RDER%/+RDER%01 +RDR%P P#rc,ase +rder Response +RDR%P/+RDER%01 PARTI' Party In6or&ation Message CREMA%/CREMA%01
DE)MA%/DE)MA%01
PAEXT Etended Pay&ent +rder PAEXT/PEXR2001 PAM!" M#$tip$e Pay&ent +rder PAEXT/PEXR2001 PA+RD Pay&ent +rder Message PAEXT/PEXR2001 PRICAT Price/%a$es Cata$og#e Message PRICAT/PRICAT01 PR+DAT Prod#ct Data Message PRICAT/PRICAT01 8!+TE% 8#otation Message 8!+TE%/+RDER%01 REMADV Re&ittance Advice REMADV/PEXR2001 RE8+TE Re7#est For 8#otation RE8+TE/+RDER%01 %"%FCT %a$es Forecast Message PR+ACT/PR+ACT01 %"%RPT %a$es Data Report PR+ACT/PR+ACT01
#DETTE
The #rganisation for Data Echange b4 Tele Trans*ission in Europe is a
group that represents the interests of the auto*oti+e industr4 in Europe.
The4 are the eui+alent of the Auto*oti+e Industr4 Action 8roup @AIA8
in !orth A*erica.
The organisation de+elops tools and reco**endations that i*pro+e the flow of goods3 ser+ices product data and business infor*ation across the whole auto*oti+e +alue chain. #DETTE has been responsible for de+eloping co**unications standards such as #FT= and #FT=<.%3 constant i*pro+e*ent processes such as Materials Manage*ent
#perations 8uideline / ogistics E+aluation @MM#8/E and auto*oti+e specific docu*ent standards as defined below:
DELINS Delivery 2orecast 6 Delivery
EXHAND 2or Delivery (ced!le &:ception <andlin%
CALDEL /T Delivery
SYNCRO (e0!enced Delivery
KANBAN =A'BA' Delivery
FORDIS >*eady or Dispatc? Advice
INVOIC nvoice
STOACT nventory *eport
TRINAD 2orardin% nstr!ction
CONSU Consi%n+ent Consolidation
ORDERR ,!rcase #rder
ORDCH! #rder Can%e
REPORD #rder *esponse
PRILST ,rice List Based
READV *e+ittance Advice
STATAC Acco!nt (tate+ent
Ke points
Depending of the custo*er edi standard3 the edi application will con+ert the custo*er *essage in sap standard idoc DEI!".
Following rules *ust be anal4sed or discussed with the custo*er to interpret
the content of the idoc and to find the wa4 to para*eter the schedule agree*ent which will store the content of it.
&. 9hich are the rules to identif4 the concerning schedule agree*ent.. <. 9hich is the frequency of the trans*ission for each t4pe of *essage. . 9hich t4pe of *essage will contain which t4pe of infor*ation : forecast3
0. 9hat is the rule of update the eisting schedules lines : *odification between to gi+en dates or cancel and replace. @field labke4 in idoc: &K *odif < K cancel/r 2. Do we recei+e cu*ulati+e t4s or should we calculated the*.
After this anal4se3 we should be able to attribute a t4pe of schedule agree*ent and the right para*eters.
G. Are the schedule dates epressed in arri+al date or departure dates.
After this anal4se3 we should be able to attribute a t4pe of schedule agree*ent and the right para*eters.
EDI Docu*ent "tandard
http://www.edibasics.co*/ediBresources/docu*entBstandards/
There are *an4 EDI docu*ent standards but what do the4 all *ean and where are the4 usedL
ANSI ASC X12
n 19@9 te A+erican 'ational (tandards nstit!te "A'() cartered te
Accredited (tandards Co++ittee "A(C) 81 to develop !nior+ standards or inter-ind!stry electronic e:can%e o b!siness transactions na+ely electronic data intercan%e. A'( 81 as ori%inally conceived to s!pport co+panies across diferent ind!stry sectors in 'ort A+erica oever today tere are +ore tan 3 co+panies orldide !sin% 81 &D standards in daily b!siness transactions. A(C 81 also contrib!tes to '6&D2ACT +essa%es tat are !sed idely o!tside o te nited (tates.
• Further information about ANSI X12 can be found here »
• Further information about the ANSI X12 document types can be
found here »
EANCO
Tis standard as ori%inally conceived in 19E@ by te &A' eneral Asse+bly and as to be developed on te ten e+er%in% international '6&D2ACT standard. Te &A'C#$ +essa%es +aintained by (1 are +ore detailed in nat!re co+pared to te T*ADAC#$( +essa%e set. &A'C#$ as ori%inally
developed or te retail sector and as s!bse0!ently %ron to beco+e te +ost idely !sed '6&D2ACT s!bset and is no o!nd in a variety o oter ind!stry sectors s!c as ealtcare constr!ction and p!blisin%.
• Further information about EANCOM can be found here »
UN/EDIFACT
nited 'ations6&lectronic Data ntercan%e or Ad+inistration Co++erce and Transport is te international standard tat as developed by te nited
'ations. Te or7 o +aintenance and !rter develop+ent o tis standard is done tro!% te nited 'ations Centre or Trade 2acilitation and &lectronic B!siness "'6C&2ACT) !nder te ' &cono+ic Co++ission or &!rope. Te &D2ACT standard provides a set o synta: r!les to str!ct!re an interactive e:can%e protocol and provides a set o standard +essa%es ic allo +!lti-co!ntry and +!lti-ind!stry e:can%e o electronic b!siness doc!+ents. &D2ACT is idely !sed across &!rope +ainly d!e to te act tat +any co+panies
adopted it very early on. &D2ACT as seen so+e adoption in te A(,AC re%ion oever tere are c!rrently +ore 8$L-based standards bein% !sed in tis partic!lar re%ion today.
• Further information about EIFAC! can be found here »
• Further information about the EIFAC! document types can be
found here »
HIPAA
Te <ealt ns!rance ,ortability and Acco!ntability Act as enacted by te .( con%ress in 199F. A 7ey co+ponent o <,AA is te establis+ent o national standards or electronic ealt care transactions and national identiers or providers ealt ins!rance plans and e+ployers. Te standards are +eant to i+prove te eGciency and efectiveness o te 'ort A+erican ealt care syste+ by enco!ra%in% te idespread !se o &D in te .( ealt care
syste+. Te <,AA &D transaction sets are based on 81 and te 7ey +essa%e types are described belo.
• Further information about "I#AA can be found here »
• Further information about the "I#AA document types can be found here
»
ODETTE
Te #r%aniHation or Data &:can%e by Tele Trans+ission in &!rope is a %ro!p tat represents te interests o te a!to+otive ind!stry in &!rope. Tey are te e0!ivalent o te A!to+otive nd!stry Action ro!p "AA) in 'ort A+erica. Te or%aniHation develops tools and reco++endations tat i+prove te Io o
%oods services prod!ct data and b!siness inor+ation across te ole a!to+otive val!e cain. #D&TT& as been responsible or developin%
processes s!c as $aterials $ana%e+ent #perations !ideline 6 Lo%istics
&val!ation "$$#6L&) and a!to+otive-specic doc!+ent standards as dened via te lin7 belo.
• Further information about OE!!E can be found here »
• Further information about the OE!!E document types can be
found here »
R#$%&&'N%&
Tis consists o a consorti!+ o +aJor co+p!ter cons!+er electronics se+i-cond!ctor +an!act!rers teleco++!nications and lo%istics co+panies or7in% to%eter to create and i+ple+ent ind!stry-ide open e-b!siness process
standards. Tese standards or+ a co++on e-b!siness lan%!a%e ali%nin% processes beteen s!pply cain partners on a %lobal basis. Te *osetta'et doc!+ent standard is based on 8$L and denes +essa%e %!idelines b!siness processes interace and i+ple+entation ra+eor7s or interactions beteen co+panies. sin% *osetta'et ,artner nterace ,rocesses ",,s) b!siness
partners o all siHes can connect electronically to process transactions and +ove inor+ation itin teir e:tended s!pply cains. 2!rter inor+ation abo!t
*osetta'et ,, doc!+ents can be o!nd ro+ te lin7 belo.
• Further information about $osettaNet can be found here »
• Further information about the $osettaNet document types can be
found here »
S(IFT
Te (ociety o ;orldide nterban7 2inancial Teleco++!nication as or+ed in 19@3 and is ead0!artered in Br!ssels. (;2T operates a orldide nancial +essa%in% netor7 ic e:can%es +essa%es beteen ban7s and nancial instit!tions. (;2T also +ar7ets sotare and services to nancial instit!tions +!c o it or !se on te (;2T'et 'etor7. (;2T'et is te inrastr!ct!re !sed to e:can%e tese doc!+ents and 2' nterAct and 2ileAct are !sed to encode te (;2T doc!+ents or trans+ission. Te +aJority o interban7 +essa%es !se te (;2T netor7. As o 'ove+ber E (;2T lin7ed E@4 nancial
instit!tions across 9 co!ntries. Te (;2T doc!+ent standard is split into o!r areas ,ay+ents Trade (ervices (ec!rities and Tradin%.
• Further information about S%IF! can be found here »
• Further information about the S%IF! document types can be found here
»
Tis is an early standard or &D and as pri+arily !sed in te = retail sector. t as ori%inally introd!ced in 19E as an i+ple+entation o te '6TD synta: one o te prec!rsors o &D2ACT and as +aintained and e:tended by te = Article '!+berin% Association no called (1 =. Te standard is +ore or less obsolescent since te develop+ent o it efectively ceased in 199K in avor o te &D2ACT &A'C#$ s!bsets. Despite tis it as proved d!rable and te +aJority o te retail &D traGc in te = still !ses it today.
• Further information about !radacoms can be found here »
• Further information about the !radacoms document types can be
found here »
VDA
Tis or%aniHation develops standards and best practices to serve te needs o co+panies itin te er+an a!to+otive ind!stry. Te VDA as developed over tirty +essa%es to +eet te need o co+panies s!c as V; A!di Bosc
Continental and Dai+ler A. 2!rter inor+ation abo!t tese +essa%es can be o!nd via te lin7 belo.
• Further information about &A can be found here »
• Further information about the &A document types can be found here »
VICS
Te Vol!ntary nter-ind!stry Co++erce (tandard is !sed by te %eneral
+ercandise retail ind!stry across 'ort A+erica. t is a s!bset o te A'( A(C 81 national standard. VC( &D is bein% !tiliHed by to!sands o co+panies depart+ent and specialty retail stores +ass +ercandisers and teir
respective s!ppliers. n 19EE (1 ( beca+e te +ana%e+ent and
ad+inistrative body or VC( &D. (1 ( also +ana%es te A(C 81 derived nior+ Co++!nication (tandard "C() or te %rocery ind!stry and
nd!strial6Co++ercial (tandard "6C) or te ind!strial sector.
#FT= @#DETTE File Transfer =rotocol fornece u*a *aneira padro para siste*as de co*putador heterogNneos para se co*unicar uns co* os outros.
#FT= @reco*endaOo da AssociaOo da IndPstria Auto*Q+el @,DA no. 01&0/< R a definiOo do File Transfer =rotocol @FT= a #DETTE 8rupo I, para as ca*adas I"# / #"I 0 a . Ele per*ite transferNncias de dados de diferentes tipos de arui+os. #FT= R usado na indPstria auto*Q+el europeia e os seus fornecedores co*o o protocolo padro. Ele ta*bR* R usado pela indPstria uS*ica e apenas introduido por outros setores @bancos3 transportes.
EDI Messaging =rotocols
http://www.edibasics.co.uk/ediBresources/*essagingBprotocols/
#FT=
http://www.'scape.co*/blog/oftpBodetteBfileBtransferBprotocol A"<
http://www.'scape.co*/blog/bid/&%%02/A"<B"i*plified
A"<3 FT=3 #FT=3 >TT= U to na*e 'ust a few EDI Messaging =rotocols
but what are the4 and what do the4 *eanL
&.< A"&
App'icabi'ity Statement (AS) 1 was de+eloped b4 the IETF @Internet Engineering Task Force to i*ple*ent secure and reliable *essaging o+er "MT= and "/MIME. It was the first A" protocol to be de+eloped and uses signing3 encr4ption and MD! con+entions. @MD! refers to Message Disposition !otifications or the abilit4 to pro+ide 5$eturn
$eceipts6. As with an4 A" file transfer3 A"& file transfers t4picall4 reuire both sides of the echange to trade "" certificates and specific 5trading partnerH na*es before an4
transfers can take place.
&. A"<
App'icabi'ity Statement (AS) 2 uses the sa*e signing3 encr4ption3 and MD!
con+entions used in the original A"& protocol. A"< *essages are usuall4 sent across the internet using the >TT= or >TT=" protocol. A"< has been widel4 depl o4ed as a point to point connecti+it4 *ethod. A"< offers *an4 ad+antages o+er standard >TT=3 including increased +erification3 and securit4 achie+ed through the use of receipts and digital
signatures. A"< transactions and acknowledge*ents also occur in realBti*e3 increasing the efficienc4 of docu*ent echanges. The ." co*pan4 9al*art was one of the first
&..& A"
App'icabi'ity Statement (AS) * was de+eloped b4 the IETF to i*ple*ent secure and reliable *essaging o+er FT=. A" is based upon the secure +ersion of the FT= protocol3 rather than >TT=. A" transport is "/MIME o+er FT= and operates a client/ser+er *odel like FT=3 as opposed to the peerBtoBpeer approach used b4 A"<. A" also uses MD!Vs @receipt notifications like A"<. A" is a push/pull protocol and the client side A" does not reuire a listener to be alwa4s aware of inbound traffic @whereas A"< alwa4s reuires a persistent connection for the listener. A" *a4 be especiall4 well suited for banking and other industries where there are hea+4 in+est*ents in FT= scripting3 applications and securit4.
&.0 A"0
App'icabi'ity Statement (AS) + offers secure < docu*ent echange using web ser+ices and was de+eloped b4 the subBco**ittee of the #A"I" eb; M *essaging ser+ices technical co**ittee. A"0 is still in its draft definition for*at. The A"0 profile pro+ides the *arket place with an entr4 le+el solution that allows co*panies to begin utilising their internal "#A based platfor*s for eternal < *essaging while at the sa*e ti*e taking on so*e of the *ore co*plicated aspects of web ser+ices. The European Aerospace industr4 is proposing to use A"0 as its co**unication standard for sending
eb;M related < docu*ents between trading p artners. Further infor*ation about A"0 can be found on the Dru**ond 8roup site3ere.
&.2 ebM"
ebXM, Messa-in- Ser.ice offers a secure and reliable "#A=/9eb "er+ices based packaging3 routing and transport protocol as defined b4 the eb;M specifications. The ebM" is an open standard and as such is co**unication protocol neutral although the *ost co**on underl4ing protocols are >TT= and "MT=. ebM" essentiall4 offers a wa4 to echange eb;M based < docu*ents between different business applications using "#A=/9eb ser+ices.
&.G FT=
Fi'e !ransfer #rotoco' is a standard network protocol used to echange and *anipulate files o+er a TC=/I= based network such as the internet. FT= is built on a clientBser+er architecture and utilises separate control and data connections between the client and ser+er applications. FT= is also often used as an application co*ponent to auto*aticall4
transfer files for internal functions within progra*s. FT= can be used with userBbased password authentication or with anon4*ous user access.
&. FT="
Fi'e !ransfer Secure #rotoco' is an etension of FT= which adds support for the Transport a4er "ecurit4 @T" and the "ecure "ockets a4er @"" cr4ptographic protocols. FT=" should not be confused with "FT=3 an inco*patible secure file transfer subs4ste* for the "ecure "hell @""> protocol. It is also different fro* "ecure FT=3 the practice of tunneling FT= through an ""> connection
&.? >TT=
"yper!e/t !ransfer #rotoco' is used to reuest and trans*it files3 especiall4 web pages and web page co*ponents3 o+er the internet or other co*puter networks. In >TT=3 web browsers t4picall4 act as clients3 while an application running on the co*puter hosting the web site acts as a ser+er. >TT= is t4picall4 i*ple*ented across TC=/I= howe+er it can be i*ple*ented on top of an4 other protocol on the internet3 or on other networks.
&.1 >TT="
"yper!e/t !ransfer #rotoco' Secure is a co*bination of the >4pertet Transfer =rotocol with the ""/T" protocol to pro+ide encr4ption and secure identification of the ser+er. >TT=" connections are often used for pa4*ent t4pe transactions across the internet and for the echange of sensiti+e infor*ation between corporate business s4ste*s.
&.&% #FT=
Odette Fi'e !ransfer #rotoco' was de+eloped to offer a standard co**unication platfor* for the European auto*oti+e industr4 and has been in use since the *idB&1?%s. #FT= has also seen adoption across the retail3 white goods3 *anufacturing3 go+ern*ent3 transport3 insurance and banking industries to na*e but a few. The #FT= protocol is +er4 si*ple to use3 consisting of onl4 fourteen co**ands. The protocol is etre*el4 efficient3 allowing large trans*ission windows to be utilised whilst incorporating file restart3 data co*pression and securit4. #FT= has been designed to allow co*panies to co**unicate easil4 +ia point to point connections.
&.&& #FT= <.%
Odette Fi'e !ransfer #rotoco' .ersion 20 is the latest +ersion of the #FT= standard and has been designed fro* the outset to be used across the internet. #FT=< offers a
nu*ber of benefits o+er #FT= including data co*pression3 echange of digital certificates @to i*pro+e securit4 of trans*issions between trading partners3 it allows the handling of +er4 large files @o+er 2%%8b and offers support for additional character sets such as Chinese and )apanese. To date3 #FT= has *ainl4 been used in Europe howe+er as #FT=< has been designed to operate across the internet it can help trading partners
connect to one another all o+er the world. Man4 auto*oti+e *anufacturers in Europe ha+e been running #FT=< pilot pro'ects since <%%? and it is epected to be widel4 deplo4ed across production pro'ects during <%&%.
&.&< "FT=
Secure Fi'e !ransfer #rotoco' is a network protocol that pro+ides file access3 file transfer and file *anage*ent functionalit4 o+er an4 reliable data strea*. It was designed as an etension to the "ecure "hell protocol @""> +ersion <.% to pro+ide secure file transfer capabilit43 but it is also intended to be usable with other protocols as well. "FT= can be used in a nu*ber of different applications such as secure transfer o+er Transport a4er "ecurit4 @T" and transfer of *anage*ent infor*ation within ,=! applications. This protocol assu*es that it is run o+er a secure channel3 such as "">3 that the ser+er has alread4 authenticated the client and that the identit4 of the client user is a+ailable to the protocol.