Technical Interview Questions and Answers :: EDI
VAN a Value Added Network, often referred to as an EDI VAN, is a private network dedicated to the secure exchange of EDI data. Trading partners obtain an account with an EDI VAN such as GXS VAN, Sterling, EDS/ELIT, COVISINT INTERCONNECT etc. This account serves as an electronic mailbox for sending and receiving electronic documents.
Internet EDI is another way of communication, itâ€™s similar to OFTP2. You r partner can send you the data to your server via Internet or vice versa.
EDI Standard : ANSI X12, UCS, EDIFACT, VDA, TREDACOM etc.
Application Format Standard : IDoc, Delimited Files, CSV etc.
The ST segment is the transaction set header. The ST purpose is to indicate the start of a transaction set. The ST01 is the Transaction Set Identifier Code. The ST01 uniquely identifies a transaction set. The ST01 will identify if a file is a 997, 835 or 277.
AK5*A~ ÃŸ AK501 = A, transaction set accepted
A â€“ Accepted
E â€“ Accepted with Errors
R â€“ Rejected
AK9*A*1*1*1~ ÃŸ AK901 = A, file accepted
A - Accepted
E - Accepted, But Errors Were Noted.
P - Partially Accepted, At Least One Transaction Set Was Rejected
R - Rejected
Contact the trading partner to resend the file.
AS1 : AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet
AS2 : AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.
Files are sent as "attachments" in a specially coded SMIME message (an AS2 message)
AS2 messages are always sent using the HTTP or HTTPS protocol (Secure Sockets Layer â€” also known as SSL â€” is implied by HTTPS) and usually use the "POST" method (use of "GET" is rare).
AS3 : AS3 (Applicability Statement 3) is the draft specification standard by which vendor applications communicate EDI (or other data such as XML) over the Internet using File Transfer Protocol (FTP).
Request for quotation 840
Response to request for quotation 843
Purchase Order 850
Acknowledge Purchase Order 855
Change Purchase Order 860
Acknowledge Change Purchase Order 865
Step 3-Physical Distribution
Notify Shipment 856
Process Invoice 810
Process Invoice (Credit / Debit) 812
Show Payment Status 820
855 : Used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order.
855 is acknowledge for 850
997 : Used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. 997 generally indicates EDI standard problems rather than business rule errors
997 is Acknowledge for all transaction.
It result of error checking by the trading partner's business application program.
No, it will cause an infinite loop.