Overview Order information is exported to the 3 rd party routing software by a phantom process in Eclipse. Users may opt to schedule the phantom to process at a regular time and create the download files or choose to manually initiate the process as appropriate. The information exported is provided in 1 comma separated variable (csv) file which provides customer and order information. Configuration Parameters Routing Administrator Control Record: This is a branch specific control that notifies the Administrator of all manifests that were automatically created by the 3 rd party routing software import or of any errors that occurred during that import: The Communication Method may be configured as Message or Tracker based on user preference. Routing Ship Vias Control Record: This is a branch specific control that allows you to define the default Ship Vias that will be selected for download to the 3 rd party routing software during the Order Download process: The print phantom respects the Routing Ship Vias control record and may or may not print pick tickets (in a non-rf environment) immediately upon Sales Order Entry for these Ship Vias based on the Hold Pick Ticket Print for Routing Interface SVIA control. Copyright Epicor Software Corporation 2016. All rights reserved Page 1
Hold Pick Ticket Print for Routing Interface Ship Vias Control Record: This control will either stop the pick tickets from printing until the 3 rd party routing software import is complete and the manifests are created Y, or it will print the pick tickets immediately upon escaping from the Sales Order so the products can be staged N : Export Driver: Order Export: Routing Order Exporter is the driver that initiates communication of customer and order information to the 3 rd party routing package. It is located on your System>Custom Menu. Once a branch is entered, Eclipse will automatically default the ship via field to the ship vias that are defined in the Routing Ship Vias control file. If the user wishes to manually override the default ship vias they may do so by altering the Ship Via input. Once the export selection parameters are filled out to the users specifications they may schedule the export for a future time or begin the export immediately by using the Schedule and Begin hotkeys. The Mutli hotkey is used to enter or manipulate multiple Ship vias. All fields on this screen are required. The driver values select all invoiced sales order generations with a ship date in the range of dates and a ship via and ship branch matching the inputs. It will exclude all invoices within the date range that are already on a manifest. Copyright Epicor Software Corporation 2016. All rights reserved Page 2
Export File Layout: Order File: When the Routing Order Exporter is run a file is created called ROADORD~branch# in the Eclipse systems msg-out folder, where the branch# is the branch specified in the driver. The ROADORD~branch#.RNC file contains information as shown in the layout below. Order Export File Information Field Field Name Length Example 01 Bill ID* Character The Bill ID does not contain spaces and is unique. The Order ID # is used. 02 Location ID* Character The Location ID is unique for each customer. This Customer ID # is used. 03 Location Code Character Location ID extension / suffix 04 Location Character The customer name is used. 05 Address* Character Primary Ship-To physical address. 06 Address2 Character Secondary Ship-To street address or description of primary address. 07 City* Character Ship-To City 08 State* Character Ship-To State 09 Zip* Character 5-digit Ship-To postal code (6 digits for Canada) 10 Plus4 Character 4-digit postal code extension. 11 Arrival Date* Character Format: MM/DD/YYYY (includes the / delimiters) 12 Shipper Character Name of shipper 13 Pieces Integer Total pieces for each bill (qty on order). 14 Weight Integer Total weight for each bill. 15 Cube Decimal Total cube for each bill. 16 Units Decimal Relative unit of measurement. 17 Units2 Decimal Additional relative unit of measurement. 18 Domicile* Character DC Distribution Center is used. 19 Cargo Type Character Cargo type code (D = Delivery) 20 Appointment Integer Format = HHMM in military time (no colon) 21 Required Character Not used 22 Standard Trip ID Character The Ship Via is used. This is a key field. 23 Note1 Character Delivery instructions 24 Note2 Character Comment 25 Note3 Character Comment Upon successfully writing the files to the msg-out folder, a message/tracker is sent to the Routing Administrator user indicating that Routing order file download to branch branch# is complete Error Handling: If the Routing Order Exporter finds no invoices matching the driver parameters, an Administrator receives the message: No orders were selected for download to route for branch branch# Copyright Epicor Software Corporation 2016. All rights reserved Page 3
Send Manifest Information TO Eclipse Overview: The 3 rd party routing package uses the downloaded orders and creates sequenced truck routes that equate to manifests in Eclipse. When the routing process is completed, a file is uploaded to create a manifest in Eclipse for each route and update the orders with routed information. Import Process: The 3 rd party routing application creates a file named ROUT~branch#.RNC and places the file in the Eclipse systems msg-in folder. Eclipse polls the msg-in folder and processes, archives and deletes the file. Manifest File: The posting file contains information as shown in the layout below: Manifest Import File Information Value Length Length Eclipse Example Sum Utilization Ship-To Entity ID 15 15 None 29583 [Numeric] Order # Order.Gen 15 30 Added to Manifest Order #.Invoice gen Field Description Customer ID Holding Place 40 70 Ship Via String 17 87 Changed on order key to manifest UPG UPS GROUND Stop Number Numeric 3 90 Key to sequence on 1 manifest Arrival HHMM Military 5 95 The added to 1810 the manifest Arrival Date YYYYMMDD 9 104 None 20041206 Depart HHMM Military 5 109 None 1820 Depart Date YYYYMMDD 9 118 None 20041206 Holding Place 16 134 Route Start HHMM Military 5 139 Manifest Header 0800 Start Route Start YYYYMMDD 9 148 Manifest Header 20041206 Date Ship Date Driver ID String 8 156 Manifest Header JUSTINW Driver Line Feed Char 10 1 157 A successful processing of an import file notifies the Routing administrator with the following message/tracker: Routing upload for branch branch# is complete. The following manifest was created : manifest# Copyright Epicor Software Corporation 2016. All rights reserved Page 4
Additionally, if the control record Hold Pick Ticket Print for Routing SVIA is answered Y, picktickets for every order imported are printed on the branch default printer (or Pickticket override printer by shipvia) in reverse route sequence. For example, a manifest with 10 stops (1 order per stop) shall print the 10 picktickets in sequence of 10, 9, 8 etc. printing the first stop last. Updates to Eclipse: Order updates: The shipvia of the order is changed to the one indicated by the 3 rd party routing package. A reference is made in the order change log to indicate whether or not a change was made (see below) The stop number imported by the 3 rd party package is stored in the ledger log file (attribute 24). The order change log is updated for each order imported by the routing software. The post includes the following details: 1. Old and new shipvia (or message that it was not changed) 2. Old and new stop # (or message that it was not changed) 3. Reference to the manifest the order was added to. A sample change log post: Change Log Viewing Change Log for : S1427983 ShipDate/Inv# :.001 %User ID(Date(EST(Port(Comment- PHANTOM 312/06/04304:33pm3hantom3**Routing** 3 3 3 3Stop number changed to 1 3 3 3 3Ship via was not changed 3 3 3 3S1427983.001 added to manifest M0004583 Manifest Updates: A manifest is created for each ship via uploaded by the 3 rd party routing package. A message is sent to the administrator detailing all the manifests created during an import. Each order is placed on a stop according to the stop number uploaded. The Start of the manifest is the uploaded Route Start. The delivery times of the manifest are the uploaded Arrival s for each stop. Copyright Epicor Software Corporation 2016. All rights reserved Page 5
Error Handling: Errors are sent to the Routing Administrator via an Eclipse system tracker or message. In the event of an error during the upload process, the administrator may receive errors like the ones shown below: Sales order Already on a manifest message = Could not add sales order# to manifest manifest#1. Sales order# is already on manifest manifest#2. Where manifest#1 is the manifest created for the shipvia in the processed upload and manifest#2 is the manifest the order is already on. No data in upload file message = No data in Routing upload ROUT~branch#.RNC file Orders sent but not routed message = Routing upload for branch branch# is complete. The following manifest was created: manifest#1. Warning!!! The following orders were not routed: sales order#1 sales order#n Note: The last sent orders are stored only temporarily to provide this detail. Thus, if 100 orders were sent down and a file imported that just had 2 orders, the message would include 98 unrouted orders. When additional files are imported in without any further exports, no unrouted orders are identified. If the 3 rd party package imports an invalid shipvia, Eclipse will still update the order and create a manifest with the imported value. A sales order generation that has been cancelled since it was exported to the routing software will not create an error. The order will be placed on the manifest and a Warning!! will appear below the order # (because the ship date on the added cancelled gen is blank and consequently not equal to the manifest ship via) Orders uploaded on the same stop that have different times will cause estimated delivery time data corruption; however, the orders are still added to the manifest. An invalid or non-existent customer id is acceptable. The order is the key. If multiple drivers are specified, the driver identified on the last stop (highest stop number) is updated on the header of the manifest. 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. No ship dates are modified on the orders. If multiple route start times are sent, the values for the last stop are used for the header of the manifest An order for another branch or an invalid order id will not be added to the manifest. It will produce an error that is sent to the Routing Administrator. Copyright Epicor Software Corporation 2016. All rights reserved Page 6