More information on using server assigned card numbers
The server AssignNo table holds unique up to nineteen digit card numbers to be used in programs such as In-House Cards. You can obtain unique card numbers from Siriusware Technical Support for a minimal fee per number or if you own a BIN number you can populate the AssignNo table with your own unique card numbers. Whether you own your own BIN or purchase numbers from Siriusware Inc., you must call Siriusware Technical Support in order to populate the AssignNo table with card numbers.
When populating this table, you must assign a num_source for the card numbers. You may have reasons to allocate certain ranges of card numbers to different num_sources in the AssignNo table based on multiple card number programs at your site. But generally, unless you have multiple programs, using the default num_source of 0 is adequate.
Your salespoints are configured to store a local supply of card numbers from the server AssignNo table for use in off-line situations. This is done with the following .INI setting (this may be entered in the appropriate group section within the global .INI from SysManager, as described previously.)
AssignNoQty=(0,25;1,10;2,15)
This setting above would prompt the salespoint to always locally store twenty-five numbers from num_source 0, ten numbers from num_source 1 and fifteen numbers from num_source 2.
If you only use the default num_source of 0, your setting would look something like this:
AssignNoQty=(0,25)
The amount of numbers stored locally is enough to get by when running in stand-alone mode. Un-used numbers cannot be sent back to the server for redistribution, so do not store so many numbers locally that you drain your server AssignNo table. For instance, food and beverage stations would never issue In-House Cards items, so those POS do not store any local card numbers.
To load card numbers into the
AssignNo table, use the
SysManager >
Utilities >
Import Card Numbers utility, as described in
How to import card numbers.
assign_no warning thresholds can be implemented from SysManager > Preferences > AssignNo Warning Thresholds. When the number of available assign_no values drops below a threshold (default=100), a warning appears each time you start SysManager. You can view, manage thresholds and disable or enable the warnings for each assign_no bucket using the SysManager > Preferences > AssignNo Warning Thresholds dialog.
To determine how many unassigned (available) card numbers you have remaining, you can use the following SQL script:
Use SiriusSQL
SELECT ckd_out_to, COUNT(*) AS Total
FROM assignno
WHERE (ckd_out_to = '-1')
GROUP BY ckd_out_to
/*Here is what the output looks like
Ckd_out_to Total
-1 243 */