How the System Processes Manifest Data Imported From RouteView

The RouteView software processes the order information downloaded from the Eclipse system and creates sequenced truck routes that equate to manifests in Eclipse. When the routing process is completed, RouteView creates a file named ROUT~brnch#.RNC and places the file in the Eclipse system's msg-in shared folder.

The Eclipse system polls the msg-in folder and processes the data.

Successful Processing

For successful processing of an import file, the system does the following:

Creates a manifest from the imported file for each ship via RouteView processed.
Sends the following messages to the user or message group identified in the Routing Administrator control maintenance record:

Routing upload for branch branch# is complete.
The following manifest was created: manifest#.

Prints pick tickets for each order on the branch default printer, or the pick ticket override printer assigned to the ship via, in reverse route sequence.

For example, for a manifest with 10 stops, the system prints the pick ticket for the tenth stop, followed by the pick ticket for the ninth stop, and so forth.

The setting in the Hold Pick Ticket For Routing Interface SVIA control maintenance record determines when the pick ticket prints.

Updates the order as follows:

Changes the ship via to the ship via indicated by RouteView.
Changes the stop number in attribute 24 of the ledger log file to that indicated by RouteView.
Adds the following routing entries to the change log:
The old and new stop number, or a message that it was not changed.
The old and new ship via, or a message that it was not changed.
A reference to the manifest to which the order was added.

Error Handling

If an error occurs during the upload process, the system sends the following summary message to the user or message group designated in the Routing Administrator control maintenance record:

Routing upload for branch branch# is complete. No manifests were created. N errors during processing.

The following table lists the errors that can prevent RouteView from creating manifests. The table shows the error and the message that the Eclipse system sends.

Error	Message
Sales order already on manifest	Could not add salesorder# to manifest manifest#1. Salesorder# is already on manifest manifest#2.
Invalid sales order #	Invalid sales order #.
No data in upload file	No data in Routing upload ROUT~branch#.RNC file.
Orders sent but not routed	Routing upload for branch branch# is complete. The following manifest was created: manifest#1. Warning!!! The following orders were not routed: salesorder#1 salesorder#N. For example, if the Eclipse system exported 100 orders and imports manifest data for only two orders, the message lists the 98 unrouted orders. Note: The system stores the last sent orders temporarily to provide the detail in the above message. If the next upload includes manifest data for two of the 98 remaining orders, the system does not include a message that 96 orders still remain unrouted.

In some cases, the system processes manifest data that contains errors. The following table explains what can occur and the action the system takes.

Error	Action
Invalid Ship Via	If the manifest data received from the third party software contains an invalid ship via, the Eclipse system updates the order and creates a manifest using the imported value.
Canceled Sales Order Generation	A sales order generation that has been canceled since it was exported to the routing software does not create an error. The system places the order on the manifest and displays "Warning!!" below the order number, because the ship date on the added canceled generation is blank and consequently not equal to the manifest ship via.
Multiple orders for the same stop	Orders uploaded as being on the same stop with different times cause estimated delivery time data corruption; however, the system still adds the orders to the manifest.
Invalid or non-existent customer ID	An invalid or nonexistent customer ID is acceptable, because the order number is the key.
Multiple drivers	If multiple drivers are specified, the driver identified on the last stop (highest stop number) is updated on the header of the manifest.
Multiple ship dates	The only date that is utilized from the import file is the Route Start Date for the last stop. This is used as the Ship Date for the manifest. Additional dates for individual orders are not captured or used. Only the arrival time is posted on the manifest. No ship dates are modified on the orders
Multiple route times	If multiple route start times are sent, the values for the last stop are used for the header of the manifest.
Different branch or invalid order ID	The system does not add orders for another branch or invalid order IDs to the manifest and does not generate an error.