Enhancement or Fault Number

Item  Description

The initial U-Scan interface made use of the MFC Wrapper Class from the Microsoft MFC Library for use in Socket communications between the POS and the ScanMaster self-checkout API.  It was found that in some circumstances similar to the U-Scan interface implementation the socket mechanism had instability and synchronization issues.  The communication mechanism was changed to Named Pipes to provide a more stable communication mechanism.

U-Scan  -  after EOD the Customer Stations were offline and required reboots to connect to the ScanMaster system.

Signing on to U-Scan lane from the Attendant Station errors would occur -  Device: : Offline {VPOSOMAN} error message and in the black information box, the message Connection Lost would be displayed.  Go to direct mode and see that ScanMaster is up and online.  Can hand key an item in direct mode and it appears in ScanMaster, but it does not appear on the U-Scan. To get reconnected, a reboot must occur.

SM2F2BAT.EXE

Running Convert PLU Report to Batch does not bring over promotion code number

Scenario:

1.       Enter a promo code on an item in item maintenance

2.       Go into convert PLU report to batch

3.       Create a batch of items

4.       Edit the batch

Expected Results:  Promo code should still be on all items

       Actual Results: all items have dropped the promotion code number

SM2PDIMR.EXE

Item Movement Report - Variable weight items have 0.00 weight when price is in item record

Scenario:

1.       Put item price per pound in item record

2.       Sell item

3.       Run Item Movement report4

Expected Results: total revenue / price = weight sold

Actual Results: weight = 0.00

SM2PDIMR.EXE

Item Movement Report - Scale items calculate wrong cost

Scenario:

1.       Sell scale item

2.       Run item Movement report for the item

Expected Results: Total cost = weight x cost / unit

       Actual Results: cost is equal to cost/unit x Quantity