Support

Downloads

• Arch Bay
• Aristokraft
• Armstrong
• Masco Retail Cabinet Group {Kraftmaid}
• Norcraft
• Schrock
  
• Wellborn
  
  

Help

• Download the generic help file for EDI clients.
• View the generic On-Line help file for EDI clients.

Faq

• How does the client connect to the 20-20 system?
  The EDI client software connects to our server using HTTP, through a special component which is part of Internet Explorer. This component is specifically designed to transmit and collect XML from a server using HTTP. Our server, actually, acts as a Web Service. It receives a big chunk of XML, representing the PO, and stores it until it is written to a Notes database for replication to the manufacturer's system. The client must connect to the Internet to send his orders. When Internet Explorer is configured correctly, our client software will request a connection to the ISP if the user hasn't already connected. There is a way to "stack" orders on the disk, but this requires a few minutes of training. In short to order, typically, a person has to connect to the Internet, which is parallel to the need to connect to get their emails.
  
• How are Acknowledgements (ACK) handled at the client end?
  First your system needs to generate a file for each message the manufacturer wants to send. A special scheme has been defined for transmission of messages to 20-20. Typically the manufacturer will send only one message (file) for each order. The message can indicate that the order is Accepted or Refused. But one could at a future time send additional messages to indicate to the client, for example, that the order is in the paint shop, or that the order is on the truck and leaving the manufacture. These messages are relayed to our server by replication in a Notes Database. The message's code indicates to us what to do with it. Typically an order acknowledgement would be sent to the dealer via e-mail. If you send an "accepted" message, you may join a text with the message. For a refused message, you could enter a reason and special instructions for instance. Other less important messages may only be attached to the order, in the database, as information the dealer can access on the Dealer Web Site. 20-20 Design, or 20-20 Project for that matter, display no information on the status of the order. We also install an icon on the client's desktop, giving him access to the web site with the information on his orders.
  
• How do we make the EDI dial up automatically ?
  1. In Windows, click Start, point to Settings and click Control Panel.
  2. In Control Panel, double-click the Internet icon.
  3. Under the Connection tab, click to select "Connect to the Internet as needed."

  NOTE: This setting also effects the behavior of Microsoft Internet Explorer.

• Error in EDI: "The date in the certificate is invalid or has expired."
  You only need to either install a new version of Internet Explorer,
  or download from windowsupdate.microsoft.com the "Root Certificates Update".

• Repeated identical error when trying to send an order:
  Sometimes, after changing certain settings for EDI, you always get the same error. For example you might have changed the dealerID or the Password a few times, but you always get the same message Invalid DealerID or Password. The recurring error is caused by having a previously unsuccessful attempt to send an order. A copy of the previous error is then kept in the 2020\EDI\60\SEND directory, or in certain cases the root of the drive where 2020 is installed. Previous unsuccesful orders are files finishing with .XMO . So, to start anew, try emptying that directory of any .XMO files.

• Time Zone Problems:
  Sometimes orders will not pass thru if the time zone is not set correctly on the sender's computer.

• Proxy Errors:
  When using a proxy, and when connecting to gate.2020edi.com to place orders, make sure that your proxy lets https secure web sites pass through. Your proxy, in this case, must be open for Port 443.

• Multiple Intallations of 20-20 Design:
  Make sure you only have ONE version of 20-20 installed on your machine. Problems often occur when two version of 20-20 are installed on the same machine, in two different directories, such as C:\2020V60 and C:\2020V61.