| ScanMaster | ScanMaster Release Table |
| |
Link to Update: | CD-ROM |
| |
Link to Demonstration Files: | FTP Site for 2.2.0 Demo Files |
| Posting Date: | 30-Jun-05 | |
|
See the table below for a description of the new features provided and faults addressed in this release. |
||
|
Fault Number |
Enhancement or Fault Description |
| New Feature | This release of ScanMaster will require software keys (hasp plugs) attached to the ScanMaster server for the support and control of software functionality. The CryptKey process has been replaced by this new program in this release. |
| New Feature |
VISA Compliancy The Problem: Pin Block needs to be masked in the settlement file, log file, and the authorization file. All 16 characters must be masked. Option to Mask Account # on Store Signature Slip should be reserved. The options is "Mask Acct Num on Str Sig Slip". According to the Visa Compliancy, the account number cannot be displayed on any receipt. Also the option of "Disable Exp Dates on Sig Slips" should also be reserved WG2.EXE |
|
New Feature WD 6346 |
Add PocketOffice support Phase 1 � Q-Buster & RMA not included in this release. |
|
New Feature WD 6338 |
Add support for American Greetings Interface |
|
New Feature WD 6345 |
Add support for Super Valu Audit pre-audit function |
|
New Feature WD 6342 |
Add Support for Penn Traffic Host |
| New Feature | Add support for SIL Processor option for stop on critical error & pop up message box for the error. |
|
New Feature WD 6336 |
Add support for Secondary Universal payments |
| New Feature | ESL - system will now work with shelf label interface - this release does not include support for Unit of Measure conversion. |
|
New Feature WD 6374 |
Installs Add Warning Message when upgrading ScanMaster to Upgrade Registers First |
|
New Feature WD 6373 |
SM2RCTRL.EXE Add Register Control File Option 'Beep Scanner On Error' for Fujitsu OPOS "Beep Scanner On Error 701583" has been added to control.tmp. The option needs placed under the Device tab in the register control file editor. Goes with WD#6292 for WG2.EXE |
|
New Feature WD 6362 |
WG2.EXE Invalid Coupon error message does not beep the Scanner. The error message displays on the POS display, but the cashier does not get an error beep indication from the scanner. |
|
New Feature
WD 6363 |
WG2.EXE Scale error message does not beep the Scanner. The error message displays on the POS display, but the cashier does not get an error beep indication from the scanner. |
|
WD 5814 TAR#XAZBAL5ET |
SM2ITEM.EXE In price mode, the cursor does not automatically go to the Unit Price field. In batch maintenance - with price mode turned on if you entered a the upc the cursor would be put down to unit price. |
| WD 5919 |
SM2ITEM.EXE On Random Weight UPC numbers the system will not allow any change in Item Type - such as Unit, Store coupon or MFG Coupon. |
|
WD 6039 TAR# RAZBK8KJ4 |
SM2PDIMR.EXE Unit cost incorrect in PLU item reportIf - an item has a unit cost defined, the plu item report displays it incorrectly. The decimal position for unit cost appears to be shifted 1 place to the left. |
|
WD 6042 TAR# RAZBHLXJ9 |
SM2SILPR.EXEIf split quantity price, quantity will show, but not price; showing 0 price. Displaying 0 in batches. |
|
WD 6049 TAR# 239164 |
SM2PDIMR.EXE Customer selects a Speed Index of "Report Code" in the PLU Movement Screen and saves his criteria to a Configuration File. When that saved Configuration File is Loaded, the Speed Index has changed. It may become either "UPC Code" or "Department". If the same saved configuration file is loaded again and again, the Speed Index will keep changing to either "UPC Code" or "Department". |
|
WD 6058 TAR# 245027 |
SM2ITEM.EXE Double clicking on Save after changing from unit to split gives wrong results In Direct Item maintenance bring up an item. Then change the item type from a UNIT to SPLIT. Then enter a SplitQty/Price and click on SAVE twice. (double click) When SAVE is clicked twice, the pricing fields are all zeroed out and it goes back to a UNIT type item. It only seems to happen, however, when switching from UNIT to SPLIT. When switching any other way and double-clicking the SAVE, it does not happen. Also got it to happen by pressing Alt-S-S very quickly. |
| WD 6211 |
SM2ITEM.EXE When in Direct Item Maintenance, if I put in a value for Limited Quantity, say the number '3', then put in a price for "LMT.QTY/PRICE", hit tab or ENTER, the Limited Quantity changes to the value of zero instead of the '3' that I added. This was found to have been fixed in 2.01.00, but broken again. |
| WD 6212 |
SM2ITEM.EXEIn CREATE/EDIT Batch, Under the Header Date tab, I would enter a START DATE for the batch, hit ENTER or Tab and it highlights UPC. It should go to the Header End Date. Also, when tabbing through this same tab, it will highlight - Batch Type, Batch Description, Batch Action, but not HEADER START DATE. |
| WD 6213 |
SM2ITEM.EXE Enhanced Price Management - UPCS that are being queried but not SAVED to the batch are created any way once BATCHLIST is entered. |
|
WD 6229 TAR# RAZBLQ56N |
SM2ITEM.EXE When item modified by batch - message field appears in item record "This item modified by Lnnnnn". Message appears at bottom of item record in Direct Item Maintenance between the Delete and Lock Tab buttons. Even though the batch is deleted or the item is manually modified- the message remains forever. If the item is updated through Direct Item - this message should go away.
|
| WD 6285 |
SM2ITEM.EXE When creating a Batch the customer enters the first Item number in the batch, then clicks on Ad Level 1 and ON ADD will display in RED next to the Ad Level. They enter the sale price and save it and the Base Item Price doesn't change, which is correct. Then they enter the next item number they want to add to the batch and the ON ADD flag is still there in red. It should stay on for all items that are added to the batch. But if they enter a NOT FOUND Item Number and it displays, Do you wish to add this item to the batch? and they click on NO. And then they enter the next item number they want to add to the batch, the ON ADD flag is now gone. So each price there after that is entered changes the Base Item Price as well. |
| WD 6292 |
WG2.EXE The use of Fujitsu OPOS Scanner Object with the Fujitsu Scanners (9900 and 9950) requires a new method of sending a beep command to the scanners. The POS will need to pass a new command sequence using the direct I/O method though the Fujitsu Scanner OPOS Object. The Fujitsu OPOS Service Object will need modified by Fujitsu to facilitate the POS sending of the beep command. |
| WD 6294 |
SM2PDIMR.EXE When running a plu movement report if an item has a quantity sold but no revenue it will not show up on the report unless you include zero movers |
| WD 6313 |
SM2ITEM.EXE Byte 69 should be either a 0 or 1 but is a null after creating a batch. Scenario:1. Select Create/Edit a batch from the menu.2. Create a new batch and put at least one item in the batch and save.3. Use a btrieve file viewer to look at the batch header entry for this batch in gr2headr.btr.4.5. |
| WD 6335 |
WG2.EXE Need to support new method of reading Live Weight from a Fujitsu 9900 or 9950 Scanner/Scale using Fujitsu OPOS |
| WD 6354 |
WG2.EXE When using Full Touch POS the Cashier Messaging Box may be overlaying the enter key needed to satisfy the messaging option Scenario: 1. Send an immediate message to the POS 2. The message box pops up and the screen says "<<<<< Message Received >>>>>" "Press Enter to Continue. The Enter key may be partially or totally covered by the message depending on where the enter key was placed. 3. If the key is only partially covered the user can touch the enter key and continue. If the enter key is totally covered by the message, the system is essentially locked up and must be manually restarted |
| WD 6376 |
Install Landrive:\Grocery\CRP32001.NGN file gets deleted when upgrading to the same version of ScanMaster. Upgraded from 2.01.02-050 to 2.01.02-050 Scenario: 1. System is loaded with the 2.01.02-050 release 2. Rerun the upgrade from the 2.01.02-050 release CD 3. Check to see if landrive:\grocery\CRP32001.NGN exists Expected Results: landrive:\grocery\CRP32001.NGN still exists on the system Actual Results: landrive:\grocery\CRP32001.NGN does not exist on the system |
| WD 6407 |
SM2BAPLY.EXE When building an ad batch and setting a sale price on an item the items base price should remain what it was before going on sale. However, the base price is getting changed to the sale price, therefore, when coming "off sale" the item will stay at the sale price unless manually corrected at store level. |
| WD 6408 |
SM2BAPLY.EXE When a customer deleted an active batch the system should set the end data of the items to today minus one. Then the customer should be able to do a stage and have those items come off sale. this is not happening. The items are staying on sale unless manually being changed |
| WD 6409 |
SM2BAPLY.EXE When ad batches are supposed to come off sale and a stage has been run those items do not always appear in the current items to apply batch. It may take 2 or 3 stages before those items get included in the current items to apply batch and then come off sale. Scenario:1.There is an ad batch dated 4/18 - 4/242. It is 4/25 and I activate batches3.Current Items to Apply does not include ad batch items4.5.Expected Results: All items dated to come off 4/24 should be included Actual Results: Only some of items going on are included none coming off |
| WD 6411 |
SM2BAPLY.EXE When creating a batch you only need to put 1 item that is linked to like code to have the rest of the items linked to that code change. When you do this, however, only that item in the batch will have the modified by batch option updated in item maintenance. All other items will either not have anything or have the last batch number that affected them. Scenario:1. Item is linked to like code #12. All items with like code #1 go on sale for .793. I only put upc #1 in batch at .794. I activate the batch and all items go to .795. In item maintenance only upc #1 says modified by batch #1Expected Results: All items with like code should have modified by batch #1 Actual Results: Only upc #1 has the description all other UPCs do not have any description |
| WD 6413 |
SM2ITEM.EXE When adding an item to a batch and the clicking the price mode button it prompts you to save the item before continuing even though you have not made any changes to the item yet. Scenario:1. Create a new batch2. Type in upc number and hit enter3. click on price mode4. it asks you to save upc before continuing5.Expected Results: It should just go into price mode without saving anything since you haven't made any changesActual Results: It makes you save before it will take you into price mode |
| WD 6432 |
SM2EJMRP.EXE Does not respect refund, return, cancel movement, voids, error corrects, suspended/retrieved sales. The Problem :sm2ejmrp.exe doesn't respect refunds, returns, and cancels Scenario: 1. Do a return, refund, and or cancel on reg 2. Check movement in sm2ejmrp.exe 3. Movement increments for each scenario Expected Results: Movement should not change for refund, should decrease for return, should not change for cancel Actual Results: Movement increments on all of the above |
| WD 6453 |
SM2RPAIR.EXENulls not being fixed in "String" fields. The Problem: Null characters are not being replaced by space characters when fixing files. Scenario: 1. Edit gr2item.btr to have one or more null in a string type field, i.e., Description 2. run sm2rpair.exe and select repair the item file. Expected Results: Nulls will be replaced by spaces Actual Results: Nulls are not replaced. |
| WD 6454 |
SM2RPAIR.EXESm2rpair sets Modifiedbybatch letter to 0 The ModifiedByBatch field in the item file has the Batch Type letter (HLO) set to a zero when repairing the item Scenario: 1. Ensure your gr2item.btr file has a batch number in the modifiedbybatch field. 2. Run sm2rpair against the item file. Expected Results: No change in the modifiedbybatch field, i.e., L888, H100 Actual Results: The letter type(LHO) part of the field is changed to a zero, i.e., 0888, 0100 |
| WD 6458 |
File Spec Change Need to change RecordCount field in Batch Headers to LJS (Left Justified Space filled) Scenario: 1. Due to the way the Batch Header RecordCount is updated it is necessary to format it as LJS instead of RJ0. |
| WD 6462 |
SM2BAPLY.EXE An item that does not have an ad flag enabled on it is then activated from a batch and when you ring the item it shows You Saved Amounts on the receipt. Scenario:1. Put an item in a Permanent batch(using standard batching)2. Activate that batch3. Ring Item on register4. Finalize the sale5. Expected Results: there should be no you saved amount because this was a permanent price change not a temporary one which are the only ones that should show a savings amountActual Results: are seeing a you saved amount that reflects the item price. This is because when the batch applies it is not updating the base price of the item to the new price |
| WD 6519 |
SM2ITEM.EXE
Change an item in Direct Item Maintenance to a Scale Item - then hit SAVE. Ring that item at the POS and get, "System Error - The following error has occurred and has been logged in REGLOG.001, (11) Division by Zero". What makes this peculiar is click on NEXT/PREVIOUS or EXIT in Direct Item Maintenance, a message states, "Item has changed, would you like to save?". As if never saved it before. |
| WD 6523 |
SM2ITEM.EXE When editing the Batch Header Start Date and End Date the Item Start Date and End Date are recorded incorrectly. Scenario:1. Create a batch with any start and end date you want2. Edit the batch and go to Header and Dates tab on any item3. Type in a new date for start date4. 5.Expected Results: You should see the Item start date look just like the batch start dateActual Results: The Item start date is recorded as yy/yy/mmdd instead of mm/dd/yy |
| WD 6537 |
SM2BAPLY.EXE In current items to apply batch you can have the same item in twice with 2 different prices due to like codes not updating Scenario:1. Put an item into a batch at any price as long as it is linked to a like code2. Put another item into a second batch at a different price that is linked to the same like code3. Stage all batches4.5.Expected Results: The items linked to the like code should appear only once and at the LOWEST PRICEActual Results: the item appears twice at both batch prices. |
| WD 6538 |
SM2ELMRP.EXEEJ Movement Report does not calculate like Item Maintenance Movement The Problem: When you suspend a transaction Item Maintenance records the movement immediately, EJ movement does not record the movement until it is retrieved and finalized Scenario: 1. Ring a sale on the register 2. Suspend the transaction 3. Run an EJ Movement Report 4. Look in Item Maintenance at the movement for that item Expected Results: Both the EJ report and Item Maintenance should be identical Actual Results: Item Maintenance is increased by the amount of items sold in the transaction and EJ Report does |
| WD 6546 |
WG2.EXE Scanner data is being lost through the RS232 comm transmission. Though rare, one or two digits of the code may be lost causing transposition in the price of a random weight (type 2) UPC or causing a NOT FOUND on a non-random weight PLU. This is generally caused by a lacking of hardware performance as compared to the software level / feature set. As serial data arrives, one digit at a time, the serial driver is not able to receive the digits as fast as they are arriving. Example: Random weight UPC-A 2 12345 60123 4 ($1.23) may appear as 2 12345 61234 ($12.34) if a digit is lost |
| WD 6560 |
WG2.EXE Register gets into a continuous loop with Automatically Switching Offline - Press clear to continue. Then goes to Please wait while going offline. Then back to Automatically Switching offline. Register is getting a 1022 error which is the MicroKernel is Shutting down. From that point on, the register is trying to reset itself but can't because btrieve no longer exists. |
| WD 6566 |
SM2BAPLY.EXE, SM2BATCH.EXE & SM2ITEM.EXE Bottle link is deleted when items go off sale Scenario: 1. create a batch with items that have bottle links2. activate the batch3. activate the off sale for the batch4.5.Expected Results: item should remain on bottle linkActual Results: items bottle link is removed |
| WD 6611 |
WG2.EXEInterleave 2 of 5 requires left padding to 14 digit length Barcodes that come though OPOS have been assumed to be fixed at 14 digit lengths. This is not the case. Research reveals they may be less than that - down to 2 digits. The POS is therefore erroneously padding the smaller 2 of 5 code on the right instead of the left. Scenario: 1. Scan Interleave 2 of 5 code of 1200000013 (10 digits) on 9950 Expected Results: POS accepting and looking up 1200000013 Actual Results: POS accepting and looking up 12000000130000 |
| WD 6679 |
SM2PCKUP.EXEAuto Pickup then edit and accept cause pickup rollover & Out of sheet balance. The Problem: Auto Pickup then edit and accept cause pickup rollover & Out of sheet balance. Scenario: Run a system clear using SM2CLR.EXE BOCF setting 'Use Auto Pickup Feature' set to 'Y' Yes 1. Ring $100.00 open dept sale for cashier 456 and tender $100.0 to cash 2. Sign off the register or not 3. On the backoffice run Pickups/Loans 4. Select the cashier 5. Click on the Auto Button 6. Go to the cash pickup field and enter -25.00 (notice that the cash field in the new drawer total column in $25.00, but the total at the bottom of the column is zero. 7. Click accept and follow the steps to finish the pickup. If you check gr2store.btr the 0 date O record in the total pickup/loan field 'Total Pickup Amount' you will see '0000000000010000'The 'Total Pickup Amount' should be '0000000000007500'You could follow this through by settling the cashier and running an EOD (End Of Day) and completing the Office Reconciliation and Final Deposit and see the that Store Totals Report shows a 'Pickup Rollover' of $25.00 and an 'Out of Balance' of $-25.00. |
| WD 6738 |
SM2SETTL.EXEDelayed Cashier/Lane Settlement started before cashier logs onto register and completed after sales have been tendered, deletes record for cashier/lane in gr2prstl.btr & gr2prsrg.btr. Causes an Out of Balance situation Scenario: 1. Ring Sales for a cashier/lane 2. Delay the cashier/lane 3. Change the date 4. Run the EOD 5. Run Cashier/Lane settlements 6. Select the delayed cashier/lane 7. Leave the cashier/lane up on the delayed settlement screen 8. Sign on the register using the same cashier/lane number that you are trying to delay settle on the backoffice 9. Ring sales and tender the transactions. 10. Finalize the delayed settlements by clicking on Accept 11. Finish the office reconciliation and final deposit. 12. Try to do a pickup on the cashier/lane - they will be unavailable for pickup - exit pickups/loans 13. On the register ring another sale an tender the transaction 14. Go into pickups/loans again and select the cashier/lane that you delayed settled 15. Notice that the cashier/lane is only accountable for the last transaction rung on the register. Expected Results: The cashier/lane is still accountable for all transactions rung Actual Results: The cashier/lane is not responsible for any transactions rung while the cashier/lane was being delay settled. |
| WD 6766 |
SM2ADJST.EXEAdjusted Cashier/Lane Settlement started before cashier logs onto register and completed after sales have been tendered, deletes record for cashier/lane in gr2prstl.btr & gr2prsrg.btr. The Problem :Adjusted Cashier/Lane Settlement started before cashier logs onto register and completed after sales have been tendered, deletes record for cashier/lane in gr2prstl.btr & gr2prsrg.btr. Causes an Out of Balance situation Scenario: 1. Ring Sales for a cashier/lane 2. Settle the cashier/lane 3. Change the date 4. Run the EOD 5. Run Cashier/Lane Adjusted Settlements. 6. Select the settled cashier/lane 7. Leave the cashier/lane up on the adjusted settlement screen 8. Sign on the register using the same cashier/lane number that you are trying to adjust on the backoffice 9. Ring sales and tender the transactions. 10. Finalize the adjusted settlement by clicking on Accept 11. Finish the office reconciliation and final deposit. 12. Try to do a pickup on the cashier/lane - they will be unavailable for pickup - exit pickups/loans 13. On the register ring another sale an tender the transaction 14. Go into pickups/loans again and select the cashier/lane that you delayed settled 15. Notice that the cashier/lane is only accountable for the last transaction rung on the register. Expected Results: The cashier/lane is still accountable for all transactions rung Actual Results: The cashier/lane is not responsible for any transactions rung while the cashier/lane was being delay settled. |
|
|
|