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-438 L3 Support <p>Dear @Khaled Khalil,</p> <p>Please assign NEP DEV resource to check why operator is not importing in <br/> NEP under report eNodeB, while it is available in XML.</p> <p>XML Import: 2025-06-04-11.48.54_Ooredoo_Tunisia (xml attached here)<br/> Platform: Ooredoo Test .102<br/> XML Import Date: 11-06-2025</p> <p>XML Snippet: attached here.</p> <p>NEP Snippet: attached here.</p> <p>And there is no relevant error in an error report related to this.</p> <p>Thank you<br/> Indrasan</p> LS-438

Operator detail is not importing in NEP under report eNodeB_Huawei

Bug Normal Closed Fixed Indrasan Yadav Indrasan Yadav AI_All_incidents Huawei_RAN_OO Fri, 13 Jun 2025 05:40:38 +0300 Mon, 13 Oct 2025 11:21:19 +0300 Wed, 25 Jun 2025 08:18:13 +0300 Fri, 20 Jun 2025 00:00:00 +0300 0 2 0 minutes 6 hours, 30 minutes <p>Dear @Indrasan Yadav, </p> <p>The operator is not appearing in the NEP under the eNodeB report because the operator must be imported before importing the XML file. </p> <ul class="alternate" type="square"> <li>Import Operator using a CSV file:<br/> - Import the XML file </li> </ul> <p>Regards,<br/> Mustapha</p> <p>Dear @Mustapha Al-Hage,</p> <p>As discussed during our Teams call, I attempted to import operator details via CSV multiple times using the input data where the color was set to yellow. However, an error message appeared indicating that the same color already exists. I demonstrated this issue to you during the call.<br/> Subsequently, I changed the color to blue and orange, but the same error persisted. I then left the color field blank, but another error was shown stating that the color cannot be blank.</p> <p>Finally, I used the value “0_102_255”, which you shared as a reference from OmanTel. This time, the import was successful. I then imported the corresponding XML, and the data is now correctly appearing under the “eNodeB” report.</p> <p>Conclusion:<br/> The issue has been resolved successfully.</p> <p>Thank you<br/> Indrasan</p> Actual Start Wed, 11 Jun 2025 00:00:00 +0300 Baseline End Fri, 20 Jun 2025 00:00:00 +0300 Baseline Start Fri, 20 Jun 2025 00:00:00 +0300 Customer Date of Baselining Tue, 17 Jun 2025 04:47:31 +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 Fri, 20 Jun 2025 00:00:00 +0300 Planned Start Fri, 20 Jun 2025 00:00:00 +0300 Rank 0|xtinep: Rank (Obsolete) 9223372036854775807 VTDirections