[LS-384] Zain KW | Sync issue observed between Unmapped and FR | MOB-7319 Created: 15/May/25  Updated: 02/Feb/26  Due: 20/May/25  Resolved: 08/Dec/25

Status: Closed
Project: L3 Support
Component/s: Financial
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Daljeet Singh Virdi Assignee: Abir Messaikeh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 1 week, 4 days, 6 hours, 40 minutes
Original Estimate: Not Specified

Attachments: Microsoft Word Sync issue in Unmapped and FR.docx     Text File fixqueriesls384.txt    
Issue Links:
Relates
Customer:
Zain Kuwait
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

Customer has raised issue for the attached nodes SN present in the Unmapped and FR as well.
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.

Kindly check and do rectify the same.



 Comments   
Comment by Daljeet Singh Virdi [ 03/Jul/25 ]

Dear @Wajdi Jomaa,

As discussed over chat that there are still some unsolved duplicates which are not reported by customer but exist in the network.
Could you pl provide me the ETA ,as I need to share update on this ticket with customer.

Comment by Wajdi Jomaa [ 12/Aug/25 ]

General preview of work related to this issue:

  • 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
  • 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
  • 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"
  • Clean data in unmapped report with cleanup scripts then add serial number to passive nodes + sync process to fix data

patch needed: 3.7.1.688 + upgrade directly to 3.7.1.689

Comment by Daljeet Singh Virdi [ 10/Sep/25 ]

Tested Fine on Test platform,Patch deployement pending on prod , later will ask customer for the closure

Generated at Fri Apr 17 09:37:37 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.