EDI ŠABATA. Implementation guideline for Electronic data interchange (version 1.0)

Size: px

Start display at page:

Download "EDI ŠABATA. Implementation guideline for Electronic data interchange (version 1.0)"

Joan Hutchinson
7 years ago
Views:

1 EDI ŠABATA Implementation guideline for Electronic data interchange (version 1.0) 1/5

2 Version history Ver. Date Description Author Reviewer First release R.Doležal, J. Škrobák - artipa Table of content Version history... 2 I. Purpose of EDI... 3 II. EDI support and contacts... 3 III. EDI messages... 3 IV. EDI connection... 4 V. Setup process /5

3 I. Purpose of EDI The provision of services and goods is a highly integrated business process. This is supported by an integrated flow of information between suppliers and customers. We were looking for solutions to improve processes in the supply chain. We wanted to optimize the flow of information in shortening of delivery times, reliability and costeffectiveness on both sides. For this purpose, helps us modern communication technologies - EDI (Electronic Data Interchange) and our cooperation with the EDI provider artipa.software. The EDI has the following advantages: Improves data accuracy Accelerates information exchange Reduces complexity of exchange Reduces the need for human factors The data are typically exchanged between two information systems. You can eliminate the need to re-enter data from paper or documents and therefore prevent potential data entry errors. EDI saves more than 10% of cost for eliminate these errors. The information workflow is highly important for the exchange. Time between send and receive of EDI messages is very short. All of EDI process are automatic under standardized data format. EDI exchange allows companies and plants using different Information or Accountant Systems to achieve computer-to-computer (or server-toserver) exchange of business documents (for example order, invoice, dispatch advice etc.) All of EDI transactions reduce personal assistance or reduce the cost of personal involvement. II. EDI support and contacts Technical support Sales and coordination support Operation times of the support support@artipa.com (Czech or English language only) sales@artipa.com (Czech or English language only) Monday - Friday, CET Please ensure that your request to support team contains name and GLN code. III. EDI messages Šabata supports these EDI messages: EDI message Meaning Sender Recipient ORDERS UN/EDIFACT D.01B EAN 010 Purchase order ŠABATA Supplier CONTRL UN/EDIFACT D.01B EAN 004 Technical Acknowledgement of ORDERS Supplier ŠABATA DESADV UN/EDIFACT D.01B EAN 007 Despatch advice Supplier ŠABATA INVOIC UN/EDIFACT D.01.B EAN 010 (signed - ISO ) Invoice with digital signature Supplier ŠABATA CONTRL UN/EDIFACT D.01B EAN 004 Technical Acknowledgement of DESADV and INVOIC ŠABATA Supplier AUTACK UN/EDIFACT D.94A Signature acknowledgement of INVOIC message ŠABATA Supplier APERAK UN/EDIFACT D.01B EAN 003 Application acknowledgement of DESADV and INVOIC ŠABATA Supplier All abovementioned message types are required by Šabata. In case of any question please contact us by to support@artipa.com. 3/5

4 IV. EDI connection 1 All EDI connections with Šabata are provided by the system artipa.businessportal (ABP) of artipa.software company. The ABP EDI network could be reached by following protocols or software tools: AS2 EDIVAN/X.400 ABPClient WEB EDI Peer to peer connection with other EDI VAN providers or suppliers who have their own AS2 solution Connection with other EDI VAN providers under X.400 worldwide nets. Direct secured HTTPS connection with artipa s client software for customers of artipa. For more information send us your request to sales@artipa.com Manual web user interface for suppliers who have no regular EDI solution and prefer simple use of web browser like E-shop with all its advantages and limits. For more information and detailed proposal send us your request to sales@artipa.com. EDI VAN network Suplier with own EDI VAN provider artipa EDI network Supplier with ABPClient (customer of artipa.software) Šabata artipa WebEDI Supplier with own EDI solution AS2, X.400, OFTP/2 Figure 1 - EDI situation for EDI ŠABATA and supported connections Supplier with web browser (without any EDI solution) 1 For detailed technical information see the EDI datasheet. 4/5

5 V. Setup process Request for EDI connection You (supplier) will send the request of connect to Šabata EDI community by to Artipa support team will send back to you a detailed information about EDI connection (EDI datasheet). You will complete the EDI datasheet and send it back to support@artipa.com. Test phase - connection Artipa support team will set the new connection with your side according to the completed datasheet. Test phase - message The focus of this test phase will be on the factual accuracy of EDI messages, EDI compliance standards and syntax correctness. During this phase we will exchange paper ( or current way) and electronic documents (in the parallel mode) until EDI messages will be correct for both sides. Productive phase Start of the productive EDI exchange will coordinate with Artipa EDI support team. This team will send the EDI agreement documents to supplier s side. Supplier will complete this agreement and sent it back to support team. From the date determined in the agreement will be exchanged agreed documents just in its EDI form. 5/5

Magna IT EDI services. Supplier Implementation guideline for Electronic data interchange

Magna IT EDI services. Supplier Implementation guideline for Electronic data interchange Magna IT EDI services Supplier Implementation guideline for Electronic data interchange Version 1.0 05.11.2009 Version history version date comment author reviewed 1.0 05.11.2009 Initial release Stefan