|
Frequently Asked Questions
- What is EDI?
- Why do we need EDI?
- How do we implement EDI?
- How much does EDI cost?
- What is VAN?
- As a new trading partner, we understand that your company prefers the use EDI to exchange shipment information. Where do we begin?
- We are not EDI ready yet. What should we do?
- What EDI standard and version does Deringer support?
- Does Deringer support XML data?
- Does Deringer support Flat File data?
- Does Deringer support EDIINT (EDI over the Internet - AS1 and AS2)?
- What communication protocols does Deringer support?
- What VAN do you recommend to exchange EDI documents with Deringer?
- We submitted a New Partner Package form, but no one has contacted us yet. Who should we contact to find out the status?
- How do we test exchanging transactions with Deringer?
- Where and how do we obtain Deringer's EDI or XML requirements or specifications?
- Who should we contact if we have some questions regarding Deringer EDI or XML mapping requirements?
- How do we begin the mapping process?
- Does Deringer provide mapping services if we decide to setup EDI in-house?
- Does Deringer provide EDI 997 Functional Acknowledgement?
- We did not receive 997 Functional Acknowledgement for the EDI document that we sent. What should we do and who can we contact?
- If we send some transaction data that contains errors, how can they be corrected?
Frequently Asked Questions - Responses
- What is EDI?
A: EDI stands for Electronic Data Interchange. EDI is the computer-to-computer exchange of business data (e.g., Purchase Order, Invoice) between companies using networks. It replaces the faxing and mailing of paper documents. EDI documents use specific computer record formats (e.g., segments and elements) that are based on widely accepted standards. However, each company may use the flexibility allowed by the standards in a unique way that fits their business needs.
Back to Top
- Why do we need EDI?
A: The EDI method of data exchange between companies represents a faster, more secure and reliable method of information exchange than does the method of exchanging paper documents. The computer-to-computer exchange of business data through EDI is much less expensive than the manual handling of paper documents. There is also a continuing need for most businesses to increase efficiency. Businesses are finding that they can reduce costs by automating B2B (business-to-business) processes with EDI. Money is saved through improving the speed and accuracy of electronic documents they exchange with their customers.
Back to Top
- How do we implement EDI?
A: EDI capability involves either buying or outsourcing the following components: Software for data translation and communications, mail boxing of EDI transactions through VANs (Value Added Networks), mapping and translation. Various partners will require VAN and Internet communications. A server or PC, communication devices (modems), and peripherals (network interface cards, hard drives) will be needed. Additional requirements include secured office space, monitored security, backups and redundant power. Additional software will be needed if integration of the EDI transactions with back office systems is desired.
Back to Top
- How much does EDI cost?
A: It depends if you are setting up an in-house EDI department or outsourcing EDI to a third-party service provider. In general, outsourcing is a better alternative if there is a lack of IT resources, EDI software, and infrastructure. However, setting up an in-house EDI department is more cost-effective for large corporations.
Back to Top
- What is a VAN?
A: VAN stands for Value Added Network. A VAN is responsible for the secure and reliable communication of EDI documents over the networks. VAN will interconnect with your business partner's VAN to exchange business data. Data can be tracked, resent, or deleted. Deringer uses a variety of communication methods such as VAN, FTP, AS2, and HTTP to exchange transaction data.
Back to Top
- As a new trading partner, we understand that your company prefers the use of EDI to exchange shipment information. Where do we begin?
A: Deringer prefers most companies to accept transactions via EDI because of cost and time savings. Once you are ready to begin your partnership with Deringer, submit the New Partner Package form and we will manage all requests based on business requirements. After we setup your trading profiles and establish a communication connection, we will contact your company.
Back to Top
- We are not EDI ready yet. What should we do?
A: Deringer prefers most companies to send data in EDI format. Once you are ready to begin your partnership with Deringer, submit the New Partner Package form. However, if EDI is not a viable option for your company right now, other available options include sending XML data, Flat file (e.g., CSV) data, or entering data on a electronic form (AIMS application).
Back to Top
- What EDI standard and version does Deringer support?
A: Deringer makes every effort to keep up with the EDI Standards. Currently, the only supported Standard is ANSI X12 Version 4010.
Back to Top
- Does Deringer support XML data?
A: Yes, Deringer supports XML data. We do accept XML data on certain transactions such as the Consolidated and Non-Consolidated Invoice, and Warehouse Order transactions.
Back to Top
- Does Deringer support Flat File data?
A: Yes, Deringer supports Flat File data. We do accept Flat File data in several formats such as Microsoft Excel CSV format, Microsoft Access format, or a proprietary format.
Back to Top
- Does Deringer support EDIINT (EDI over the Internet - AS1 and AS2)?
A: Deringer recognizes the potential cost-savings inherent to EDIINT. In fact, our preferred communication method is through the EDIINT (AS2). We support both AS1 and AS2 standards.
Back to Top
- What communication protocols does Deringer support?
A: Deringer supports most common communication protocols VAN (Value Added Network), AS2 (Application Statement 2), FTP (File Transfer Protocol), HTTPS (Hyper Text Transfer Protocol over SSL) and SMTP (Email).
Back to Top
- What VAN do you recommend for us to exchange EDI documents with Deringer?
A: Deringer connects to Inovis VAN to exchange EDI documents with other VANs or EDI providers. We are able to exchange EDI documents directly through VANs like Inovis, Sterling Commerce, and GXS. If you use a different VAN, or your service provider uses a different VAN, make arrangements to have your VAN or provider set up an interconnection to one of these providers.
Back to Top
- We submitted the New Partner Package form, but no one has contacted us yet. Who should we contact to find out the status?
A: All completed forms will be examined by the EDI Project Coordinator first and then forwarded to an EDI Business Analyst, who handles your account. If your company does not get a response from one of our EDI team members (Contact information is on our Contact Us pages), please contact the EDI Project Coordinator, Kristi Yelle, at: (518) 298-7441; Fax: (518) 298-7407; E-mail: kyelle@anderinger.com.
Back to Top
- How do we test exchanging transactions with Deringer?
A: Deringer employs a strict testing regimen to ensure the EDI process is working before deploying to production. Deringer's EDI team performs Unit and Integration testing before providing the business teams with transaction sets to validate the business data. Once the testing is complete, it is followed by a two-week parallel testing (conditional live) period. Once the parallel is satisfactory, it is ready to go live.
Back to Top
- Where and how do we obtain Deringer's EDI or XML requirements or specifications?
A: You can request EDI or XML specifications by contacting the EDI Project Coordinator, Kristi Yelle, at (518) 298-7441 or E-mail: kyelle@anderinger.com.
Back to Top
- Who should we contact if we have some questions regarding Deringer's EDI or XML mapping requirements?
A: For specific EDI or XML mapping questions regarding Deringer's requirements, please contact the EDI Project Coordinator, Kristi Yelle, at (518) 298-7441 or E-mail: kyelle@anderinger.com.
Back to Top
- How do we begin the mapping process?
A: Deringer provides both EDI and XML implementation guides that specify EDI, XML and Deringer's business requirements. These guides indicate which segments and elements are mandatory, optional, or conditional. In addition, they also specify the acceptable codelist values to send depending on the transaction type. Each guide also includes sample data for your reference. Use these implementation guides to create mapping specifications before starting the mapping process.
Back to Top
- Does Deringer provide mapping services if we decide to set up EDI in-house?
A: Unfortunately, Deringer's primary focus is to forward processed data accurately and promptly to US Customs and Border Protection, as well as its warehouses. Therefore, Deringer does not provide specific consulting to any partners on EDI. However, Deringer can refer you to a service provider that specializes in providing support on mapping. In addition, your VAN or EDI service provider can also provide support on mapping.
Back to Top
- Does Deringer provide EDI 997 Functional Acknowledgement?
A: Yes, Deringer is able to acknowledge all EDI documents received from partners by responding with an EDI 997 Functional Acknowledgement per partner request.
Back to Top
- We did not receive 997 Functional Acknowledgement for the EDI document we sent. What should we do and who do we contact?
A: Transmission of EDI transactions will be acknowledged by an EDI 997 Functional Acknowledgement. It is the sender's responsibility to verify that Deringer has acknowledged the transmissions and has taken appropriate action if the expected acknowledgments have not been received within the time specified by both sender and receiver. Please check your EDI system, contact your EDI VAN, or provider to investigate if the EDI document was transferred to Deringer's mailbox before contacting Deringer EDI team members.
Back to Top
- If we send some transaction data that contains errors, how can they be corrected?
A: If the transmitted data contains errors, inform a Deringer EDI team member immediately and email or fax the corrected data to the branch contact.
Back to Top
|