OverviewElectronic Data Interchange (EDI) is a means of transferring data between organizations by electronic means. Readysell has an EDI implementation that allows customers to transfer the following types of data to/from select suppliers:
...
EDI makes the process of placing orders and entering receipts automatic and seamless, allowing for gains in efficiency at both the customer and the supplier side.
Readysell EDI is based on the proved RObI platform and is available for any Readysell customer. If you would like to learn about which of your suppliers support Readysell EDI, please contact our office.
Purchase Receipts Supplier Purchase Orders Customer
Basic ConceptsWebSphere Interface TabCustomers who are using RObI should already be familiar with the WebSphere Interface Tab on Readysell. Because Readysell EDI is built on the RObI platform, this tab will also show orders and receipts being sent to/from suppliers.
For those unfamiliar, on the Readysell main menu you will see a "Web Sphere Interface" tab. If you click this tab you should see a list of the most recent messages sent and received by RObI. These include successful messages as well as any errors or warnings.
This information is primarily for the purpose of Readysell support, however you may also view this tab for information about recent interactions between Readysell customer and supplier systems.
EDI Business RulesBecause customer and supplier systems may not always have their data perfectly aligned, Readysell EDI operates on a number of business rules to reduce the incidences where manual intervention is required. Readysell EDI will also attempt to auto-correct certain data based on any manual intervention that is required to avoid requiring the same intervention for future orders.
Product MatchingWhen a customer places an order with a supplier over EDI, the customer's system sends across the
following fields: Product Code Product Supplier Code Product Supplier Barcode !worddavff7b7950ce484811898a3acbfd8c34e9.png|height=296,width=463!If the product supplier code is blank for the supplier being ordered from, the default supplier code will be used instead (the default supplier is the one set in the "Supplier" field). If the default supplier code is blank, then the product code will be sent.
Readysell EDI will then try to match to a product in the supplier's system based on the following (in the order specified):
...
To avoid errors, if more than one product is found (for example multiple supplier's using the same code) the match will be ignored.
- Exact match of customer "Product Code" to supplier "Mnemonic Code" (for EzyCode)
- Exact match of customer "Supplier Barcode" to supplier "Supplier Barcode"
- Exact match of customer "Product Supplier Code" to supplier "Mnemonic Code"
- Exact match of customer "Product Supplier Code" to supplier "Previous Product Code"
- Exact match of customer "Product Supplier Code" to supplier "Alternate Code"
Product CorrectionNote: This feature is not currently available for Pelikan Artline EDI.
If a product match cannot be found based on any of the rules above, the product will appear with the code "SPECIAL" in the supplier's system. The original product description will remain in the name field and the product code will be available for reference in the line notes field.
The supplier will have to correct the missing product by replacing the "SPECIAL" code with their own product code. When the EDI order acknowledgement is sent back to the customer system, Readysell EDI will automatically correct the product supplier code automatically. This will only affect the product supplier record for the supplier for which the order was placed; no other supplier records will be changed. If no supplier record exists for the product supplier, then one will be created.
Replacements and SubstitutionsNote: This feature is not currently available for Pelikan Artline EDI.
If any products are added to the order at the supplier end, these products will be added to the bottom of the purchase receipt at the customer side.
WorkflowSending Purchase Orders (Readysell EDI)1. Customers should create a Purchase Order in Readysell as usual.
2. When the order is entered, the print functionality should be used as if the order as usual. 
...
To test this process you can enter any information into the "EDI Endpoint URL" field on a supplier record. This will allow you to perform the steps above without having to activate the EDI feature permanently. Once you have completed your testing, remove the data out of the "EDI Endpoint URL" field.
Sending Purchase Orders (Pelikan Artline EDI)1. Customers should create a Purchase Order in Readysell as usual.
2. When the order is entered, the print functionality should be used as if the order as usual.
...
- Confirm your order and click "Submit"
- You will receive an email confirmation from Pelikan Artline for your order.
Receiving Purchase ReceiptsNote: This feature is not currently available for Pelikan Artline EDI.
Once the supplier has processed the EDI order and voiced the customer, a purchase order acknowledgement will be sent to the customer system. This will appear as a regular "Purchase Receipt" in the customer system.
The receipt will contain the products and quantity that the supplier will be sending and will automatically correct any incorrect products on the order (as per the business rules section).
This receipt should be processed in the same way as any other purchase receipt.
Technical AspectsArchitectural Overview
RObI PlatformRObI runs as an ASP.NET application on top of a Microsoft Internet Information Server (IIS). RObI has been tested on Windows XP, Windows Vista, Windows 7, Windows Server 2003 (including R2) and Windows Server 2008 (including R2).
RObI Web InterfaceIf you access http://SERVER_HOSTNAME:8092/ from the internal network (and log in using the server's Administrator username/password) you will be presented with the following screen.
This is the RObI web interface and will provide you with access to the following features:
- Service List
- list of the accessible web service triggers and providers of RObI.
- Log Viewer
- real-time viewer for the RObI log file as well as access to the log files directory. This directory contains the log files for the last 30 days as well as all of the XML messages sent and received by RObI.
RObI ConfigurationRObI is configured in two places.
...
The ASP.NET web configuration file contains a number of configuration variables required for RObI. A description of the function of most of these flags can be found in this user guide. This file also contains the "Installation Path" and flags to turn on and off each of the integration features.
InstallationReadysell EDI installation must be handled by a Readysell staff member. Please contact our support team for assistance.
Supplier System- Go to System References and set Description of the following to True
- Type: WEB, Reference: DEALERORD-IN-ENABLE
- Type: WEB, Reference: DEALERORDACK-OUT-ENABLE
- For each customer:
- Place the customer's username/password into their Customer record as the EDI
...
- Enter the customer's EDI Endpoint URL into the relevant field
Customer System- Go to System References and set Description of the following to True
- Type: WEB, Reference: DEALERORD-OUT-ENABLE
- Type: WEB, Reference: DEALERORDACK-IN-ENABLE
- For each supplier:
- Place the customer's username/password into their Supplier record as the EDI
...