Page Comparison

16068 Despite the existence of an issued credit note tagged to a particular customer, change of customer was allowed in a return bill through bill modification

Module:

POS – Back Office – POS Control – Bill Modification

Reported Version:

1.102.0

Scenario:

1. Create a bill B1 with Customer C1
2. Create a return bill B2 against the customer C1 and issue a Credit Note. Save the Bill.
3. Change the customer to C2 in the same bill.

16466 Bills of customers created with GINESYS Loyalty could not be found while adjusting return bills if the loyalty software was changed

Module:

POS – Normal POS
POS – POS as Delivery Slip
POS – POS as Collection Centre

Reported Version:

1.107.0

Scenario:

Earlier GINESYS Loyalty was being used by this GINESYS user. They later switched to some other CRM software. A customer had a loyalty card made with GINESYS Loyalty tagged in the bill. Now the user switched the CRM software. Now while creating Return Bills with the same Customer tagged, both Customer and Loyalty Card Number was being searched in the lookup. Now since GINESYS Loyalty was not integrated anymore; the previous loyalty card number was not getting populated and the lookup query was failing - so the source Bill was not being shown for adjustment.

16773 Unhandled error was being displayed during data sync when  excise applicable Charge  was being synced to the store.

Module:

POS – Administration – Data Exchange

Reported Version:

1.105.0

Scenario:

Modify any excise applicable charge and run sync from HO to Store.

21765 On editing customer while creating a POS Bill, OTP validation was skipped; although the benefit was OTP enabled.

Module:

POS – Normal POS
POS – POS as Collection Centre

Reported Version:

1.111.0

Scenario:

1. Select a loyalty customer (with OTP enabled benefit) in a POS bill.
2. Modify the customer details.
3. Go to payment option and redeem points.
4. See that the OTP validation is skipped despite the benefit being OTP enabled.

21798 In an Easyrewardz enabled system, Loyalty discount amount was saved positive value instead of negative while the item is returned.

Module:

POS – Back Office – Reports

Reported Version:

1.113.1

Scenario:

While returning an item against bill, if Easyrewardz is enabled, then the loyalty discount amount against bill was saved as negative value after saving the return bill. However, the total discount amount was properly reversed. So, there was no problem in cash mismatch but in reports, erroneous data was displayed.

22016 In an  Easyrewardz  enabled system, for percentage based discount type coupon, the discount percentage factor (%) was being displayed as the discount amount

Module:

POS – Normal POS
POS – POS as Collection Centre

Reported Version:

1.113.2

Scenario:

In Easyrewardz percentage based discount type coupon, the discount percentage factor was being displayed as the discount amount.
E.g. suppose according the Easyrewardz setup, there is a discount coupon which provides a discount of 10%. Then on a bill of INR 2000, it should provide a discount of INR 200. But it was showing a discount amount of INR 10.

16625 The records in Store Performance document report were not ordered serially that is according to the date

Module:

POS – Back Office – Reports – Store Performance

Reported Version:

1.51.2

Scenario:

1. Go to POS > Back Office > Reports > Store Performance
2. Run the report
3. Observe that the records in Store Performance document report were not ordered serially that is according to the date

16812 Sales Person wise filter was not working in the Sale Detail Analytic report.

Module:

POS – Back Office – Analytics – Sale Detail

Reported Version:

1.107.0

Scenario:

1. Go to POS > Back Office > Analytics > Sale Detail
2. Run the report, filtering results on the Sales person
3. Observe that the records are not being filtered properly

19621 Sync failed due to wrong value in GRC Advice charge information.

Module:

POS – Back Office –Transactions  - Goods Receive Advice

Reported Version:

1.110.0

Scenario:

Sync failed due to a null value in the “Sign” column of Applied Charge in GRC Advice.  This generally occurs when the user misses to put the sign while generating GRC Advice for the POS site. So when the document is sent to the site, there is a conflict with the database.

21694 System gets hanged if barcode based search is done while searching for return bill.

Module:

POS – Normal POS
POS – POS as Delivery Slip
POS – POS as Collection Centre

Reported Version:

1.110.0

Scenario:

In case there are a lot of items then System got hanged if barcode based search was done while searching for return bill.

 21660 In Purchase Return Debit Note Report the Tax Details were showing wrong data

Module:

POS – Back Office – Transactions – Goods Return – Print [button]

Reported Version:

1.112.0

Scenario:

In case of outright track secondary POS site,
Go to POS > Back Office > Transactions > Goods Return > Print [button]
Run the Purchase Return Debit Note report (i.e. the Goods return report for the Outright Track secondary stores)
Observe that in the "Charge Details" section area of the report, VAT % on "Total Amount" was getting doubled