Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: None
-
Customer:Ooreedo Tunisia
Description
Dear @Khaled Khalil,
Could you please assign a NEP-DEV resource to check & fix below issue:
We need to add a header in cabinet/shelf/board report on platform .102 for “Ooredoo Tunisia” like it was available in ZAIN-KSA for duplicate serial numbers in dump, below is ZAIN KSA snippet for reference:
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Hi Indrasan,
The issue has been resolved.
we added a new patch Number : 3.7.0.1326
Best Regards
Nouha
The fix is available in the patch 3.7.0.1326
Dear @Basant Kumar,
Please deploy the below NEP patch on .102 platform.
The fix is available in the patch 3.7.0.1326
Thank you
Indrasan
Dear Team,
Patch 3.7.0.1326 has been successfully deployed on the .102 server, and all database queries have been executed. However, we are encountering errors in some queries.
I am attaching the highlighted screenshots for your reference.
Regards,
Basant
Dear @Nouha Mhadhbi,
Did you check the highlighted error during queries execution as shared by integration team @Basant Kumar.
Note: Requested header is appearing now in cabinet/shelf report but still missing in board report.
I checked the data in NEP after patch deployed, but there is an issue, I am sharing below snippet for your reference:
1- Under cabinet report from where below highlighted data is coming as this is not available in dump/xml?
2- Under shelf report manufacturer is missing for highlighted one and from where below highlighted data is coming against this shelf type “RRU” as this is not available in dump/xml?
3- Under board report highlighted data is appearing from where? And you can see in below snippet the value of column is shifted towards right from corrected one column
You can see in below snippet the value of “board type” is shifted in column “merged board”.
Note: require snaps are attaching here with today date.
Thank you
Indrasan
dear Indrasan,
All identified issues have been resolved. Patch 3.7.0.1330 has been successfully deployed for this ticket. For your information, the script below has been applied to the Ooredoo database. Kindly proceed with restarting your server.
Best,regards
Nouha
Dear @Nouha Mhadhbi,
Please review the following regarding the headers “Board Serial Number” and “Board Dump Serial Number.” (Board report snippet is attached for your reference)
If both fields contain the same serial number, what is the purpose of having both? In such cases, we could retain only one of them.
As per my understanding:
• The header “Board Serial Number” contains the first (i.e., unique) serial number.
• If the same serial number appears again in another instance—whether for a cabinet, shelf, or board—it is then placed under the header “Board Dump Serial Number.”
This same rule is already applied in ZAIN-KSA, as I explained at the start of this email trail for your reference.
Thank you
Indrasan
Dear Indrasan,
Diana implemented the addition of Dump Serial Number with ZAIN KSA, and as she explained to Nouha, Dump Serial Number will be a copy of Serial Number, and this what Nouha implemented. I am not sure why we need both to be the same, but it is not a personal openion or view, we need to known exactly what the customer want us to do, so we get that approved by @Hassan Abdine and then we can implement it.
Regards,
Khaled Khalil
Dear @Khaled Khalil,
The serial numbers available in the dump are being parsed as they are—whether unique or duplicate for cabinet/shelf/board. However, when importing into NEP, only unique serial numbers are imported, and duplicates are ignored.
Since our requirement is to retain all serial numbers in NEP, we need to maintain both headers as we did in ZAIN-KSA:
• Serial Number → for unique serial numbers (imported as the primary entry).
• Dump Serial Number → for duplicate serial numbers (imported as secondary entries for cabinet/shelf/board).
This ensures that both unique and duplicate serial numbers are captured in NEP as per dump.
Thank you
Indrasan
This JIRA has now been reassigned to me by the NEP DEV team. However, since the requested header is now available, the JIRA can be closed. It appears the reassignment was done based on header availability, without confirmation on the concerns I had raised.
I am closing this JIRA now and will create a new JIRA to address the issue related to the correct values being displayed under this new header.
Dear All,
Any update on this?
Thank you
Indrasan