Item Description
|
Certification |
The Verifone MX915 and MX860 have been Certified with the current
NCR ScanMaster V2 and ISS45 V8 POS applications in conjunction with
the CP 828.7 gold 24 for EMV.
The MX925 is compatible to the
MX915 and is also supported.
Details of the Certified
Product Configuration
| Component |
Version |
| |
|
|
POS |
|
|
ScanMaster |
2.09.00-140 |
| |
|
|
Payment Terminals |
|
|
MX915 |
|
|
Operating System Version |
1.6.14.1404 |
|
Application Version |
mx_xpi_5200j-Build 20 2/22/16 |
|
MX860 |
|
|
Operating System Version |
MX0007US/RFS00018 |
|
Application Version |
2.6.4A-03 -
Feb -2016 |
| |
|
|
Connected Payments |
|
|
CP Version |
828.7 gold 24 |
|
MTX_EPS.DLL |
828.7.21.26 |
|
MTX_POS.DLL |
828.1.0.98 |
|
|
New Feature |
Add Option to WIC CVV Paper Program to Allow for Non-Whole Dollar Amount
Vouchers.
(ER 810081501 / CRD 447386 / FSD 447386) |
|
New Feature |
SSCO Assist Mode for Manual Coupons and Discounts.
Requires SSCO for ISS45
5.00.01.00.37. Link supplied above.
(ER
ER 20140917-7167 /
CRD 452291 / FSD
452291) |
|
New Feature |
Survey Template Enhancement for Ball's Foods.
Enhance code to allow
survey template to have the same 16 digit code that loyalty uses. The
current format for IVR_SURVEY is as follows:
MMDDSSSSCPPPTTTT
MM –
Month 2 digit
DD – Day 2 digit
SSSS – store #
C – check digit
PPP – POS #
TTTT – Ticket #
Enhance code to allow for 3 digit
AWG number in IVR_SURVEY:
MMDDYHHSSSPPTTTC
MM – Month 2 digit
DD
– Day 2 digit
Y – Last digit of year
HH – Military Hour
SSS – AWG
#
PP – POS #
TTT – Ticket #
C – check digit
CouponNumEncoded:
T3 H2 Y1 T2 S2 M2 T1 S1 P2 M1 D2 S3 D1 H1 P1 C
The Check Digit is
calculated using Standard Mod10method. Below are the steps needed to
calculate the check digit. Enhancement is required if this is different
from what ISS45 currently does:
From the right to left, start with odd
position, assign the odd/even position to each digit
Sum all digits in
odd position and multiply the result by 3
Sum all digits in even
position
Sum the results of steps 3 & 4
Divide the result of Step 4
by 10
The check digit is the number which adds the remainder to 10
(ER 811091501 / CRD 453059 / FSD 453059) |
|
Updated Feature |
Performance enhancements to General Batches. General batches can be
rather slow when batching promotions with a large number of linked items
that are already on file. Performance changes were done to storeline but
never ported to ISS45. These changes cover a more than just promotion
batches. In some cases the customer is having the same promotion 100 times
in the same batch with that promotion having 810 items linked to it.
Attached are the batches that the customer used to recreate the issue.
1. Create a promotion batch and a Promotion link batch that links the
promotions to 100's of items.
2. Process the batches into the system.
3. Delete the batches and reprocess the batches.
Expected Results:
Batches should apply in a reasonable amount of time.
Actual
Results: It's taking hours to process multiple batches.
(CRD 447151 /
FSD 447151) |
|
Updated Feature |
8.1.8.0-050 corrected an issue with Loyalty promotions where the tax on a
promotion attached to an item was not forgiving tax. It was reported that
promotions were not calculating as they previously were and that taxes
should not be forgiven. Ultimately, this will be able to be controlled by
an option in the Loyalty Promotion setup where the promotion can be
explicity designated to forgive tax or not.
However, since this change still has to go
through the CR process, a temporary method of reverting the system to
previous behavior is being provided via a flag in the winpos.ini.
Adding the following line to the WinPOS.ini will
cause the tax calcuation for such promotions to behave as prior to
8.1.8.0-050:
DoNotForgiveLoyaltyPromotionTax=Yes
If this line is absent from the winpos.ini or if
it set to No, the current POS behavior will be preserved. |
|
WD 318213 |
Enhanced promo. tax not being forgiven correctly on Food Stamp Items if
PLU's have different tax sets than the dept.
Scenario:
1. Set up
#900 and 901 with TAX #2 at 9 %.
2. Set up Promo #14 with a Mark-Down
Department (#2) with Tax #1.
3. Rang the sale, tendered to EBT Food
Stamps and only .86¢ Tax was forgiven and .10¢ Change was given.
Expected Results: Correct amount of tax should be forgiven
Actual
Results: Tax being for given is either to much or to litte, leaving either
a balance due, or change back to the customer. |
|
WD 426939 |
Recall Transaction Fails when Frequent Shopper, Tax, and Late Swipe are in
order.
Setup: Create 2 items, each are taxable, and each have a FS
discount in PLU Maint. Ensure that "Reprocess ticket at Late Swipe" is set
to YES. Have function 961 (Ent. Frequent Shopper Number) is tied to a key.
Also, ensure that function 913 (Save/Recall Order) is tied to a key.
1. Ring the two items created above.
2. Press key for function 961
3. Enter FS Number. The discounts should apply
4. Save order with
Function 913
5. Recall Order with Function 913
Expected Results:
The order will recall and discounts will be applied
Actual Results:
The order fails to be recalled properly and will be voided out. Also, if
you look at the Void amount, it usually will be greater than the Save
amount on the original receipt. |
|
WD 443391 |
SSCO: Prompt for Member Card at Start of Ticket = Yes will not prompt for
ALT ID on PIN Pad if first item scanned.
Prompt For Member Card at
Start of Ticket = Yes
Do Not Prompt for Frequent Shopper at the
Beginning of a Ticket = No
These options can affect the the
Alternate ID on teh PIN Pad on a SSCO. |
|
WD 443393 |
SSCO will not prompt customer for member card/secondary ID at pinpad
unless first item is weighted/qty item and member card at start of ticket
is set. |
|
WD 445922 |
SSCO: PinPad Gets Stuck for several minutes before releasing the SSCO to
continue.
Scenario:
1. Ring up item
2. Swipe EFT card at
member prompt on PIN Pad
3. Press Finish and Pay
4. Press GO BACK
button
Expected Results: SSCO stays in sync.
Actual Results: PIN
Pad was stuck for several minutes before releasing control to SSCO. |
|
WD 445923 |
SSCO: Upon power fail recovery the SSCO is in the wrong state and results
in Wrong Function message. |
|
WD 445976 |
Group Promotion Receipt shows wrong information.
Scenario:
1.
Setup 10% employee discount by department with delayed turned ON
2.
Ring in 2 or 3 items
3. Tender transaction
4. Print Receipt
Expected Results: Receipt prints and savings today line would show the
discount
Actual Results: Recepit prints but savings today shows the
discount as subtraction and as addition so it shows SAVING GROUP TOTAL as
0 but the receipt is correct the total has been lowered by the savings. |
|
WD 446367 |
SSCO- Swiping Employee Card and Pressing Finish & Pay can cause lockup. |
|
WD 446368 |
SSCO Pressing Finish and Pay and Pressing GO BACK button and trying to
scan item results in "Wrong Function" message. |
|
WD 446594 |
SSCO: Fresh install of an SSCO with ISS45 version 8.1.8.0-050 has issues
with Databar Coupons.
In the logs there is a Databar Error "In
StartDataBarEngine: Error creating instance of databar engine dll,
rc=[80040154]". Another issue occuring is "[FATAL ERROR: TRANSACTION WRITE
PROBLEM!!!!]" Unable to recover from this error.
Scenario:
1.
Install Fresh SSCO/ISS45 (8.1.8.0-050)
Expected Results: Install
should work. No errors.
Actual Results: Errors occur and SSCO will
not run. |
|
WD 449944 |
SmartCard WIC record: Ohio SmartCard WIC - Some Transactions rejected by
the state with a CRC32 error.
Some transactions that are submitted to
the state are not getting paid. Reconciliation report states,
‘Questionable for Adjustment’. Upon further investigation, those
questionable transactions are being marked as a CRC32 error.
Year,
Month and Day parameters describe an un-representable DateTime |
|
WD 449945 |
Online WIC record: Ohio SmartCard WIC - Some Transactions rejected by the
state with a CRC32 error.
The site went live with SmartCardWIC around
10-18-15. Some transactions that are submitted to the state are not
getting paid. Reconciliation report states, ‘Questionable for Adjustment’.
Upon further investigation, those questionable transactions are being
marked as a CRC32 error The error is Year, Month and Day parameters
describe an un-representable DateTime. |
|
WD 450385 |
Problems with Reprocess on Late Swipe Not Redeeming Customer Points for
Items Correctly.
NO Loyalty - Straight ISS45 Member Cards
Customer has 18 points.
Did not enter member card at start of
transaction.
Purchase item that requires 10 points to redeem.
Rang
up 2 items.
Enters member card. (Reprocess on late swipe turned on)
Box comes up prompting cashier to use points. (Only shows one item)
Cashier presses yes.
Deduction is taken on both items. (Cost 20 points)
Press total to complete the order.
Box comes up stating that there is
not enough points.
Cannot cancel items. Must void transaction.
Further Testing proves that IF the Member Card is scanned BEFORE the point
reward item is rang up - it will work correctly. It is only after a point
reward item is rang and Member Card follows somewhere in the transaction.
Using the same steps, but do not enter member card during transaction
and wait till total is pressed, it will complete the transaction and
customer will have negative points.
Reprocess on late swipe needs
to go through transaction one item at a time and validate that the
customer has enough points to redeem.
Expected Results: Regardless
of where the card is swiped in the order, should only allow rewards for
available points.
Actual Results: All reward items are given to
the customer even though they do not have enough points. Then it shows
them as negative points. |
|
WD 450981 |
Tfserver.exe not processing transactions into XML for TrickleFeed
processing.
Customer is using the TrickleFeed process to export
transactions out to XML in which the warehouse then uses this
information for movement and customer analysis. 8180-070 included a new
tfserver.exe (1.1.0.3) - this new file cases the XML files to have no
transaction data, only header information.
Scenario:
1. Stop
POS_SRV_Manager
2. Drop the attached XML files into c:\pcmaster
2.
Copy the attached transact.qdx into c:\pcmaster\qdx
3. Create folder
path C:\AccOutBox\Order
4. Reboot the server
After the reboot, 5
to 7 minutes the XML files will be in the Order folder you created.
Expected Results: XML files contain Transaction Data
Results:
XML files contain only header information, no transaction data. |
|
WD 451277 |
Late swipe after Total is being treated the same as a manual return to
sale. The order discount is being reversed and re-applied during the
ticket reprocess. It should be noted that the manual return to sale will
still show multiple discount lines, by design. |
|
WD 451460 |
WIC CVV - Exiting sale mode using EXIT/NO key and cancelling CVV mode does
not reset voucher amount.
Scenario:
1. Set GSP, "WIC CVV prompt
options" to prompt for amount OR amount + exp date.
2. Set up a $5.00
WIC CVV Item in PLU Maintenance.
3. Assign a key to EXIT/NO (27) value
in keyboard programming.
4. Enter WIC CVV sale mode by using WIC CVV
key.
5. Enter $5.00 for the voucher amount. The "WIC CVV TRANSACTION"
banner should show above the data entry area.
6. Press EXIT/NO key (not
touch-screen menu button). The "WIC CVV TRANSACTION" disappears. At this
point, the POS is no longer in WIC CVV sale mode and all entered vouchers
have been cancelled.
7. Enter WIC CVV sale mode again by using WIC CVV
key.
8. Enter $3.00 for the voucher amount. The "WIC CVV TRANSACTION"
banner should show above the data entry area.
9. Try to sell the $5.00
item.
Expected Results: The $5.00 item should not be allowed
to be sold. The "WIC Voucher amount exceeded" control check should fire,
since the total voucher amount should be only $3.00.
Actual
Results: The item sells because the POS never reset the cleared $5.00
amount and it thinks that the voucher amount is actually $8.00. An attempt
to sell another $5.00 item fires the control check because the $8.00
amount is now exceeded.
|
|
WD 452361 |
Replace all Retalix POS splash screens and watermark screens with NCR
screens. |
|
WD 453068 |
StoreBalance.RPT and Store Sales.RPT are missing from the 8.1.8.0-070 and
8.1.8.0-080 Manual Patches
Manual Patch 8.1.8.0-070 was built from an
8.1.8.0-060 build that was missing package 33 which includes the
storebalance.rpt and storesales.rpt.
These files were included
correctly in the CDS releases for 8.1.8.0-070 and 8.1.8.0-080. |
|
WD 453181 |
Master Provider Parameter is Missing M-DOT option from dropdown box.
After upgrading to 8180 or higher - in the GSP - Store\Technical\Master
Provider\Master Provider - option for MDOT is missing. Options are None,
Retalix Loyalty and PDX Prior to 8180 - options were - None, Retalix
Loyalty, PDX and MDOT. |
|
WD 453642 |
Problems with Reprocess on Late Swipe Not Redeeming Customer Points for
Items Correctly.
Scenario:
NO Loyalty - Straight ISS45 Member
Cards Customer has 18 points.
Did not enter member card at start of
transaction.
1. Purchase item that requires 10 points to redeem.
2
Rang up 2 QTY and scanned item.
3. Enters member card. (Reprocess on
late swipe turned on) Box comes up prompting cashier to use points.
4.
Cashier presses yes. Deduction is taken on both items. (Cost 20 points)
5. Press total to complete the order. Box comes up stating that there
is not enough points.
6. Cannot cancel items. Must void transaction.
Need to have reprocess on late swipe go through transaction one item
at a time and validate that the customer has enough points to redeem.
Expected Results: Regardless of where the card is swiped in the order,
should only allow rewards for available points.
Actual Results:
All reward items are given to the customer even though they do not have
enough points. Then it shows them as negative points and you must cancel
the transaction. |
|
WD 453729 |
EMV Testing: ISS45 is sending Reset/Clear and Begin Order and causing an
approx 3 sec delay after 2nd item scanned.
Scenario:
1. Sign on
POS
2. Ring 1st item (no delay)
3. Ring 2nd item (approx. 3 second
delay)
Expected Results: No delay after 2nd item scanned.
Actual Results: Approx. 3 second delay after 2nd item scanned. |
|
WD 454186 |
POSW32.EXE uses 100% CPU after new posguidl.dll included in 81.8.0-080 is
installed.
After upgrading to 8.1.8.0-080 the POS will spike at 100%
CPU. With this updated DLL in place, the POS uses all availalble CPU. |
|
|
|
|
 |
 |
