Details
-
Type:
Bug
-
Status:
Cancelled
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: Financial
-
Labels:None Labels
-
Customer:Zain Jordan
Description
Customer has reported duplicate Asset name with different serial number issue.
Attachments
Activity
-
- Time Spent:
- 2 hours
-
Issue check and raised with L3 team
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2026-02-12 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2026-02-12 24:00 (milestone: set planned end date to due date) |
| Assignee | Khaled Khalil [ kkhalil ] | Daljeet Singh Virdi [ dsvirdi ] |
| Attachment | duplicate assset name with different sn.png [ 127900 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 2 hours [ 7200 ] | |
| Worklog Id | 291109 [ 291109 ] |
| Baseline Start | 2026-02-12 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2026-02-12 24:00 (set baseline based of initial work logging) |
| Component/s | NEP [ 16200 ] |
| Time Spent | 2 hours [ 7200 ] | 4 hours [ 14400 ] |
| Worklog Id | 291226 [ 291226 ] |
Dear Daljeet,
These two board are related to different node types (eNodeB and RAN BS), and in general this can be acceptable.
However, in this specific case we are getting Role4G and eNodeB with the same name(52954-ULN-Naaimeh-North-PE-TASC-O).
Kindly check the XML to confirm whether this information is valid, as we should not have Role4G and eNodeB defined with the same name.
Show
Bessem Manita
added a comment - Dear Daljeet,
These two board are related to different node types (eNodeB and RAN BS), and in general this can be acceptable.
However, in this specific case we are getting Role4G and eNodeB with the same name(52954-ULN-Naaimeh-North-PE-TASC-O).
Kindly check the XML to confirm whether this information is valid, as we should not have Role4G and eNodeB defined with the same name.
| Attachment | d0fb4212-2430-4cbd-a739-2486170b0f4e.png [ 128211 ] |
-
- Time Spent:
- 1 hour
-
Issue checked and respond to customer that it is not an issue
Issue fixed after new AI patch
Show
Daljeet Singh Virdi
added a comment - Issue fixed after new AI patch
| Status | Open Bug [ 10108 ] | Cancelled [ 10013 ] |
| Resolution | Fixed [ 1 ] |
| Time Spent | 4 hours [ 14400 ] | 5 hours [ 18000 ] |
| Worklog Id | 293669 [ 293669 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
16d 6h 38m | 1 | Daljeet Singh Virdi | 26/Feb/26 10:45 AM |
|
Links Hierarchy |
 Documentation
|
L3 anaylsis by Bessem:
These two board are related to different node types (eNodeB and RAN BS), and in general this can be acceptable.
However, in this specific case we are getting Role4G and eNodeB with the same name(52954-ULN-Naaimeh-North-PE-TASC-O).
Kindly check the XML to confirm whether this information is valid, as we should not have Role4G and eNodeB defined with the same name.