[LS-438] Operator detail is not importing in NEP under report eNodeB_Huawei Created: 13/Jun/25  Updated: 13/Oct/25  Due: 20/Jun/25  Resolved: 25/Jun/25

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

Type: Bug Priority: Normal
Reporter: Indrasan Yadav Assignee: Indrasan Yadav
Resolution: Fixed Votes: 0
Labels: AI_All_incidents, Huawei_RAN_OO
Remaining Estimate: 0 minutes
Time Spent: 6 hours, 30 minutes
Original Estimate: Not Specified

Attachments: File OT-17_Updated.rar     PNG File Snippet-1.png     PNG File Snippet-2.png     PNG File Snippet-3.png     PNG File Snippet-4.png     PNG File XML Snippet.png     PNG File eNodeB CSV Snippet.png     PNG File eNodeB Report NEP Snippet.png     File server.log.2025-06-11    
Customer:
Ooreedo Tunisia
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

Dear @Khaled Khalil,

Please assign NEP DEV resource to check why operator is not importing in
NEP under report eNodeB, while it is available in XML.

XML Import: 2025-06-04-11.48.54_Ooredoo_Tunisia (xml attached here)
Platform: Ooredoo Test .102
XML Import Date: 11-06-2025

XML Snippet: attached here.

NEP Snippet: attached here.

And there is no relevant error in an error report related to this.

Thank you
Indrasan

 Comments   
Comment by Mustapha Al-Hage [ 23/Jun/25 ]

Dear @Indrasan Yadav,

The operator is not appearing in the NEP under the eNodeB report because the operator must be imported before importing the XML file.

  • Import Operator using a CSV file:
    - Import the XML file 

Regards,
Mustapha

Comment by Indrasan Yadav [ 25/Jun/25 ]

Dear @Mustapha Al-Hage,

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.
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.

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.

Conclusion:
The issue has been resolved successfully.

Thank you
Indrasan

Generated at Wed Apr 15 14:42:22 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.