Subject: | Improvement to Replication diagnostics utilities |
Summary: | We need the ability to easily identify data mismatch between branch and head office. to achieve this, we need the following improvements: - Create a utility that can be run at a branch level that lists master file that is missing (Missing in HQ/ Missing in Branch/Mismatch Data Values)
- Create a utility that can be run at a branch level that lists transactions that are missing (Missing in HQ/ Missing in Branch/Mismatch Data Values)
The next step will be to use this information to PUSH/PULL data between two entities. (Version 2) - Use XXXXX issue on case 6401 to build the PUSH/PULL mechanism. |
Audit Notes: | |
04 Jul 2017 | 11:44AM Comment 1 by Sanjay (Link Technologies) Case 8650 added to project 8.14 |
12 Jul 2017 | 05:16PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 12-07-2017 05:16 PM Time Taken: 16.00 |
| Development work for this case has been completed. The change will be available in version: 8.14 Documentation update required(Yes/No. Add change details below): Yes QA required(Yes/No.Include areas that require testing): Yes
The following changes were made(Include Database object names, Program classes and any other relevant information):| - Created a new menu in POS WEB ~> Replication ~> Compare Data
- Created a process for "POS Replication Compare Data Process". By default this process is disabled.
Documentation details: - Use the "Compare Data" menu in the branch only.
- Data is compared with branch database and HQ database. Results are displayed as either "Additional", "Missing" or "Different"
- Replication rules enabled in HQ will filter the results in the "Missing" section.
To create a "Compare Data" batch, follow these steps: - Create a new batch in "POS WEB ~> Replication ~> Compare Data". See figure 1 below.
- Enable the process "POS Replication Compare Data Process". This process should be scheduled to run every minute on a separate schedule job name.
- The background process will process the batch created in 1. above and display entries that are a mismatch between the branch and head office databases.
- Click on the "View" link to view the mismatch entries. See figure 2 below.
- Mismatch entries can be queued to replication by the table name or by the detail line. See figure 3 below.
- Once the data is queued for replication, the normal replication process will process the records.
Figure 1: Compare Data batch
Figure 2: View link for mismatch entries
Figure 3: Send entries to replication queue
|
|
15 Jul 2017 | 02:19PM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 15-07-2017 02:19 PM Time Taken: 1.00 |
| Hi Alvis, We worked to create the test plan. Test Plan link However, we were unable to test the case. The batch was not completed because the process was disabled. Refer to figure 1. Only 3/104 comparison was made and the process stopped. Setup in QA1 with database LINKSOFTBRANCH1. .Figure 1: Error Log
|
|
17 Jul 2017 | 09:56AM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 17-07-2017 09:56 AM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 8.14 Beta 2 Documentation update required(Yes/No. Add change details below): QA required(Yes/No.Include areas that require testing): Yes
1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Corrected the error on comparing data. This was caused by the syntax script for "Send purchase order to branch" rule.
|
|
17 Jul 2017 | 06:19PM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 17-07-2017 06:19 PM Time Taken: 1.00 |
| Hi Alvis, Based on the test plan in comment 3. The following has been tested with 814 Beta 2. Environment in QA1 and QA4 - HQ - LINKSOFTHQ.
- Branch1 - LINKSOFTBRANCH1
- Branch2 - LINKSOFTBRANCH2 - QA4
In addition, investigate the different in LB_POS_PaymentLines where void date is populated at HQ. Transaction ID - B1RC0000000002 Regards Rashna |
|
18 Jul 2017 | 08:42AM Comment 6 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 18-07-2017 08:42 AM Time Taken: 2.00 |
| Hi Rashna, I have checked the replication setup and found that rules enabled in HQ prevent data from being transmitted from HQ to branch. For the payment lines issue, I have corrected the data transmission script so that NULL dates are sent as NULL as suppose to '1900-01-01'. Updates are in beta3 build. regards Alvis
|
|
18 Jul 2017 | 05:13PM Comment 7 by Vineet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 18-07-2017 05:13 PM Time Taken: 4.00 |
| Bula Team I have tested the below areas today: - Missing POS Transactions not replicated from HQ to Branch. A improvement to replication rules case has been logged: Refer to case 8686
- Adjustment created at HQ and Brach. Mismatched these from both sides. Sent updates from HQ to branch and compared data. (Pass)
- Created Transfer from Branch. Created a mismatch in transaction and value of transaction at HQ. Resent updated from branch. (Pass)
- Created a PO at Branch and received at HQ. Mismatched details of PO at HQ and resent updates from branch. (Pass)
- Created Stock take at Branch. Once update was sent to HQ, mismatched at Branch and resent updates from HQ to branch. (Pass)
Best Regards Vineet Ram Consulting Manager +679 7770085
|
|
19 Jul 2017 | 01:06PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 19-07-2017 01:06 PM Time Taken: 1.00 |
| Documentation completed on the case. Documentation updated at POS-Web-- Point of Sale -- Compare Data |
|