HELLA business needs
EDI (Electronic Data Interchange) , that is, electronic data interchange, is mainly to realize the exchange of business system data between two enterprises. For example, company A can send orders, delivery plans, inventory inquiries, etc. to company B through the electronic data exchange platform, and company B ships the goods on time and responds to the delivery notice and invoice information.
The main functions of the EDI system:
· EDI message transmission
· EDI message translation
· Business system integration
So what kind of business data interaction does Hella expect to have with its suppliers through the EDI platform? Please see the image below:
| Business code |
effect |
direction |
| DELFOR |
delivery plan |
Supplier receives |
| DESADV |
Shipping notice |
Supplier sends |
Among them, DELFOR ( Delivery schedule for component supplier ) represents the customer demand forecast, which refers to the material demand sent by the buyer to the supplier in a period of time in the future. In the automotive industry, this does not act as a true purchase order but just a purchase forecast, allowing suppliers to manage raw materials and other resources to ensure they have the ability to ship when a purchase order is received. The main business contents include supplier code, product material number, unloading location, order number, delivery plan number, delivery date and delivery quantity, etc.
DESADV means a delivery notice to inform the buyer that the goods have been dispatched. The main business contents include goods information, packaging information, order-related information and estimated time of arrival.
Transport protocol used by HELLA
In this case, Hella uses the OFTP/OFTP2 transmission protocol, which is the abbreviation of Odette File Transfer Protocol , a transmission protocol proposed by Odette for transmitting EDI messages. Its message encryption & signature and EERP ( End-to-end-response , used to notify the sender that the file has been successfully received) and other features ensure the safety and reliability of the business file transfer process.
To connect Hella with OFTP/OFTP2 , the following information needs to be specified:
( 1 ) Hella OFTP configuration information:
Hella SSID/Odette ID（HellaSSID）
Hella Password ( Hella SSID password)
Remote Host ( Hella remote host address)
Port ( Hella OFTP receiving port)
( 2 ) Vendor OFTP configuration information:
Odette Identifier/SSID Code (Supplier SSID )
SSID Password (vendor SSID password)
Remote Host ( vendor remote host address)
Port ( vendor OFTP receive port)
HELLA EDI Solutions
At present, most of the implementation solutions used by our Hella supplier customers are Oracle database solutions. After the received DELFOR message is successfully parsed, it will be written into the ERP system, and then the relevant delivery notification information will be read from the ERP to generate the DESADV message. Send to HELLA . The above steps can be set to automatically receive and parse, generate and send, and realize unattended and seamless connection with the database.
The EDI file conversion process is divided into two parts: analysis and generation. The system can integrate the EDI system with the enterprise database according to the actual business needs . The specific business process is shown in the following figure:
With the help of EDI platform, it can help enterprises integrate supply chain, reduce inventory, and achieve lean production. Of course, according to the actual IT conditions of customers, different EDI solutions can be selected, such as: Excel , XML , IDoc , Database , etc. The specific implementation methods will be decomposed next time ~
For more EDI -related knowledge, please visit http://www.kasoftware.com , or follow our WeChat public account: kasoftware , we will provide you with complete technical support and the latest EDI success stories.