Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...


Control

Release Date

20 May 2019

HO Version11.145.0
POS Version1.
xxx
145.
x
5
Web Database Compatibility Version1.16
Features & Enhancements00
Bug Fixes
11
08
Navigation

Table of Contents

Bug Fixes

Serial

Dev IDIssue TrackerDescription
1
16532 N.A.16532 Respective POS Order Item information is not available in the POS bill Data source. Thus information are not getting printed while POS bill is saved

Module:

Normal POS - POS Bill - POS Bill Print

Reported Version:

1.145.0           40232

Scenario:

Observe that, respective POS Order Item information is not available in the POS bill Data source. Thus information are not getting printed while POS bill is saved

2
16240N.A.

16240 Bill could not be saved. Reason:

The INSERT statement conflicted with the CHECK constraint

... Error message is showing

while saving the

when the POS bill is saved with

Promotion

promotional items & Bill Discount

Module:

POS - Normal POS - POS Bill

Reported Version:

1.145.4     

   39855

  

Scenario:

  1. Go to
NPOS
  1. POS > Normal POS > POS Bill.
  2. Create a POS bill with Bill Discount & Promotion applicable items.
Save
  1. Try to save the bill.
  2. Observe that,
at the time of bill saving
  1. an error message is
showing -
  1. shown: Bill could not be saved. Reason:
The INSERT statement conflicted with the CHECK constraint "POSBillItem_C08"
  1. .
The conflict occurred in database "NPOS", table "dbo
  1. .
POSBillItem"
  1. .
Cannot insert the value NULL into column 'POSBillItemId', table 'NPOS.dbo.POSBillItemTrack'; column does not allow nulls. INSERT fails.
  1. The statement has been terminated.
The statement has been terminated.3
  1.  
216087N.A.
16087 User can't do settlement when POS Bill permission is not given

16087 Cannot do POS bill settlements if the user does not have POS bill access permission

Module:

POS - Normal POS - Back Office - Transactions - Settlement

Reported Version:

1.145.2       

   40216

  

Scenario:

  1. Create a Terminal for Collection Center.
  2. Create a User with Collection Centre access
(Do
  1. but do not give POS Bill access
)
  1. to the user.
  2. Now, login with that User
& go to
  1. .
  2. Go to POS > Normal POS > Back Office > Transactions > Settlement.
  3. Observe that, the User is unable to do Settlement.
4
316074N.A.

16074 Loyalty Point not showing

in

on POS Bill

Module:

POS - Normal POS - POS Bill

Reported Version:

1.145.1     

   39617

  

Scenario:

  1. Go to POS > Normal POS > POS Bill.
  2. Create a POS bill.
  3. Print the bill.
  4. Observe that, loyalty point information is not showing in the bill.
5
416008N.A.

16008 POS Bill

can not be Saved: There is a previous call to generate document number under scheme '

cannot be saved. It is showing that POS Bill Cash Memo

'

is still in progress.

Cannot

User cannot proceed

.

further

Module:

POS - Normal POS -POS Bill

Reported Version:

1.145.3         

   39030

  

Scenario:

  1. Go to POS - Normal POS -POS Bill
  2. Try to save the POS bill.
  3. Observe that,
PPS
  1. POS bill can not be Saved.
A previous call to generate document number under scheme '
  1. It is showing that POS Bill Cash Memo
'
  1. is still in progress.
Cannot
  1. User cannot proceed
.
  1. further
6
516055N.A

16055 The INSERT statement conflicted with the FOREIGN KEY constraint "POSStlmDetail_R02"... - Error message is showing while settling at POS

Module:

POS - Normal POS - Back Office - Transaction - Settlement

Reported Version:

1.145.

145 

           

 40196

Scenario:

  1. Go to POS - Normal POS - Back Office - Transaction - Settlement.
  2. Try to settle any POS transaction.
  3. Observe that, the following error message is showing: The INSERT statement conflicted with the FOREIGN KEY constraint "POSStlmDetail_R02". The conflict occurred in database "NPOS", table "dbo.MOP", column 'MOPId'.The statement has been terminated while saving settlement
- error message is showing while settling at POS7
  1. .
6

16092

N.A

16092

After allowing

The customer cannot be updated despite the Site Policy - 'Allow to add customer in POS bill modification after settlement'

, the customer is not getting updated

Module:

POS - Normal POS - Back Office - Transaction - Settlement

Reported Version:

1.145.3       

   40149

  

Scenario:

Allow
  1. Enable the Site Policy 'Allow to add customer in POS bill modification after settlement' from HO.
  2. Go to POS > Normal POS > Back Office > Transaction > Settlement.
  3. Settle for that day.
  4. Now select any POS Bill which is part of that settlement and try to update the customer.
  5. Observe that, the customer is not getting updated
8
716158N.A

16158 Automatic data sync running after the scheduling time end

Module:

POS - Data Sync

Reported Version:

1.145.3     

   40506

  

Scenario:

  1. Suppose, Auto Sync schedule has been set
to
  1. in every 15 minutes between 08:00 a.m. to
08
  1. 09:
15
  1. 00 p.m.
  2. Observe that, sync is still running after
08
  1. 09:
15
  1. 00  p.m.
9
816266N.A

16266 System.Net.WebException: The operation has timed out  - Error message is showing while sending SMS

at the time of

after POS billing and Settlements 

Module:

POS - Normal POS - POS Bill

POS - Normal POS - Back Office - Transaction - Settlement

Reported Version:

1.145.3           

  39151

Scenario:

Observe that, System.Net.WebException: The operation has timed out  - Error message is showing while sending SMS at the time of POS billing and Settlements 1010278N.A

10278 After replacing the MASTER Database files, all other System Databases are using files from Template Data instead of DATA folder

Module:

Normal POS

Reported Version:

1.141.1

Scenario:

Observe that, after replacing the MASTER Database files, all other System Databases are using files from Template Data instead of DATA folder

1116529N.A

16529 GlobalPOSBillCNId column in POSBillCN table is saving with null/empty string if POS Bill is saving with credit note and showing an error - ORA-01400: cannot insert NULL into ("MDRL"."PSITE_POSBILLCN"."CODE")...

Module:

Ginesys POS - Normal POS - POS Bill

Reported Version:

1.145.4               41200

Scenario:

GlobalPOSBillCNId column in POSBillCN table is saving with null/empty string if POS Bill is saving with credit note. Observe that, an error message is showing - ORA-01400: cannot insert NULL into ("MDRL"."PSITE_POSBILLCN"."CODE") ORA-06512: at "MDRL.P_PSITE_POSBILLCNI_BULK_INS", line 28 ORA-06512: at "MDRL.P_POSBILL_MERGE", line 10 ORA-06512: at line 1"
  1. Go to POS > Normal POS > POS Bill and POS > Normal POS > Back Office > Transaction > Settlement.
  2. Send SMS after POS billing and Settlements 
  3. Observe that the following error message is showing : System.Net.WebException: The operation has timed out.