This option is only available with the RoadNet Plugin.
In order for employees to access this screen, the “May Import Orders From Roadnet (also set MaySequence Permission)” checkbox on the Plugins Panel must be checked.
The checkbox Use Special Fix for Zero-Case Lines on the setup was added in September 2009. This checkbox correlates to the fact that RoadNet has the ability to route on only one package type at a time. For invoices that had both Cases and Kegs, RoadNet was able to function properly. The issue raised when an invoice had zero cases and only kegs in it. Since, the Keg column is the second column RoadNet assumed that the order was zero. If this checkbox is checked than we will populate the Case column of the export file with the Keg Qty for invoices that have only Kegs.
The RoadNet import allows partial import if there are specific issues encountered with the import file (lines with issues will be not be imported). Note that RoadNet prefixes the Route ID with the day number. In order for eoStar to match to the appropriate driver, this needs to be excluded during import. Because of this, eoStar will automatically exclude the first character from the Route ID on import.
How-to Import Files From RoadNet
The import file format must match the format used when exporting to RoadNet, otherwise eoStar will not be able to properly read it and apply updates to the routes. Here are the available formats, click a format’s link to download a spreadsheet containing the file structure for that format:
- Go to Orders > RoadNet Import.
- Click Setup.
- Click the Send Orders tab.
- Set the Import/Export Folder.
- Enter the Input File Name.
- This is the file that will be imported.
- Select the Export Format to use.
- This is the file format eoStar is expecting to import.
- Click Read Import File.
- View any Error or Warning messages by the drop down arrow.
- When finished making changes, click the command button Post Updates Now.
Troubleshooting Notes for Import Files From RoadNet
When the user exports the orders we store those orders in a state of “waiting to be imported”. Once you do an import, we consider those processed and won’t be looking for another import for those orders again. The idea behind this is to protect against over writing changes by mistake after they’ve been routed.
If you want to bring in a reroute file again, to adjust the route, you would need to exporte out of eoStar again to flag those orders as “Waiting to import”.