| Subject: | Issues with Client data comparison | | Summary: | Hi Sanjay, We have setup data comparison with Version 816 Beta 1. Database are on QA4. Refer to Batch 2017-08-03T083620. for deatils - HQ - CLIENT-LINKSOFT-HQ
- BRANCH - CLIENT-LINKSOFT-BRANCH
| Number | Issue | Resolved | | 1 | Data comparison for "POS Trasanctions" take almost 2 and half hours. Started 8.36am end at 11.21am.
| | | 2 | Viewing "Additional", "Missing" and "Different" data is very slow. Page keeps on loading . Use table "LBS_POS_Order" as an example. | | | 3 | There are 6883 different records in "LBS_POS_OrderDetail" where unit cost is different. We are not able to receive the unit cost from HQ because of rule R1080. Case 8686 is already logged, we need to allow sales to through for configured locations. Review transaction - SRTX0000011150 in "LT_REPL_DATA_HIST" at HQ | | | 4 | For "Transaction ID - SRTX0000439075", HQ has 2 lines in "LBS_POS_OrderDetail" , however the BRANCH has only 1 line of record. This was "NOT" picked as missing in the comparison. 
| | | 5 | There are transactions in the "LBS_POS_Order" which have compared last save date. Refer to "Transactions - "SRTX0000842792", "HQTX0000000020", "HQTX0000000021", "HQTX0000000022".There are 1,047,392 records of difefrences. | | | 6 | LBS_POS_Payment has 2196 records out of which only 65 records is for location "SUV03".The "LT_POS_UTILITY_ClearNonLocationData" did not remove allocated cash payments | |
| | Audit Notes: | | | 03 Aug 2017 | 06:12PM Comment 1 by Alvis (Link Technologies) Case 8728 added to project 8.16 | | 03 Aug 2017 | 06:21PM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 03-08-2017 06:21 PM Time Taken: 4.00 | | Hi Rashna We have done the following: - Data comparison will take this long due to a large number of transactions. This time is affected by changes to item 3,4,5,6 below.
- Detail list will now show 1000 records. once these 1000 has been resolved, the system will show the next 1000.
- We have changed rule 1080 to handle configured locations.
- Missing transactions will show as a result of changes in item 3.
- LastSavedDateTime field is now ignored in all data comparisons.
- This issue has been resolved in case 8730.
regards
Alvis |
| | 11 Aug 2017 | 08:37AM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 11-08-2017 08:37 AM Time Taken: 1.00 | | Hi Team, Issues mention has been resolved | umber | Issue | Results | | 1 | Data comparison for "POS Trasanctions" take almost 2 and half hours. Started 8.36am end at 11.21am.
| All transactions for OTGL was compared in 2 hours. | | 2 | Viewing "Additional", "Missing" and "Different" data is very slow. Page keeps on loading . Use table "LBS_POS_Order" as an example. | Resolved in case 8723 | | 3 | There are 6883 different records in "LBS_POS_OrderDetail" where unit cost is different. We are not able to receive the unit cost from HQ because of rule R1080. Case 8686 is already logged, we need to allow sales to through for configured locations. Review transaction - SRTX0000011150 in "LT_REPL_DATA_HIST" at HQ | Resolved case 8735 | | 4 | For "Transaction ID - SRTX0000439075", HQ has 2 lines in "LBS_POS_OrderDetail" , however the BRANCH has only 1 line of record. This was "NOT" picked as missing in the comparison.  
| Resolved as rule 1080 had been modified to include exception for other locations | | 5 | There are transactions in the "LBS_POS_Order" which have compared last save date. Refer to "Transactions - "SRTX0000842792", "HQTX0000000020", "HQTX0000000021", "HQTX0000000022".There are 1,047,392 records of difefrences. | Resolved | | 6 | LBS_POS_Payment has 2196 records out of which only 65 records is for location "SUV03".The "LT_POS_UTILITY_ClearNonLocationData" did not remove allocated cash payments | Resolved in case 8730 |
This case is now closed |
| | 11 Aug 2017 | 08:39AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 11-08-2017 08:39 AM Time Taken: 1.00 | | Hi Team, Issues mention has been resolved | umber | Issue | Results | | 1 | Data comparison for "POS Trasanctions" take almost 2 and half hours. Started 8.36am end at 11.21am.
| All transactions for OTGL was compared in 2 hours. | | 2 | Viewing "Additional", "Missing" and "Different" data is very slow. Page keeps on loading . Use table "LBS_POS_Order" as an example. | Resolved in case 8723 | | 3 | There are 6883 different records in "LBS_POS_OrderDetail" where unit cost is different. We are not able to receive the unit cost from HQ because of rule R1080. Case 8686 is already logged, we need to allow sales to through for configured locations. Review transaction - SRTX0000011150 in "LT_REPL_DATA_HIST" at HQ | Resolved case 8735 | | 4 | For "Transaction ID - SRTX0000439075", HQ has 2 lines in "LBS_POS_OrderDetail" , however the BRANCH has only 1 line of record. This was "NOT" picked as missing in the comparison.
| Resolved as rule 1080 had been modified to include exception for other locations | | 5 | There are transactions in the "LBS_POS_Order" which have compared last save date. Refer to "Transactions - "SRTX0000842792", "HQTX0000000020", "HQTX0000000021", "HQTX0000000022".There are 1,047,392 records of difefrences. | Resolved | | 6 | LBS_POS_Payment has 2196 records out of which only 65 records is for location "SUV03".The "LT_POS_UTILITY_ClearNonLocationData" did not remove allocated cash payments | Resolved in case 8730 |
This case is now closed |
| | 09 Oct 2019 | 08:14AM Comment 5 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 |
|