Enhancement or Fault Number

Item  Description

WD 11998

Set up EAN 99 Coupon in System, create EAN 99 coupon for 1.74 

Ring PLU 9  4x1.69 =                        Total is    $6.76 NF

Take EAN Coupon for $1.74 =          Total is   $5.02

Take Vendor Coupon for $1.50 =     Total is   $3.52

Ring in a greeting Card for $2.99 =   Total is  $6.51

Now Food Stamp is $6.51 this is wrong should be $3.52 

Food Stamp Total is Wrong. It is making customer pay for the EAN amount. 

If you do same sale using Store and Vendor, not EAN, it works fine. 

EAN is set to validate as UPC 5 but doesn't make a difference.

WD12133

W&M Certificate Number update: 08-087A1 - POS Screen Needs to reflect the new W&M certificate number at all times

WD12470

Sign on message fails when message end date is 2010 or system date is 2010 

Scenario:

1. Screen 1-12-1

2. System date is 12/30/09

3. Create message with start date 12/30/09, set "How many days?" to 1 (system creates ending date of 12/30/09)

4. Sign onto register and message will appear

5. Change message (step #3 above) to "How many days?" to 2 (system creates ending date of 12/31/09) the system date has not changed

6. Sign onto register and message will appear

7. Change message (step #3 above) to "How many days?" to 3 (system created ending date of 1/1/2010) the system date has not changed

8. sign onto register and the message will not appear

9. The same thing happens (message will not appear) if the system date rolls to x/x/2010 

Expected Results: Sign on message will work with any year 

Actual Results: Sign on message fails when message year is 2010 or system date is 2010

WD 12490

SmartWIC - V7 EBT WIC Reconciliation report displaying wrong dates

Scenario:
1. Run the WIC_EBT.EXE executable, go to REPORTS, select Reconciliation File Report
2. Go to "Select Report Date Type", select "by Day", select the drop down
3. After 1/1/2010, any older files (*.A99 files) will be displayed incorrectly
4. A file from 12/31/2009 will display as 12/31/2019, a file from 6/7/2008 will display as 6/7/2018
5. You can open the file with no issue and the data within the file is correct

Expected Results: File dates will display correctly; i.e. the proper year

Actual Results: Any file date older then 2010 is displayed with an extra 10 years added; i.e. 2008 displays as 2018, 2009 displays as 2019

WD 12491

SmartWIC - V7 WIC_EBT.EXE getting error 'Run-time error 3420' - VB error

Scenario:
1. V7.1.3.0-110, run the WIC_EBT.EXE file
2. Go to REPORTS, Reconciliation File Report
3. If the c:\pcmaster\wic\history file has too many *.A99 files, the dealer had 189, you will get the run time error
4. Zip up the older *.A99 files, we left 38, and the report works
 

Expected Results: No matter how many *.A99 files the reports will work

Actual Results: Too many *.A99 files and you get a run-time error

WD 12492

SmartWIC - V7 Cannot open any claim file with a date of 2010 with WIC_EBT.EXE get "No Reconciliations For This Date" error 

Scenario:

1. V7.1.3.0-110

2. Ring up some EBT WIC items and tender the order with EBT WIC

3. Run SWEXTRCT 1, this will create a claim file in the c:\pcmaster\wic\working directory

4. Rename this claim file to a correct ZZ######.S99 file and zip it into the c:\pcmaster\wic\claim directory

5. Start WIC_EBT.EXE, go to report, and then claims

6. Attempt to open the claim file by clicking on the PREVIEW button 

Expected Results: You can open any claim file regardless of the year; i.e. 2000-2010 

Actual Results: A claim file with a date of 2010 generates an error "No Reconciliations For This Date, Nothing to Report for this Date?? 1/5/2010 Returning to frmMain."

WD 12548

Set Parameter:

Go to 6 1 2 1 3 and turn OFF # 12

Parameter reads -> Password Required with Cashier Bar-Code (IF you say NO) then it will work like before

Previous versions did not require the Manager to enter password when using scan card to override control check. Newer release requires intervention at the lane, password entry.

Scenario: Create Manager Scan Card - 8888SSSSCCCC (k)  S= store number, C= Cashier number and a check digit. (8888010101052) Store Number 101, Cashier/Manager number 105 for this example.

1. Set Store Number to 101

2. Create Cashier number 105 and give all privileges

3. Create Control Check as Warning Only with a privilege of 8.

4. Put Control Check on a function, for example voiding an item over 1.00

Ring Item, void item and press Total. Control Check shows up, press Clear, scan manager card.

On 7121-070 - the control check is cleared by the scan of the card, cashier can finalize sale.

Starting at 7130-050, scan card, and now prompt is waiting for password entry.

We have never stored the password in the card barcode; the system was satisfied with the scan of the number only in the past, provided user on card had privilege.  

Expected Results: Control Check is cleared and cashier can finalize sale. 

Actual Results: Control check is cleared but prompt is waiting for password entry

WD 12560

SmartWIC - Can't open a WIC claim file dated 2010 with WIC_EBT.EXE 

Scenario:

1. V7.1.3.0-110, EBT WIC

2. Sell EBT WIC items and tender order with a EBT WIC card

3. Run an EOD

4. After the EOD has completed and the claim file has been created start WIC_EBT.EXE

5. Attempting to open the latest claim file dated 2010 gives an error "Nothing to report for this date...." 

Expected Results: Can open any claim file regardless of the date

Actual Results: Cannot open any claim file dated 2010

WD 12561

SmartWIC - If a claim file cannot be opened, when you close the error message window you get a run time error 3420 

Scenario:

1. 7130-110 with EBT WIC (SmartWIC)

2. Ring a sale and tender with a EBT WIC card

3. Run EOD so a claim file is generated

4. After the EOD completes start WIC_EBT.EXE

5. Open the new claim file, get an error, click OK for the error, close the WIC_EBT.EXE screen

6. Get a "Run time error '3420" error

Expected Results: Can close the WIC_EBT.EXE window with no errors 

Actual Results: If there is an error opening a claim file with WIC_EBT.EXE, when you close the executable screen you get a run time error