13,094
edits
Changes
From Nordan Symposia
Jump to navigationJump to search
mLine 1:
Line 1: − + Line 13:
Line 13: − + Line 87:
Line 87: − + − + − + − + +
Text replacement - "http://" to "https://"
[[Image:lighterstill.jpg]]
[[Image:lighterstill.jpg]][[Image:EDI_Binarysmall.jpg|right|frame]]
An inter-company, application-to-application communication of data in standard format for business transactions. '''Electronic Data Interchange''' ('''EDI''') is a set of [[standard]]s for structuring information that is to be electronically exchanged between and within businesses, organizations, government entities and other groups. The standards describe structures that emulate documents, for example purchase orders to automate purchasing. The term EDI is also used to refer to the implementation and operation of systems and processes for creating, transmitting, and receiving EDI documents.
An inter-company, application-to-application communication of data in standard format for business transactions. '''Electronic Data Interchange''' ('''EDI''') is a set of [[standard]]s for structuring information that is to be electronically exchanged between and within businesses, organizations, government entities and other groups. The standards describe structures that emulate documents, for example purchase orders to automate purchasing. The term EDI is also used to refer to the implementation and operation of systems and processes for creating, transmitting, and receiving EDI documents.
The EDI (Electronic Data Interchange) standards were designed to be independent of communication and software technologies. EDI can be transmitted using any methodology agreed to by the sender and recipient. This includes a variety of technologies, including modem (asynchronous, and bisynchronous), [[FTP]], Email, [[HTTP]], AS1, [[AS2]], etc. It is important to differentiate between the EDI documents and the methods for transmitting them. While comparing the [[bisynchronous protocol]] 2400 bit/s modems, [[CLEO]] devices, and [[value-added network]]s used to transmit EDI documents to transmitting via the Internet, some people equated the non-Internet technologies with EDI and predicted erroneously that EDI itself would be replaced along with the non-Internet technologies. These non-internet transmission methods are being replaced by [[Internet Protocol]]s such as [[File transfer protocol|FTP]], [[telnet]], and [[e-mail]], but the EDI documents themselves still remain.
The EDI (Electronic Data Interchange) standards were designed to be independent of communication and software technologies. EDI can be transmitted using any methodology agreed to by the sender and recipient. This includes a variety of technologies, including modem (asynchronous, and bisynchronous), [[FTP]], Email, [[HTTP]], AS1, [[AS2]], etc. It is important to differentiate between the EDI documents and the methods for transmitting them. While comparing the [[bisynchronous protocol]] 2400 bit/s modems, [[CLEO]] devices, and [[value-added network]]s used to transmit EDI documents to transmitting via the Internet, some people equated the non-Internet technologies with EDI and predicted erroneously that EDI itself would be replaced along with the non-Internet technologies. These non-internet transmission methods are being replaced by [[Internet Protocol]]s such as [[File transfer protocol|FTP]], [[telnet]], and [[e-mail]], but the EDI documents themselves still remain.
As more trading partners use the Internet for transmission, standards have emerged. In 2002, the [[IETF]] published RFC 3335, offering a standardized, secure method of transferring EDI data via e-mail. On July 12th, 2005, an IETF working group ratified [http://www.ietf.org/rfc/rfc4130.txt RFC4130] for MIME-based HTTP EDIINT (aka. [[AS2]]) transfers, and is preparing similar documents for FTP transfers (aka. [http://www.ietf.org/rfc/rfc4823.txt AS3]). While some EDI transmission has moved to these newer protocols the providers of the [[value-added network]]s remain active.
As more trading partners use the Internet for transmission, standards have emerged. In 2002, the [[IETF]] published RFC 3335, offering a standardized, secure method of transferring EDI data via e-mail. On July 12th, 2005, an IETF working group ratified [https://www.ietf.org/rfc/rfc4130.txt RFC4130] for MIME-based HTTP EDIINT (aka. [[AS2]]) transfers, and is preparing similar documents for FTP transfers (aka. [https://www.ietf.org/rfc/rfc4823.txt AS3]). While some EDI transmission has moved to these newer protocols the providers of the [[value-added network]]s remain active.
EDI documents generally contain the same information that would normally be found in a paper document used for the same organizational function. For example an EDI 940 ship-from-warehouse order is used by a manufacturer to tell a warehouse to ship product to a retailer. It typically has a ship to address, bill to address, a list of product numbers (usually a [[Universal Product Code|UPC code]]) and quantities. It may have other information if the parties agree to include it. However, EDI is not confined to just business data related to trade but encompasses all fields such as medicine (e.g., patient records and laboratory results), transport (e.g., container and modal information), engineering and construction, etc. In some cases, EDI will be used to create a new business information flow (that was not a paper flow before). This is the case in the Advanced Shipment Notification (856) which was designed to inform the receiver of a shipment, the goods to be received and how the goods are packaged.
EDI documents generally contain the same information that would normally be found in a paper document used for the same organizational function. For example an EDI 940 ship-from-warehouse order is used by a manufacturer to tell a warehouse to ship product to a retailer. It typically has a ship to address, bill to address, a list of product numbers (usually a [[Universal Product Code|UPC code]]) and quantities. It may have other information if the parties agree to include it. However, EDI is not confined to just business data related to trade but encompasses all fields such as medicine (e.g., patient records and laboratory results), transport (e.g., container and modal information), engineering and construction, etc. In some cases, EDI will be used to create a new business information flow (that was not a paper flow before). This is the case in the Advanced Shipment Notification (856) which was designed to inform the receiver of a shipment, the goods to be received and how the goods are packaged.
==External links==
==External links==
* [http://www.doli.state.mn.us/edi_1.html EDI Introduction] — [[Minnesota]] Department of Labor & Industry website.
* [https://www.doli.state.mn.us/edi_1.html EDI Introduction] — [[Minnesota]] Department of Labor & Industry website.
* [http://www.anu.edu.au/people/Roger.Clarke/EC/EDIIntro.html EDI: An Introduction] — a visiting [[fellow]] on [[Australian National University]] website.
* [https://www.anu.edu.au/people/Roger.Clarke/EC/EDIIntro.html EDI: An Introduction] — a visiting [[fellow]] on [[Australian National University]] website.
* [http://www.elifecoupler.com/1-edix12.htm "The EDI Workflow" - by eLife Coupler]
* [https://www.elifecoupler.com/1-edix12.htm "The EDI Workflow" - by eLife Coupler]
* [http://www.edimatrix.demon.co.uk/aboutedi.htm "Introduction to EDI" document] -- on the site of a commercial EDI software supplier
* [https://www.edimatrix.demon.co.uk/aboutedi.htm "Introduction to EDI" document] -- on the site of a commercial EDI software supplier
[[Category:General Reference]]
[[Category:General Reference]]
[[Category:Computer Science]]
