EDI Messages
Short Description
EDI Messages...
Description
http://www.edibasics.co.uk/
EDI Messages 1.1
Other Oth er Pict Picture ures: s: sour source ce doc doc Edi Edi Genera Generall prese presenta ntation tion
Edi Messages to sap Idocs: EDI message
Standard
SAP Message
SAP Idoc
Delfor In
EDIFACT
DEI!"
DEF#$%&
Del'it In
EDIFACT
"E()IT
"E()IT%&
DEI!"
If no kanban DEF#$%& nu*ber
Desad+ #ut EDIFACT
DE"AD,
DE,$-%
In+oic In
EDIFACT
I!,#IC
I!,#IC%&
Delins In
#DETTE
DEI!"
DEF#$%&
Caldel In
#DETTE
"E()IT
"E()IT%&
A+iep #ut #ut
#DETTE
DE"AD,
DE,$-% DE,$-%
In+oic out
#DETTE
I!,#IC
I!,#IC%&
01%2 In
,DA
DEI!"
DEF#$%&
01&2 In
,DA
"E()IT
"E()IT%&
01& In
,DA
DE"AD,
DE,$-%
Del'it In
EDIFACT
Comments if kanban or transport nu*ber or
transport
Integrate custo*er de*and EDI message
Standard
SAP Message
SAP Idoc
Delfor In
EDIFACT
DEI!"
DEF#$%&
Del'it In
EDIFACT
"E()IT
"E()IT%&
DEI!"
If no kanban DEF#$%& nu*ber
Desad+ #ut EDIFACT
DE"AD,
DE,$-%
In+oic In
EDIFACT
I!,#IC
I!,#IC%&
Delins In
#DETTE
DEI!"
DEF#$%&
Caldel In
#DETTE
"E()IT
"E()IT%&
A+iep #ut #ut
#DETTE
DE"AD,
DE,$-% DE,$-%
In+oic out
#DETTE
I!,#IC
I!,#IC%&
01%2 In
,DA
DEI!"
DEF#$%&
01&2 In
,DA
"E()IT
"E()IT%&
01& In
,DA
DE"AD,
DE,$-%
Del'it In
EDIFACT
Comments if kanban or transport nu*ber or
transport
In this case3 custo*er sends onl4 idoc 5delfor6 :
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 4905
Transport Label Barcode-enabled incl. VDA 4913 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:
=M!T%.
=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;$"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:
HTT=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= 3 that the ser+er has alread4 authenticated the client and that the identit4 of the client user is a+ailable to the protocol.
View more...
Comments