Subject: | Validate the character length for "Next Numbers" in "New Database". |
Summary: | Hi Alvis,
In customer case 9260, we stated that the POS transaction was failing because the "Transaction Number" had 14 characters and the allowed characters in the system is only 12. I did a select in the "New Database" for version 10.1.3.2. Next Numbers are more than 12 characters by default. Can we please correct this: - Consultants do not alter the next numbers on site.
- Next Number is only updated by replication.
- Cases have been reported that the transactions are failing.
Below is the analysis.
flag | value_str | Length |
next_prescr_no | LTPR000000001 | 13 |
next_redeem_no | LTRE000001 | 10 |
next_return_no | LTRT000000001 | 13 |
next_shift_no | LTSH000000001 | 13 |
NextCustomerNumber | LTCU:000001 | 11 |
NextDoctorNumber | D0001 | 5 |
NextEFTReferenceNumber | EFAA0000000001 | 14 |
NextNonPrescriptionLabelNumber | LTNP0000000001 | 14 |
pos_next_accpay_no | LTAP000000001 | 13 |
pos_next_adj_no | LTAJ000000001 | 13 |
pos_next_batch_no | LTBT000000001 | 13 |
pos_next_creditnote_no | CNLT0000000001 | 14 |
pos_next_deposit_no | LTDP000000001 | 13 |
pos_next_payment_adj_no | PADJ0000000001 | 14 |
pos_next_quote_no | LTQU000000001 | 13 |
pos_next_receipt_no | LTRC000000001 | 13 |
pos_next_trans_no | LTTX000000001 | 13 |
POS_next_Wholesale_No | WHSL0000000001 | 14 |
pos_next_wholesale_return_no | WLRT0000000001 | 14 |
POS_Wholesale_MachineNames | | 0 |
Thanks Rashna |
Audit Notes: | Edited by rashna on 08/12/20 09:45. Edited by sanjay on 05/03/19 10:38. |
05 Dec 2018 | 08:49AM Comment 1 by Rashna (Edge Business Solutions) Case 9740 added to project 10.2 |
07 Dec 2018 | 02:58PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 07-12-2018 02:58 PM Time Taken: 1.00 |
| Development work for this case has been completed. The change will be available in version: 10.2 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Changed the "New" build data to have next numbers 10 characters long.
2. The issue was caused by: - inconsistent next number length
3. Next Step - UAT
|
|
10 Dec 2018 | 08:45AM Comment 3 by Alvis (Link Technologies) Case 9740 removed from project 10.2 |
10 Dec 2018 | 08:45AM Comment 4 by Alvis (Link Technologies) Case 9740 added to project 10.1 |
11 Dec 2018 | 11:34AM Comment 5 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 11-12-2018 11:34 AM Time Taken: 1.00 |
| The following change has been made in version 10.1.3.4: - Master file next number has the format: <2 digit company prefix><2 digit record prefix><5 digit number>
- Transaction next number has the format: <2 digit company prefix><2 digit record prefix><7 digit number>
System test completed. Proceed with UAT. |
|
11 Dec 2018 | 02:46PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 11-12-2018 02:46 PM Time Taken: 1.00 |
| Hi Sanjay QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues No | Test Description | Pass/Fail | 1 | Validate the next numbers are as per comment 5 | Pass |
Figure 1: Next Numbers
next_prescr_no | LTPR0000001 | 11 | next_redeem_no | LTRM0000001 | 11 | next_return_no | LTRT0000001 | 11 | next_shift_no | LTSH0000001 | 11 | NextCustomerNumber | LTCU:00001 | 10 | NextDoctorNumber | LTDC00001 | 9 | NextEFTReferenceNumber | LTEF0000001 | 11 | NextNonPrescriptionLabelNumber | LTNP0000001 | 11 | pos_next_accpay_no | LTAP0000001 | 11 | pos_next_adj_no | LTAJ0000001 | 11 | pos_next_batch_no | LTBT0000001 | 11 | pos_next_creditnote_no | LTCN0000001 | 11 | pos_next_deposit_no | LTDP0000001 | 11 | pos_next_payment_adj_no | LTPJ0000001 | 11 | pos_next_quote_no | LTQU0000001 | 11 | pos_next_receipt_no | LTRC0000001 | 11 | pos_next_trans_no | LTTX0000001 | 11 | POS_next_Wholesale_No | LTWS0000001 | 11 | pos_next_wholesale_return_no | LTWR0000001 | 11 |
Environment Details - OS version: Windows Server 2012
- Application version: 10.1.3.5
- Setup: Demo
- Server : 10.0.0.14
- Database: RASHNA-LINKSOFT-NEW-10
Steps to reproduce failed scenarios: N/A Next Step: for closure
|
|
17 Dec 2018 | 08:18AM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 17-12-2018 08:18 AM |
| Thanks Rashna |
|
09 Oct 2019 | 08:14AM Comment 8 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |
08 Dec 2020 | 09:45AM Comment 9 by Rashna (Edge Business Solutions) ETC was changed from 06/12/2018 to 06/12/2018 |