AFG EDI requirements details

AFG He has always been an expert in outbound logistics of automobile industry , Not only transport cars , It also provides modularity IT Solution , Used to receive 、 control 、 Interconnection and visualization and monitoring of the whole vehicle scheduling process .AFG As BMW Designated supplier , Specialized in docking logistics direction suppliers , And assist BMW Manage related logistics data . Zhixing helps many customers to complete and AFG Of EDI docking , This article will explain in detail AFG Of EDI demand .

One 、AFG EDI Demand overview

1、 Transmission data standards ：txt File format

Transfer protocol ：OFTP Implementation plan ：61-Excel,63-JSON

stay EDI During transmission ,AFG The demand must pass OFTP Transmission protocol transmission .txt Business data in the form of files , And the file needs to be AFG The virtual file name provided is named , The relevant business codes and functions are listed below .

because AFG The transmitted files are classified according to the business , As listed in the table below , It mainly includes ：

The supplier receives ： （611-612-613-619） Vehicle information （611-615-617-619） Address information （611-616-619） Color information Suppliers send ： （631-632-639） Port information

Business code	Business description	effect	Direction
611	Start Record Trasnport Order / Master Item Data	Transportation order / Header information of main material data	AFG→ supplier
612	Transport Order “Vehicle Specification”	Vehicle specification information	AFG→ supplier
613	Transport Order “Route Specification”	Route specification information	AFG→ supplier
614	Deviating Delivery Address	The delivery address is wrong	AFG→ supplier
615	Dealer master data and address	Dealer master data and address	AFG→ supplier
616	Master Item Data(Model/Color)	Main material data （ model / Color ）	AFG→ supplier
617	Additional address master data	Additional address master data	AFG→ supplier
619	End Record Trasnport Order / Master Item Data	Transportation order / Tail information of main material data	AFG→ supplier
631	Start Record for vehicle Movements	Vehicle movement starts recording	supplier →AFG
639	End Record Vehicle Movement	Vehicle movement end record	supplier →AFG

632*

because 632 More complicated , So the details are listed in the table below ：

Business code	Business description	effect	Direction
632(0)	Load Disposition	Load configuration description	supplier →AFG
632(1)	Entry booking of Compound, Port or Dealer	The courtyard , Admission booking of port or dealer	supplier →AFG
632(2)	Exit booking of Plant, Compound or Port	Exit factory , A reservation for a compound or port	supplier →AFG
632(4)	Service confirmation	Service confirmation	supplier →AFG
632(5)	COD (Change of Port of Destination) is used currently for LLP-Australia sent from LLP to BMW,During sailing the port of discharge can be changed	COD（ Change of port of destination ） It is currently used from LLP Send to BMW Of LLP- Australia During the voyage , The port of discharge can be changed	supplier →AFG
632(!)	“Yard Entry”: vehicle is ready for dispatch at a plant or fully managed compound	“ Yard ”： Vehicles are ready to be dispatched in factories or fully managed warehouses	supplier →AFG

originally EDI The system will AFG Sent to the supplier txt Format 61 The file is converted to Excel Send to supplier , Then the supplier sends JSON Format 63 File to know action EDI System , Convert it to txt Format through EDI Send to AFG.

Two 、AFG OFTP transmission

OFTP/OFTP2, yes Odette File Transfer Protocol Abbreviation , from Odette The organization's proposal for transmission EDI The transmission protocol of message . It's in line with the German Automobile Industry Association 4914/2, Or European Telecom transmission data exchange （Odette-Organization for Data by Tele Transmission in Europe） The advice of .

OFTP2 Make up for OFTP Lack of security , Message encryption is added 、 Message signature and EERP（End-to-end-response, The receiver is used to inform the sender that the file has been successfully received ） Signature .OFTP2 You can transfer files over a variety of networks , for example Internet、ISDN etc. .

OFTP The connector , Using the leading Internet 、 Safe EDI Transfer protocol OFTP2 Data communication .

added OFTP Details of the agreement , Please check out ：OFTP Protocol Brief

With the help of OFTP Port docking AFG Before , The first thing you need to do is Odette On the official website of Odette ID/ The purchase of certificates , The specific purchase process , Please check out ： apply Odette ID And Odette certificate

With the help of OFTP Port docking AFG, The following information needs to be clear

AFG OFTP Configuration information

• SSID Code（SSID Identity identifier ）
• Password（SSID password ）
• Version（OFTP Protocol version , The default is 2.0）
• Remote Host（ The host address ）
• Port（ Data receiving port , The default is 6619）
• Certificate（ certificate ）

supplier OFTP Configuration information

• SSID Code（SSID Identity identifier ）
• Password（SSID password ）
• Port（ Data receiving port , The default is 6619）
• Private Certificate（ Private key certificate , The certificate is in Odette Certificates purchased on the website ）
• Certificate Password（ Private key certificate password , For in Odette The password of the certificate purchased on the website ）

3、 ... and 、AFG EDI Solution

Supplier and AFG establish EDI System docking , Mainly involves 61* Our business is 611,612,613,615,617,616,619,631,632,639

Here is the main introduction 61 Use Excel,63* Use Json How to realize the mutual benefit EDI Seamless system docking .

1、 build workflow：

2、 Supplier receiving records & analysis

The sample workflow is as follows

（1）OFTP Port： For reception AFG It's from 611-612-613-619） Vehicle information ,（611-615-617-619） Address information ,（611-616-619） Of txt Log files ; （2）Excel Port: Will receive txt Record file to Excel file , And forward to EmailSend port （3）EmailSend Port： Will be converted Excel Documents are sent to customers by email

3、 Supplier generated records & send out

The sample workflow is as follows :

（1）JSON Port： JSON Port support will XML Data to JSON, And will JSON Data to XML, The customer calls the trading partner's Admin API Interface , take Json Format data to its trading partners . （2）XML Map Port： take JSON Port received converted to xml Of documents json Data is passed through XML Map Port to standard xml file , And forward to VDA port （3）VDA Port： take XML Map After port conversion xml File by VDA The port is converted to AFG Acceptable txt Record , And forward to OFTP port （4）OFTP Port： take txt Record according to AFG The request is named using virtual naming and sent to AFG EDI System .

The above scheme can realize automatic receiving and parsing & Generate send txt Record , Realize the relationship between suppliers and AFG Seamless docking of .

notes ： Some of the pictures and contents of the copywriting are from the Internet , The copyright belongs to the original author , If it infringes upon your rights and interests , Please contact us to delete , It's bothering you , We are deeply sorry .