| Anchor | ||||
|---|---|---|---|---|
|
Search Optifacts User Documentation
| Live Search | ||||
|---|---|---|---|---|
|
Table of Contents (on this page)
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Introduction
This document provides explanations for the various failure messages that could appear on the work ticket.
Procedure
The following listings outline the possible error messages and defines what they mean.
Blank Selection
NO SPHERE RANGE FOUND FOR THIS ITEM
SUGGEST EXPANDING EFFECTIVE SPHERE
RANGES IN THE BASE CURVE TABLE
This message appears if you have gaps or no entry in the Base Curve Table, then you will get the above message. You need to either add an entry for the entered lens material, or ensure you do not have gaps under the Effective Sphere Range Heading. If the lens is a full field, it will also print the following message:
FULL FIELDS MUST HAVE ENTRIES FOR THE
CORRECT LENS TYPE (NOT N/A)
This message is related to the one above.
If the entered lens is a Full-Field lens, you must have an entry for the specific lens material and lens type code. Even if you have an entry for PC material and NA or SV lens type, you still need a separate entry for PC material and a lens type code. (E.g. GP)
MULTI SPHERE RANGES FOUND FOR THIS ITEM
CORRECT OVERLAPPING EFFECTIVE SPHERE
RANGES IN THE BASE CURVE TABLE
This is the opposite of the “NO SPHERE RANGE FOUND” message. If there are any overlapping entries in the base curve table under the Effective Sphere Range heading, you will most likely see this message. The Base Curve Table Editor does have safety precautions against saving overlapping entries, but the calculation module will still check for this.
NO SUPPLIER LISTED FOR THIS LINE ITEM
SUGGEST ADDING ENTRIES TO THE
BLANK SUPPLIER PRIORITY LIST
This message appears if there is no entry in the Supplier Priority List for the lens style, material, type and/or power entered. Double-check the Supplier Priority Editor for an entry for this line item, expand the Supplier List and activate it to update changes. In addition, you may need to check the Base Curve Table for entries that may be forcing certain prescriptions to select specific base curves. If those base curves are not available in the Supplier Priority List, you will also get this message and will need to either add bases to the Priority List or expand the base rand in the Base Curve Table.
SUGGEST ADDING EXTRA THICK ENTRIES TO
THE BLANK SUPPLIER PRIORITY LIST
REQUIRED BLANK THICKNESS:
THIS LINE ITEM WAS NOT FOUND IN THE
LENS DATA BASE, SUGGEST MAKING AN
ENTRY INTO THE LENS DATA BASE
If Blank Selection finds an entry in the Supplier List, but the lens does not exist in the Lens Database, you will see the above error. You need to enter the line item into the Lens Database before Blank Selection can use the lens. Make sure all items in the Supplier List exit in the Lens Database by running the “Check for Differences” routine on the Blank Selection Menu. If the job requires an extra thick blank the error will also print additional information showing center thickness, recommends myodisc at frame edge, thickness required at frame edge, and the amount too thin at the frame edge this lens would be. If the Rx requires and extra thick lens and the line item does not exist you will see the following message:
THIS LINE ITEM WAS NOT FOUND IN THE
LENS DATA BASE, SUGGEST MAKING AN EXTRA THICK
ENTRY INTO THE LENS DATA BASE
NO STOCK LENS IN THE LENS DB WAS
THE CORRECT THICKNESS TO EDGE OUT
SUGGEST ENTERING ADDITION LENSES
REQUIRED BLANK THICKNESSES: ##
If the job tries all the priority picks and is unable to cut out using any of the picks in Finished Lens Stock you will see the above message along with the lens thickness needed. If possible, you may want the system to select semi-finished lenses in situations such as this. If the Layout operator is entering SVST as the lens style, you are forcing Optifacts to only consider finished lens choices. You may want to consider entering the style code of SV and configuring Optifacts to try finishes lenses first, and then choose from semi-finished if there are no suitable finished lens choices available. The above error will also print additional information showing center thickness, recommends myodisc at frame edge, thickness required at frame edge, and the amount too think at the frame edge this lens would be. If the lens pick was from Semi-finished the following message will print:
NO BLANK IN THE SUPPLIER LIST WAS
THICK ENOUGH TO EDGE OUT, SUGGEST
ENTERING A THICKER BLANK
REQUIRED BLANK THICKNESS: ##
NO BLANK IN THE SUPPLIER LIST WAS
LARGE ENOUGH TO CUT OUT, SUGGEST
ENTERING A LARGER DIAMETER BLANK
REQUIRED BLANK DIAMETER:
You will see the above message if Blank Selection was unable to find a lens large enough to cut out, based upon the Rx information given. The system will print the minimum blank size needed to cut out. You need to enter larger diameters into the Supplier Priority List.
NO BLANK IN THE SUPPLIER LIST HAD
SUFFICIENT QUANTITIES IN INVENTORY
NO INVENTORY AVAILABLE FOR JOB
You have the Inventory package, and you have the Inventory package configured to select lenses based on availability. Your Inventory database shows zero quantity for all the possible stocked lens selections for this particular job. Either you are out of lenses, or your quantity on hand in the Inventory program is not correct. Correct the problem and run this job again. This is triggered by the setting “Check Quantity on Hand and Costs?” in Inventory Configuration.
NO BLANK IN THE SUPPLIER LIST
WOULD WORK
If Blank Selection encounters an error that does not correspond to any of the above messages, this message will print. You should normally never see this message print. Please call Optifacts Support with the Rx job # if you ever see this message on a pick ticket or work ticket.
LENS HAS ZERO QUANTITY
ON HAND
The inventory package is configured to select lenses based on best fit. Your inventory database shows zero quantity for the proper stocked lens selection on this particular job. This is triggered by the “Check Quantity on Hand and Costs?” (set to N) in Inventory Configuration. When using the default parameters, this message should not appear.
Coat Switch
*** COAT SWITCHED (stock or semi-finished) COLOR TO (color now), ORIG WAS: (orig. color) ***
This message indicates that the color/coating entered at entry has been switched automatically to this color/coating
Cut Out, Thickness and PD
NO BLANK IN THE SUPPLIER LIST WAS
LARGE ENOUGH TO CUT OUT, SUGGEST
ENTERING A LARGER DIAMETER BLANK
REQUIRED BLANK DIAMETER: ##
Blank selection was unable to find a lens large enough to cut out, based upon the Rx information given. The system will print the minimum blank size needed to cut out. Remove the restrictions (adjust the Rx) and try again.
WARNING: BLANK TOO THIN AT MRP
This may occur if the entry operator has picked and specified lenses at entry. Blank selection will notify that no lens in the supplier list would work. Remove the forced entry and re-process the job allowing blank selection to pick the best possible lens for the Rx.
WARNING: BLANK TO THIN TO GEN. AT MRP
This may occur if the entry operator has picked and specified lenses at entry. Blank selection will notify that no lens in the supplier list would work. Remove the forced entry and re-process the job allowing blank selection to pick the best possible lens for the Rx.
EDGE TOO THIN BY: xx.x
This is a secondary message seen on blank selection failures. Provides additional information is assisting the lab to correct or change the selected products.
EDGE TOO THICK BY: xx.x
This is a secondary message seen on blank selection failures. Provides additional information is assisting the lab to correct or change the selected products.
CENTER TOO THICK BY: xx.xx
This is a secondary message seen on blank selection failures. Provides additional information is assisting the lab to correct or change the selected products.
Lens Type
DUPLICATE LENS TYPE INFO IN DATABASE
This message indicates some duplication within the database. Corrections must be made to remove the duplicate entries.
LENS TYPE INFO NOT LOADED IN DATABASE
This message indicates that the lens has a limited base curve range. An expansion of the base curve range may be necessary.
Pricing
NO PRICE LIST (PRICE LIST #), WILL NOT PRICE
Price list/group assigned to account and price list/group is not in the database.
NO BASE PRICE LIST (price list #) WILL NOT PRICE (which lens)
- Generally occurs when a lite-up is used that misdirects to another price list.
NON-PRICEABLE LENS TYPE, WILL NOT PRICE
- Price list/group assigned to account and price list/group is not in the database.
INVOICE TOO HIGH. WILL NOT POST (price list #), (price list code)
TYPE: xx, xxxxxxxxxxxx
- The price list/group has an entry with a value of 999.99 in the price list/group. There may be multiple items set to this value.
MINUS INVOICE AMOUNT, WILL NOT POST (price list #), (price list code)
- Only credit jobs are allowed to have a negative total. If a collective group of discounts exceed zero dollars, then a correction must be made to the price tables.
INVOICE LESS THAN FRAME + POSTAGE
- Similar to Minus Invoice Amount.
BASE PL CODE CHANGED VIA LITE-UP TO ##
WILL NOT POST, PRICE TOO HIGH ($$$.$$), PL ##, PIRCE, PRICE CODE
- This occurs when a lite-up redirect pricing to the wrong price list.
NO BLANK IN THE SUPPLIER LIST
WOULD WORK
- If Blank Selection encounters an error that does not correspond to any of the above messages, this message will print. You should normally never see this message print. Please call Optifacts Support with the Rx job # if you ever see this message on a pick ticket or work ticket.
NO COST LIST ##, WILL NOT PRICE
ERROR ## FINDING COST LIST ##, WILL NOT PRICE
- This occurs when there is no cost for products.
NO SPHERE/COMPOUND PRICES. WILL NOT POST (price list #)
- This occurs when items are missing from a price list.
CAN’T GET TAX INFO, WILL NOT PRICE
- This occurs when tax information is missing from a price list.
CAN’T GET SECOND TAX INFO, WILL NOT PRICE
- This occurs when tax information is missing from a price list.
ERROR – 242 GETTING PRICE
- This error (242) says the system could not open the table. Possible causes are: 1) permissions insufficient, 2) a hardware error, or 3) a corrupt system catalog.
CAN’T GET SHIP TO INFORMATION
- This occurs when no appropriate shipping information can be located.
SUPPLY FRAME LITE-UP AND FRAME GROUP LITE-UP
CANNOT BE ON SIMULTANEOUSLY
- This occurs when there is a bad combination of lite-up uses.
FRAME NOT FOUND IN FRAME GROUP NUMBER ##, (frame group #)
- This occurs when there is missing frame group number from frame group for this job.
NO REVERT PRICE LIST ##, WILL NOT PRICE
- This occurs when the uncut price list will not allow reverting to edged price list.
ERROR ## FINDING REVERT PRICE LIST ##, WILL NOT PRICE
- This occurs when there is a problem finding the edged price list for uncut price list.
TOO MANY REVERTS, WILL NOT PRICE
ERROR ## GETTING POPTS (##,##) DATA
WILL NOT POST (PL#)
- This occurs when there is too many steps to convert to edged.
TOO MANY COPAY DEDUCTIONS
- This occurs when there are too many deductions found in the price list.
NO INVOICE ITEMIZATION CATAGORIES
- This occurs when there is no itemization category set up in the price list for the applicable item.
NO COST LIST ##, WILL NOT PRICE (price code)
- This occurs when a cost for the product cannot be located in the cost database.
ERROR ## FINDING COST LIST #, WILL NOT PRICE
- This occurs when there is s system error finding the cost list.
ERROR ## FINDING PRICE LIST #, WILL NOT PRICE
- This occurs when there is s system error finding the price list.
ERROR ## GETTING COST LIST
- This occurs when there is s system error getting the cost list.
ERROR ## GETTING PRICE LIST
- This occurs when there is s system error finding the price list.
IINFORMIX ERROR ## READING ROW_MASTER TABLE
FOR ROW ##, WILL NOT PRICE
- This occurs when there is s system error finding the row in the price tables.
IINFORMIX ERROR ## READING COL_MST TABLE
FOR COL ##, WILL NOT PRICE
- This occurs when there is s system error finding the column in the price tables.
INFX ERROR ## READING OVRIDE PRC_LISTS TABLE
FOR ROW ##, PL ##, WILL NOT PRICE
- This occurs when there is s system error finding the override price list in the price tables.
INFX ERROR ## READING BASE PRIC_LISTS TABLE
FOR ROW ##, PL##, WILL NOT PRICE
- This occurs when there is s system error finding the base price list in the price tables.
INFX ERROR ## READING ADD-ON PRC_LISTS TABLE
FOR ROW ##, PL ##, WILL NOT PRICE
- This occurs when there is s system error finding the add-on price list in the price tables.
INFX ERROR ## READING BASE PRC_LISTS # TABLE
FOR ROW ##, WILL NOT PRICE, ##
- This occurs when there is s system error finding the base price list ## in the price tables.
INFX ERROR ## READING OVRD PRC_LISTS # TABLE
FOR ROW ##, WILL NOT PRICE, ##
- This occurs when there is s system error finding the override price list ## in the price tables.
INFX ERROR ## READING ADD-ON PRC_LISTS # TABLE
FOR ROW ##, WILL NOT PRICE, ##
- This occurs when there is s system error finding the add-on price list ## in the price tables.
CANNOT FIND RECORD IN ROW_MASTER TABLE
FOR ROW ##, COLOR ##, WILL NOT PRICE
CANNOT FIND RECORD IN ROW_MASTER TABLE
FOR ROW ##, COLOR ##, WILL NOT PRICE
CANNOT FIND RECORD IN COL_MST TABLE
FOR ROW ##, COLOR ##, WILL NOT PRICE
CANNOT FIND RECORD IN ROW_MASTER TABLE
FOR ROW ##, COLOR ##, WILL NOT PRICE
INFX ERROR ## READING ROW_MASTER TABLE
FOR ROW_MASTER ##
ERROR ## GETTING POPTS (##,##) DATA
FROM ROW_MASTER, WILL NOT PRICE
- The above message could occur when there is s system error in the price tables.
Routing
WANT TO ROUTE BASED ON PRIORITY ######, BUT
SITE: XXXXXX ISN’T IN THE ROUTE DEST EDITOR
- The lab XXXXXX is not defined although there is a routing table configuration for this job type. The job was not routed.
Example of correct routing on work ticket:
ROUTING CONDITION: XXXXXX, PRIORITY ######
- Where XXXXXX is the condition name and ###### is the priority level number.
A successful job also prints:
RX TRANSFER JOBS: Will be transmitted to XXXXXX
- The message will print in the center of the work ticket.
Shop Floor
SUGGEST CUTTING LAP FOR BOTH EYES
- On occasion Optifacts will print this message on the work ticket. The assumption is the required rear curves fall outside of normal parameters and a lap, or laps, need to be acquired. The action of this assumption is at the lab’s discretion.
*** CHECK BLOCK CRASH (which) EYE(s) ***
- This message indicates the lens at proper thickness will cut into the block. A generator data file will still be created. However, most generators will provide a similar message in the event that this message is missed. Older style generators will not provide the warning.
- When this message appears the generator operator will need to increase center thickness to a level that is acceptable to the generator or alternative blocking methods need to be accessed. If this is the smallest possible block choice, then the finer operator will need to reduce the center on the finer as best they can.
*** VERTICAL IMBALANCE OF #.## D PSM ***
*** SUGGEST RE-RUNNING WITH SLAB OFF ***
- The system will print this message anytime the imbalance exceeds 1.50 diopters.
- Ignore this warning in most cases. It prints as a reference to indicate a need. In some cases, customer service may want to verify with the account.