Enhancement or Fault Number

Item  Description

SM2EJ.EXE

EJ processor creates B records for TLOG for 7 types of Transaction. 

The following TLOG types will not process through the EJ Processor and has been modified to do so

( - Keyed MFG Coupon

) - Keyed Str Coupon

P - Instore Charge Payment

G - Gift Certificate Sold

M - Money Order Sold

! - MFG Coupon Paidout

, - Store Coupon Paidout

The EJ processor changes the last bit 'N' to a Y with 2 dots over it.

SM2EJ.EXE

Change EJ processor to NOT shutdown after two bad TLOGs in a row. 

 Currently when the EJ processor gets any runtime errors, database issues, or problems processing a TLOG, it will rename the T*.* file to a B*.* file and then restart the EJ processor.  If the EJ processor gets another error on the next TLOG it processes, it also renames the T*.* file to a B*.* file, but it does NOT restart the EJ processor.  This was done to keep the processor from skipping over TLOG due to some system or database error. 

However, if the problem is in the TLOG file itself, due to a corrupt file, or invalid data that can't be processed, it should not stop processing.  Currently the EJ processor can not distinguish between TLOG issues and other issues.  This needs to be modified to allow the EJ processor to continue processing if the problem is in the TLOG.

WD 10311

EJTMFIX.EXE

Change EJ TLOG Fix application to be run unattended.

WD 10321

WG2.EXE

ScanMaster with WinEPS OpenEPS is not handling Partial approval with Cash Back Properly.  ScanMaster with WinEPS OpenEPS is not handling Partial approval with Cash Back Properly.  ScanMaster was assuming the Approval amount from WinEPS did not include the cash back amount since there was a cash back amount that was passed back by WinEPS along with the Approval amount.  It has been found, though, that the approval amount does include the cash back amount.  This has caused erroneous code execution to be made which in some instances causes the partial approvals to process incorrectly.

The code will be modified to account for the approval amount to have the cash back amount included.

Note: Just as always, on a partial tender, any cash back amount will be automatically applied towards the remainder of the sale and the customer may end up with less cash back then they expect.  ScanMaster has always worked in this manner.  It is recommended to explain to the customer that if they wish to receive cash back, they should make this the final tender and use a different tender first for partial tender.

WG2.EXE

Change ScanMaster with the S&H TCP/IP interface to allow for the display of customers level or point accumulation.  This is needed because the S&H payment terminal is no longer available in this configuration which served as the display for the customer’s level and points.  Because this is no longer available, ScanMaster needs to display the customer's level and accumulated points on the operator display along with the customer's name which is being displayed.  This information should be available from the time it is received from S&H throughout the remainder of the sale.

WG2.EXE – Weights and Measures Changes - Need to make Specific Weights & Measure Information available at POS including Certification ID. 

The minimum information needed is shown in the following example 

Mfg: StoreNext

Model: ScanMaster

Ver: 2.05.02.06

CC#: 95-083 

This information must be present on the screen at all times so when a W&M representative is at the store the  information is able to be seen by looking at the screen at any time.

Installation

tstatus.dat is not updated on the upgrade to 2.05.01-050. 

The Problem :FSA prompt

Scenario:

1.FSA is turned on

2.At tender there is no FSA prompt

3.FSA should be included in the tstatus.dat file

Expected Results:

FSA should be an available prompt

Actual Results:

No prompt

SM2EJ.EXE

 EJ Processor not creating B*.* files when getting certain errors.  If the error is a database error (any error with a number less than zero, or greater than 500), that occurs in the middle of a transaction, the EJ processor is not creating a B file.  If the error occurs when the transaction is started, or as it is being closed, it handles the situation correctly.

The TLOGS used to duplicate this problem are attached. 

Scenario:

1. Unzip the attached TLOGS into the F:\JOURNAL directory

2. Start the EJ processor

Expected Results:

EJ Processor gets an error, creates a B file, and exits

Actual Results:

EJ Processor gets an error, and exits without creating any B files, which causes the EJ processor to get the same error again when it is restarted manually

EJTMFIX.EXE

 EJ Fix is incorrectly resetting the last character (y with dots over it) in the records

If the last character of a record in the TLOG is "y with dots over it" it tells the EJ processor to not "reprocess movement" when (or if) the TLOG is reprocessed by the EJ processor.  The EJTMFIX.EXE application is correcting various known invalid TLOG issues, and resetting the "y with dots over it" to a "N".  This means that the movement will be processed twice for all records that were previously y with dots over it.

Scenario:

1. Get a "B" or "T" file that has some records with the "y with dots over it" in the last character

2. Execute EJTMFIX.EXE application, and click the "Process" button

Expected Results:

Various issues such as invalid dates, nulls, and other small issues are corrected, and if the last character  is "y with dots over it" remains.

Actual Results:

All issues are properly resolved, but all "y with dots over it" are changed to N

SM2USCO.EXE

ScanMaster and U-Scan get out of sync.  Customer must enter cash twice for the sale to finalize since it is out of sync.

Scenario:

1.Ring an item.

2.Scan a not found item

3.Put the item on the scanner/scale

4.Press Back button

5.Remove item from the scanner/scale

   (At this point ScanMaster is in Enter Price and Dept state still because ScanMaster never got a       message from USCAN that the Back button was pressed)

6.Hit finish and pay.

7.Press Cash button.

8.Insert $20

   (ScanMaster does not recognize the cash was inserted as a tender since ScanMaster is not at Total state)

9.The sale does not finish the attendant goes into Direct Mode clears ScanMaster from Enter Price and Dept state.

10.The $20 is removed from the Bill Acceptor

11.Reinsert the $20.

Expected Results:  Customer should not have to insert the money twice.  ScanMaster and U-Scan should not be out of sync

Actual Results:  ScanMaster and U-Scan are out of sync.  The customer gets change from the second $20 after the sale is tendered and the customer also gets the first $20 back in the change. The customer will get too much money back.