| Anchor | ||||
|---|---|---|---|---|
|
Search Optifacts User Documentation
| Live Search | ||||
|---|---|---|---|---|
|
Table of Contents (on this page)
| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
This document provides a detailed explanation of the job routing tables, the Routing Group tables, what their functions are and how they work together. Job routing is used to transfer jobs to an outside source or regional processing center for production and/or coating based upon account and product group mapping.
Priority Number Assignments - Layering
The routing system will best be set up to manage a set of rules in a hierarchical approach. It is important to remember that priority numbers are sorted from highest to lowest number and used to select routing rules in a specific order. The system will find the first match (highest priority number) based on the routing and/or group definition and use that rule to route a job. If a job does not match the definition of a routing rule it will then drop down to the next rule and try to match it. Once a match is made, the job will route to the specified site. The correct structure of the group table definitions is imperative. Priority Number, System ID and other fields are not mandatory but the priority number is mandatory in the Job Routing Reason and Control Manager Menu. Although not mandatory, the priority number is also useful when used in the Group Control table to assist in assigning the group to a specific routing rule of the same priority number. The Group Control Name Set is used as a trigger in the Job routing Reason and Control Manager. Fill in only the fields needed to identify the required information.
Example: You may want to group a specific set of progressives with a specific coating. You can do so by creating a Group Style Name Set with several entries using the type code for each applicable progressive. Then, create a Group Lite-up Name Set for the coating and combine the two tables within the Group Control table.
Keys to this hierarchy are:
- Account groupings which will be assigned to a local lab as a default.
- Process groupings which will be assigned to processing centers that can do specific processes such as digital processing.
- Product groupings which combine with the two groupings above.
- Order attribute groupings: For example, Frame to come suggests that the order should be edged at a local lab even though surfacing may be done at a digital lab. Uncut orders could be sent directly to a digital lab.
Example:
- Top level (highest priority) – Management of customer and / or product name sets. A combination of group account name set and product name set (s) = one rule. At this level, we are mainly assigning group names to accounts, products and processes. We do not trigger routing at this level. We’re just associating group names with the order, so we can use these group names in the next levels.
Example: A combination of group account name set and product name set (s) = one rule. This name set is then used as a trigger in the Job Routing Reason and Control Manager.
- Mid level (mid priority) – Management of uncut distribution.
- Low level (lowest priority) – Management of edged jobs or uncut work processed at the local site.
Group Name Sets
Name sets are designed to associate a number of entries into one group or table. These names sets can then be used in combination with other name sets to create a job routing rule.
Example: An account group name set could be created to include accounts specific to a region or processing center.
Name sets can also be created to define groups of product. A product name set can then be combined with an account group name set and/or a group lite up table defined to allow or disallow a specific coating (s). Any group of tables or names sets within the group control menu can be combined to create a routing rule.
Procedure
Custom Configuration for Save Group Names
From the Optifacts main menu:
Type 3 - Editor Utilities and press enter.
Type 6 - Configuration Editor and press enter.
Type 6 – Edit Custom Configuration and press enter.
The Custom Configuration Editor displays.
The following custom configuration must be enabled.
- Press Q to Query to search if the table you are looking for exists and that it is enabled.
- If the table exists but is not enabled:
- Type U to update.
- Change to Enabled field to Y
- Press escape to save the data
- If the table does not exist:
- Type A to add a new record.
- Enter all the information as shown in the diagram below.
- Press Escape to save the data.
- Type E to exit.
Group Control Menu
The tables within this menu are used to setup group tables and name sets which we will use to define job routing rules.
From the Optifacts main menu:
Type 3 - Editor Utilities and press enter.
Type 11 - Job Routing Menu and press enter.
Type 14 - Group Control Menu and press enter to display the Group Control Menu.
Note: Tables 4 through 11 are optional and only those necessary to define the type of job need be created. The Group Control Editor Menu option 2 is used to create a combined group based upon tables created for account, product style, material, color, etc. Menu option 3 – Add New Name Set is used to create the various account and product tables within one screen.
Group Account
- Type 4 and press enter to display the Group Account table.
The Group Account table is used to define an account or group of accounts when a routing rule is designed to be applicable to specific accounts (not all accounts).
The Group Account Table displays.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field.
- Create a name set for the account or a group of accounts. An account number can be used if the rule is applied to only one account.
Examples:
Account Name Set: [ACCOUNT 30]
Account Name Set: [ 30]
Account Name Set: [UNCUT ACCT]
The account can be defined by entering the account number in the Beginning Account Code field and Ending Account Code field. A group of accounts can also be defined by creating multiple entries (one for each account) or a group of accounts can also be defined by Company Code, Branch Code, Territory Code and/or Ship Code.
- Enter all the pertinent information pressing enter past each field.
- Press Escape to save the data.
- Type E to exit.
Group Frame
- Type 5 and press enter to display the Group Frame table.
The Group Frame Table is used to define a specific frame or group of frames.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. Multiple entries can be created under the same Name Set.
- Press Escape to save the data.
- Type E to exit.
Group Rx
Type 6 and press enter to display the Group RX table
The Group RX table is used to define RX specific ranges and/or limitations.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. There are 3 screens available for data entry. Multiple entries can be created under the same Name Set.
- Press enter through the last field to view the next screen.
- Enter any applicable data.
- Press enter through the last field to view the next screen.
- Enter any applicable data.
- Press Escape to save the data.
- Type E to exit.
Group Lite Up
- Type 7 and press enter to display the Group Lite Up table.
The Group Lite-ups Table is used to define a coating, tint, services, etc. or groups of coatings, tints and/or services applicable to the job criteria.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. Multiple entries can be created under the same Name Set.
- Press Escape to save the data.
- Type E to exit.
You can create multiple conditions as shown in the following example:
Group Style
Type 8 and press enter to display the Group Style table.
The Group Style table is used to define a product by style, type, manufacturer, etc. or groups of product under the same name set.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. Multiple entries can be created under the same Name Set.
- Press Escape to save the data.
- Type E to exit.
Group Material
- Type 9 and press enter to display the Group Material table.
The Group Material table is used to define a product by material code or groups of materials.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. Multiple entries can be created under the same Name Set.
- Press Escape to save the data.
- Type E to exit.
Group Color
- Type 10 and press enter to display the Group Color table.
The Group Color table is used to define product by color or groups of colors.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. Multiple entries can be created under the same Name Set.
- Press Escape to save the data.
- Type E to exit.
Group Control
Type 2 and press enter to display the Group Control table.
The Group Control table is used to combine group tables into one Group Name Set which will then be used as a trigger in the Job Routing Reason and Control Manager table to route the job with the combined criteria to a specified site. Two pages allow a combination of 6 tables and/or name sets.
- Type A to add a new record.
- Enter all the pertinent information to define a group of product.
Two pages allow a combination of 6 tables and/or name sets.
- Enter through the last field to view the next screen.
- Press Escape to save the data.
- Type E to exit.
Use of NOT Name Sets
To disregard a name set within a rule, type the word NOT in the NOT name set field.
In the following example: Table Name Set PROG GRP B will be ignored in this rule.
Use of the Parenthesis Around Name Sets
We can use parenthesis around name sets to let the system know to look at either entry.
In the following example: If group style "SV" and group color (TRG or TRB) is used, then the rule applies.
Combined Name Sets
The Group Control table can also be used to create Name Sets which can be combined to create another Control Name Set.
Example: We can create new Name Sets and combine them to create a new Control Name Set used as a trigger in the Job Routing Reason and Control Manager.
- First we create 2 separate Control Name Sets.
Name Set PROG GRP B – Plastic Uncoated Progressive and Name Set SV GRP A – Single Vision Plastic Uncoated
- Then we combine them together to make a new Control Name Set.
New Control Name Set - LENS GRP A combining PROG GRP A and SV GRP A. The table is defined as “name set” rather than the table name. A priority number is used which we will match the to the priority number used in the Job Routing Reason and Control Manager.
Note: Matching priority numbers is not mandatory but makes it a lot easier to identify what groups match to routing rules.
The results states "If the job specifications fall into name set SV GRP A or Prog Grp A, then the job will route using "LENS GRP A" which will be set up as a trigger in the Job Routing Reason and Control Manager.
Combine Name Sets and Group Tables
You can also combine tables with name sets when creating a Control Name Set.
The results states "If the job specifications fall into name set Prog Grp A and grp_rx table PROGRESSIVES then the job will route using "LENS GRP B" which will be set up as a trigger in the Job Routing Reason and Control Manager.
Coat Codes
The Coat Codes table is used to define coatings by Group Name Set and code. This code will print on the work ticket for use in production.
Type 11 – Coat Codes Table and press enter to display the Coat Codes table.
Note: Before setting up a coat codes table, the applicable group tables must first be set up.
Example:
We will setup a group lite-up table with a name set of AR COAT and a group material table with a name set of PLASTIC
Then we will create the Control Name Set (group menu option 2) in the Group Control table to associate the 2 tables into 1 Control Name Set.
Once the Group Name Set has been created then a Coating Code may be added.
- Type 11 and press enter to display the Coating Codes table.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field. Multiple entries can be created under the same Name Set.
- Group Name Set - same as the name set created in the group control table.
- Priority Number
- Position - Enter the character position if using POSITION COAT CODES configuration.
- Coating Code
- Press escape to save the data
- Type E to exit.
The coating code will print on the work ticket.
Optifacts Rx Transfer Menu
Once all of the group tables, name sets and controls have been setup, it is now time to add them to routing rules.
From the Optifacts Main Menu:
Type 3 and press enter to display the Editor Utilities Menu.
Type 11 and press enter to display the (Job Routing) Rx Transfer Menu.
Type 1 to Set Send Interval & Force Transfer. Type the value and press enter.
Type 2 to Re-Start Queued Transmissions.
Type 3 to Check Status of Last Transmission.
Type 4 to review the Log File.
Type 5 to Pause/Resume the Receiving Program.
Type 6 to Set Time Periods to Send/Receive.
Type 7 to Re-send an old transmission.
Route Destination Editor
The Job Routing Destination Control Manager is used to define destination sites. The Route Destination Editor allows the routing lab to set up destinations to other labs that will receive the work. The following are steps to help you set up this page.
From the Optifacts Rx Transfer Menu:
Type 11 - Route Destination Editor and press enter.
The Job Routing Destination Control Manager displays.
- Type A to add a new record.
- Enter all applicable information, pressing enter past each field.
- Destination Site
- Choose the lab to receive the routed job and enter up to a 7-character lab identification name, this name will be provided by the receiving lab.
- Out-Going file Format
- Enter file format: OPTI2.5, OPTI2.8 or other. This information can be obtained from Optifacts Customer Support.
- Transmit Protocol
- U: UUCP, V: VisionWeb, E: External, I:Internal System, F: FTP, C: Local Copy. The protocol allows you to determine how the work is to be transmitted to the receiving lab.
- Destination Directory
- Enter Optifacts home directory at remote site. This is the current working directory of the receiving lab.
- Lab ID Number (if applicable) This is the site ID for the sending lab.
- Outgoing Site ID (if applicable) This is the site ID for the sending lab.
- Destination Agency (if applicable)
- Enter the DestAgency for the ECGXML file.
- Frame Points Required (if applicable)
- Enter 0 for 'no requirement', or enter 128 if 128 points required specifically.
- *** Commercial Code Format
- If destination requires different commercial codes than default, supply format.
- *** Commercial Diameter Format
- Format for commercial code search to use in searching for commercial diameter.
- Destination Site
*** These formats are used instead of the lab’s specified commercial code and commercial diameter formats in the case that the receiving lab uses different codes than the Optifacts lab.
- Press escape to save all entries.
Examples:
Example of an External site.
Example of setup for jobs outgoing through VisionWeb
Examples of Internal sites.
Job Routing Reason and Control Manager
The Job Routing Reason and Control Manager are used to define a condition for a product or product group.
Type 8 - Route Reason and Control Editor and press enter.
The Job Routing Reason and Control Manager screen displays. This table has 3 screens. Press S to view the next screen. When editing an entry, press enter through all the fields to access next screens.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field.
- Help prompts are indicated at the bottom of the screen when the cursor is moved to each field.
- Press Escape to save the data.
- Type E to exit the screen.
1st Screen:
- Priority -
- Program drops highest to lowest to find first set of condition matching job. It is recommended to start with a large number such as 10,000 and increment additional priorities by 100, i.e.; 10,100, 10,200 … doing this will allow you to sneak in additional priorities as they apply to a situation. For example, you decide to route all Crizal jobs so you assign it a priority of 10,000. You also decide to route all glass jobs so you assign it a priority of 10,100. Every thing is working well until you realize you don’t want to route Crizal jobs that need to be tinted. Because you left space you can now assign your new routing requirement for tinted Crizal 10,050. The priority number used can be the same number that was used in the Group Control table for consistency.
- Origination Site ID -
- Site ID of origination site (optional). Leave Empty to work from any site.
- Condition ID -
- Condition Name to match conditions for job attributes to set during transfer. This name must match the ‘Condition Name’ given in the ‘Route Conditions Control Editor’ page for mapping purposes. The condition ID is free format text and does not have to match the Group Trigger name but must match the entry in the condition ID table menu 3-11-9.
- Destination Site ID -
- Site ID of destination site (optional). May be specified in Route Conditions. This name will be provided by the receiving lab.
- Group Trigger 1 - Enter
- Enter a Group Name to cause routing for the Group. Precede with '!' for 'NOT'.
- Group Trigger 2 - Enter
- Enter a Group Name to cause routing for the Group. Precede with '!' for 'NOT'. It is not always required to have entries in both fields 1 and 2.
- Group Name Set - Ties
- Ties a Group Name to a condition, so won't route. Use Group triggers to route.
- Comments -
- Enter your own comments for future reference. For example; “All glass jobs will be routed to lab XYZ”.
- Lite-Up (num) - ) (NOT the number viewed on screen)
- See the Pricing Options Available Report in Retail Transfer (menu 11-14) to find the num of a lite-up.
- Lite-Up (bit) - See the Pricing Options Available Report in Retail Transfer.Lite-Ups - (NOT the number viewed on screen):
- See the Pricing Options Available Report in Retail Transfer
- (menu 11-14)
- to find the bit of a lite-up.
- Lite-Up (num) (NOT the number viewed on screen)
- See the Pricing Options Available Report in Retail Transfer (menu 11-14) to find the num of a lite-up.
- Lite-Up (bit) (NOT the number viewed on screen):
- See the Pricing Options Available Report in Retail Transfer
- (menu 11-14) to find the bit of a lite-up.
- Fld Name frm Job Def. -
- Field Name from Job Data Definitions Editor in Configuration Menu.
- Fld Value for Fld Name -
- Field Value Entered as a result of Job Data Name.
- Uncut
- Enter U/E: U if transfer should occur when job is entered as uncut.
- Finished Only -
- Enter F/S: F to transfer if job is Finished Lens on Both Eyes, S for Semi-Fin.
- Industrial -:
- Enter I/D: I to transfer when job is industrial thickness, D for Dress Thick.
- Company Code - Optional.
- Branch Code - Optional.
- Territory Code - Optional.
- Account Number - Optional.
- Ship-To Code - Optional.
2nd Screen:
- Lens Manufacturer -
- Enter lens manufacture code. I.e.; Y for Younger, HO for Hoya or KB for KBCO.
- Lens Style -
- Example 7X, P, SV, SVST. Note: Don't include seg size
- Seg Size -
- Inclusive lowest seg size to trigger
- Through -
- Inclusive Highest seg size to trigger
- Lens Type -
- Progressive or Aspheric Lens Type or Design. Example VC for Varilux Comfort or CL for Cosmolite.
- Color Code -
- May be left blank or a color code added such as BP3 for polarized brown 3.
- Material Code -
- May be lift blank of a material code added such as TVX for Trivex.
- Pair Only -
- Y to only transfer if job is a pair as opposed to R for right or L for left eye only.
- Exclude Power Increment -
- Exclude if power increment sphere or cylinder (0.125 is only exclusion allowed).
- Highest Minus Power -
- Exclude if combined minus power of sphere & cyl is more minus than this value.
- Highest Plus Power -
- Exclude if highest plus power without lower add is than this value.
- Highest Plus with Add -
- Exclude if highest plus power including lower add is than this value.
- Lower Add Range -
- Enter range values if applicable. Example: 0.00 through 4.00
- Upper Add Range -
- Enter range values if applicable. Example: 0.00 through 4.00
- True Base Range -
- Enter range values if applicable. Example: 1.12 through 8.49
- Blank Diameter Range -
- If the rule you are creating is to be a manual routing rule, set the range from 98 through 99. This will stop this rule from being included in auto routing. If it is to be part of auto routing, then leave this blank.
- Minimum Blank Range - Enter
- Enter range values if applicable
- Sphere Power Range -
- Enter range values if applicable. Example -12.00 through 10.00
- Cylinder Power Range -
- Enter range values if applicable. Example: -4.00 through 4.00
- Resolved Prism Range -
- Enter range values if applicable.
3rd Screen:
- Center Thickness Minus -
- Enter range values if applicable.
- Edge Thickness Minus -
- Enter range values if applicable.
- Center Thickness Plano -
- Enter range values if applicable.
- Edge Thickness Plano -
- Enter range values if applicable.
- Center Thickness Plus -
- Enter range values if applicable.:
- Edge Thickness Plus -
- Enter range values if applicable.
- Day of the Week -
- Enter 0 for Sunday, 1 Monday . . . 6 Saturday.
- Time of Day:
- 24 Hour time: 100 = 1:00AM, 2330 = 11:30PM.
- Beginning Date: Date Range - Enter
- Enter range values if applicable.
Note: All the fields do not have to be filled out. It just depends on how refined you want to make your routing rule. The more information that is added will narrow your routing parameters.
Rules without using group triggers or name sets.
The Job Routing Reason and Control Manager can also be set up without using group tables and triggers. There are multiple screens available for data entry.
A Group Trigger is not used but job specifics are specified as shown below.
The following fields have been entered to define the rule:
- Condition ID
- Comment
- Lite-up num and Lite-up bit (to define the applicable coating)
- Uncut flag
- Semi-finished flag
- Lens Style code
- Lens Type code
- Color code
- Material code
- Lower add range
Route Conditions Control Editor
Type 9 and press enter to display the Job Routing Condition Control ManagerThe Route Conditions Control Editor allows the routing lab to set all the condition conditions as to when and why a job should be routed to a different lab.
Condition ID:Type 9 - Route Conditions Control Editor and press enter.
The Job routing condition Control Manager screen displays.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field.
- Help prompts are indicated at the bottom of the screen when the cursor is moved to each field.
- Condition ID
- Enter a Condition ID that will map this set of conditions to the Routing Editor. This can be as simple as “Glass Job” or “Crizal Job”. This name must match the ‘Condition Name’ given in the ‘Route Reason and Control Editor”
- menu 3-11-8 for mapping purposes.
- Destination Site
- Destination site to which condition applies. (Routing Editor may override entry.) Choose the lab to receive the routed job and enter up to a 7-character lab identification name, this name will be provided by the receiving lab.
- The destination site must exist in the Route Destination table (menu 3-11-11).
- Send As Uncut
- Enter Y to force job to become Uncut en-route to destination. Leaving this entry blank may tell the receiving lab to edge the lens as well.
- Clear Lens Diameter
- Enter ‘Y’ to clear blank diameter en-route to allow blank selection at destination.
- Clear Lens Nominal Base
- Enter ‘Y’ to clear nominal base en-route to allow blank selection at destination.
- Bill-To-Account
- Billing Account Number to be applied at destination site. The receiving lab will enter the account number they have for either the sending lab or the doctor’s office that ordered the job.
- Bill-To Ship Code
- Ship-to Code that matches the Billing Account Number at destination site.
- Ship-To-Account
- Ship-To Account Number to be applied at destination site. The receiving lab will enter the ship-to number they have for the “Bill-To-Account”
- Ship-To-Ship Code
- Ship-to code that matches the Ship-To Account Number at destination site.
- Clear VSP Flag
- Enter ‘Y’ to clear the VSP Billing designation, so it doesn't apply at the destination.
- Clear Second Billing Flag
- Enter ‘Y’ to clear the split bill or co-pay designation en-route.
- Clear Safety Billing Flag
- Enter ‘Y’ to clear the safety billing en-route so it doesn't apply at the destination
- Press Escape to save the data.
- Type E to exit the screen.
Note: Clear all lite-ups
en-route, but lite-up editor entries may turn some back on. Leave blank for branch-to-branch transfers- Y clears all lite-ups en-route but lite-up editor entries may turn some back on
Route Conditions Lite-up Editor
Type 10 - Route Conditions Lite-up Editor and press enter.
The Job Routing Lite-Up Control Manager displays.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field.
- The condition ID must match the entry in the Route Manager table menu 3-11-8
- The destination site must exist in the Route Destination table.
- The Bill To Account number would be the sending site’s account number with the receiver.
- Help prompts are indicated at the bottom of the screen when the curser is moved to each field.
JOB ROUTING CONDITION CONTROL MANAGER
Condition ID: [PROG GRP A ]
Destination Site: [optifac]
Force Uncut/Drop Ship/Third Party Ship/Potential Drop Ship/None: [Y]
Dispatch Job (D/T/N): [N]
Clear Lens Diameter: [Y]
Clear Lens Nominal Base: [Y]
Bill-To-Account: [ 12345] Ship-To-Account: [ 12345]
Bill-To Ship Code: [ ] Ship-To-Ship Code: [ ]
Clear VSP Flag: [Y]
Clear Second Billing Flag: [Y]
Clear Safety Billing Flag: [Y]
Clear All Lite-Ups: [N]
Y clears all lite-ups en-route but lite-up editor entries may turn some back on
- Press Escape to save the data.
- Type E to exit.
- Type 10 and press enter to display the Job Routing Lite-Up Control Manager
- Condition ID: Condition Name to match conditions for job attributes to set during transfer. This name must match the ‘Condition Name’ given in the ‘Route Conditions Control Editor’ page for mapping purposes.
- First Number (num): See the Pricing Options Available Report in Retail Transfer.
- Second Number (bit): See the Pricing Options Available Report in Retail Transfer.
- On Off or Ignore: ‘O’ will turn this option On en-route, ‘F’ will turn Off this option en-route, ‘I’ will Ignore this option all together. Use ‘S’ to turn this option on for the local job and ‘U’ to turn this off for the local job.
- Based on Condition ID this table is used to define lite-ups that can be turned on or off during routing.
- Type A to add a new record.
- Enter all the pertinent information pressing enter past each field.
Searches the active database table. ** 1: rte_lite_ups table**
JOB ROUTING LITE-UP CONTROL MANAGER
Condition ID: [FRAME TO COME CONDIT]
First Number (num): [4 ] (Lite-ups: NOT the number viewed on screen)
Second Number (bit): [15 ] (Lite-ups: NOT the number viewed on screen)
Pricing Text : FRAME TO COME
On Off or Ignore: [I] O to turn on en-route
F to turn off en-route
I to ignore.
S to turn on for the local job
U to turn off for the local job
This Editor supercedes the clear-all-lite-up option of the
Route Condition Editor. Thus, the clear-all-lite-up
option will clear all lite-ups except the ones specified
1 row(s) found
- Help prompts are indicated at the bottom of the screen when the cursor is moved to each field.
- Condition ID
- Condition Name to match conditions for job attributes to set during transfer. This name must match the ‘Condition Name’ given in the ‘Route Conditions Control Editor’ page for mapping purposes.
- First Number (num)
- See the Pricing Options Available Report in Retail Transfer.
- Second Number (bit)
- See the Pricing Options Available Report in Retail Transfer.
- On Off or Ignore
- ‘O’ will turn this option On en-route
- "F’ will turn Off this option en-route
- ‘I’ will Ignore this option all together.
- Use ‘S’ to turn this option on for the local job
- ‘U’ to turn this off for the local job.
- Press Escape to save the data.
- Type E to exit the screen.
Multi-Site Destination Editor
Multi-site destination editor is used when a job must be routed to multiple locations for processing. We provide examples of one sequence of events below.
Menu option 15 from the Optifacts Rx Transfer menu
Type A to add a new record
Enter all the applicable data pressing enter past each field.
Multiple-Condition ID
Order Sequence – the order in which the routing is to occur
Condition ID as set in the rte_mgr and rte_cndtn tables
Comments are used to describe the condition
Example: The job needs to be sent to one location for surfacing, another for tinting and finally another for edging.
