There is a setting in Kalahari which decides if the level is reduced when the calculation is made or when the stock has been confirmed as picked.
This has now been implemented for finished lenses also. This is under the inventory settings.
So if there are 5 items in stock. When the order is entered, there will still be 5 items in stock. When the item is taken off the shelf and the barcode is scanned then the level is reduced. If the barcode is not known then the software will remember the barcode for that prescription.
Thursday, 20 November 2014
Saturday, 15 November 2014
Kalahari - Ovalling
It is now possible to turn off the ovalling feature. The software will then revert back to the trepan diameter.
Wednesday, 12 November 2014
Rx Purchasing - Confirm before sending and Local Mapping.
The purchasing module has been updated so that it is possible to send only certain orders by selecting beforehand. If this is not turned on then the program works as now, that is to send all the orders.
If the web service is used then it is possible to apply a local mapping to convert the codes before sending.
There is a tick box to indicate this and clicking on the link will bring up a text file. The entries in the text file are in the form
Annapurna code=Supplier Code
For example
A123=567890
This will send code 567890 to the supplier for codes A123.
You can also use
A123=567890+MC
to convert the one code into a lens and coating code.
If the web service is used then it is possible to apply a local mapping to convert the codes before sending.
There is a tick box to indicate this and clicking on the link will bring up a text file. The entries in the text file are in the form
Annapurna code=Supplier Code
For example
A123=567890
This will send code 567890 to the supplier for codes A123.
You can also use
A123=567890+MC
to convert the one code into a lens and coating code.
Thursday, 6 November 2014
Currencies revisited
An addition to the earlier post.
Annapurna does not explicitly support currencies. It simply raises an invoice for a value and that value is interpreted to be appropriate currency for the customer by the financial system.
Annapurna does stop prices from being applied with the wrong currency so a dollar price list is not used for a Euro customer.
If multiple currencies are used then the local currency is assumed to be the default currency and only records that are not the default currency are changed.
Firstly in the customer record, you set the currency code to a field eg USD for dollar or EUR for Euro. The code does not matter but it helps to use a recognised code.
When you create a pricelist, there is a field for currency. Put the currency code in this field.
Annapurna will now check to see that the pricelist being considered is the same currency as the customer.
Packages also have a field for currency code so that a package in one currency is not applied to a different customer.
Wednesday, 5 November 2014
Tuesday, 4 November 2014
Browser - search by current status
There is a new feature in Browser to filter orders by status code. The default is for any status code but if the status message under the job and tray number fields is clicked then a pop-up will appear.
This will ask for the status code that you wish to use for filtering the search.
This will ask for the status code that you wish to use for filtering the search.
Subscribe to:
Posts (Atom)