http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-384 L3 Support <p>Customer has raised issue for the attached nodes SN present in the Unmapped and FR as well.<br/> After did analysis , it has been observed that the asset first Financialised under Active Inventory later it got decommissioned and again inserted via Generic Connector with same SN but sync didn't work and result in two different records present in both Unmapped and Financial Report with same SN.</p> <p>Kindly check and do rectify the same. </p> LS-384

Zain KW | Sync issue observed between Unmapped and FR | MOB-7319

Bug Normal Closed Fixed Abir Messaikeh Daljeet Singh Virdi Thu, 15 May 2025 08:54:19 +0300 Mon, 2 Feb 2026 03:49:42 +0200 Mon, 8 Dec 2025 08:11:50 +0200 Financial Tue, 20 May 2025 00:00:00 +0300 0 2 0 minutes 1 week, 4 days, 6 hours, 40 minutes <p>Dear @Wajdi Jomaa,</p> <p>As discussed over chat that there are still some unsolved duplicates which are not reported by customer but exist in the network.<br/> Could you pl provide me the ETA ,as I need to share update on this ticket with customer.</p> <p>General preview of work related to this issue:</p> <ul class="alternate" type="square"> <li>Financial records with serial numbers were stored in nep_history_reference table with status is_decomissioned false, even if the asset having the serial number no longer exists, we fixed this issue by changing the status of is_decomissioned to true for all financial records</li> </ul> <ul class="alternate" type="square"> <li>Changing Object id of a network element will lead to duplicates in history (one with old name, one with new name) same for physical configuration applied to this element, we fixed this issue in code, + cleanup scrip to clean records with old names</li> </ul> <ul class="alternate" type="square"> <li>if we have 2 network element of different types with same object id, physical configuration for both elements will have the same name in history we fixed this issue by adding an infix to physical configuration in history that specifies the type of network element (scripts + code) for example : "Cabinet_IDU_objecitd/c1_version"</li> </ul> <ul class="alternate" type="square"> <li>Clean data in unmapped report with cleanup scripts then add serial number to passive nodes + sync process to fix data</li> </ul> <p>patch needed: 3.7.1.688 + upgrade directly to 3.7.1.689</p> <p>Tested Fine on Test platform,Patch deployement pending on prod , later will ask customer for the closure</p> Relates Actual Start Wed, 4 Jun 2025 00:00:00 +0300 Baseline End Tue, 20 May 2025 00:00:00 +0300 Baseline Start Tue, 20 May 2025 00:00:00 +0300 Customer Date of Baselining Fri, 6 Jun 2025 13:17:00 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Tue, 20 May 2025 00:00:00 +0300 Planned Start Tue, 20 May 2025 00:00:00 +0300 Rank 0|xtimkx: Rank (Obsolete) 9223372036854775807 VTDirections