Subject: | POS Application time-out when group by POSCASH is enabled |
Summary: | 1. Problem Details
POS Application time-out when grouped by POSCASH (POS.POSCASH.ACCOUNTCODE) is enabled to "Month"
2. Error Message (screenshot of the error)
Log Message: TransactionID: LBTX0000700194 was not created. Error Message: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
3. Environment Details Version - 14.90.230621.GA
|
Audit Notes: | Edited by sanjay on 07/08/23 16:11. Edited by sanjay on 07/08/23 16:08. Edited by sanjay on 07/08/23 15:47. Edited by sanjay on 07/08/23 15:33. Edited by sanjay on 24/07/23 19:26. |
24 Jul 2023 | 01:30PM Comment 1 by Sanjay (Link Technologies) Case L12929 added to project 15.00 |
24 Jul 2023 | 06:22PM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-07-2023 07:58 PM Time Taken: 6.00 Notes: ETC extended from: 24/07/2023 to 25/07/2023 |
| Hi Vineshwar, Laucala Bay Pharmacy issue is because they have 95,000 customers and the Customer table is defragmented to 98.8 %
Once we defragment the index, the new record will be created fairly quicky Figure 1 - Customer Table fragmentation
|
|
24 Jul 2023 | 07:26PM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 25-07-2023 09:23 PM Time Taken: 12.00 Notes: ETC extended from: 25/07/2023 to 25/07/2023 |
| PART A - Development work for this case has been completed. 1. The change will be available in versions: 15.00 and 14.90.2307 2. The following changes were made(Include Database object names, Program classes, and any other relevant information): - Changed logic to use FMISSQLAPI only if it is enabled
- Modified Integration synchronisation only if FMISSQLAPI is enabled
3. Affected Areas: - Using POSCASH with Suffix creates an issue if FMIS SQL API is not enabled.
4. The issue was caused by: - Design flaw
5. Other Relevant Notes: 6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT PART B - Development Reference (Place descriptor for objects changed): Applied to Laucala Bay Pharmacy environment for testing. Reindexing also completed on this DB.
|
|
07 Aug 2023 | 03:33PM Comment 4 by Sanjay (Link Technologies) Case L12929 added to project 14.90 |
07 Aug 2023 | 03:47PM Comment 5 by Sanjay (Link Technologies) ETC was changed from 25/07/2023 to 18/08/2023 |
08 Aug 2023 | 09:01AM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-08-2023 10:59 AM Time Taken: 12.00 Notes: ETC extended from: 18/08/2023 to 09/08/2023 |
| PART A - Development work for this case has been completed. 1. The change will be available in version: 14.9.0810 2. The following changes were made(Include Database object names, Program classes, and any other relevant information): - Before POS Transactions are transferred to FMIS, we check if there are any Masterfile records that need to be transferred. If there are, we initiate the MasterFile Process so that Transactions do not FAIL validation.
3. Affected Areas: - FMIS Integration of POS transactions
4. The issue was caused by: - Improvement
5. Other Relevant Notes: 6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation):UAT |
|
08 Aug 2023 | 09:02AM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-08-2023 11:01 AM Time Taken: 6.00 Notes: ETC extended from: 09/08/2023 to 09/08/2023 |
|
The following tests were performed:
Test Setup Instructions:
Table 1 - Test Results
No | Test Case | Expected Result | Pass/Fail | Comments | 1 | Create a new customer and Process a sale for this customer. The Validation for the FMIS transaction should not fail as the new customer will be sent before the Sale transaction is sent.
|
| Pass
|
| Environment Details - OS version: Win11
- Application version: 14.90.230810
- Setup on:
- Server: LinkQA4
- Database: LinkSOFT
- LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
- Login Details: Standard username and password for user "admin"
Next Step: Closure
|
|