The following are control maintenance records used for RouteView, along with additional setup requirements.
Complete the following control maintenance records:
Indicate whether the system holds the printing of pick tickets for routed orders until after the system receives the routing data from the third party routing software.
Y – The pick ticket prints after the third party software has routed the order and sent the routing data back to the Eclipse system.
N – The pick ticket prints before the system sends the order data to the third party routing software.
For each branch, enter the routing administrator settings by completing the following fields:
Branch – Enter the branch for which to assign the routing administrator settings.
Administrator to Receive Communications – Enter the user or message group to whom to send routing communications and error messages.
Communication Method – Select whether the system sends manifest comment notification as a message or a tracker.
For each branch, enter the ship vias to route by default to the third party routing software. If you leave this record blank, defaults are not defined.
Before using the routing interface, in Ship Via Maintenance create ship vias for each routing interface zone.
Note: Each ship via you create for the routing interface must also be designated in the routing software.
See Also: