Bug #169
closed
- Description updated (diff)
- Assignee changed from Renu Sharma to Kunal Chaudhary
- Status changed from New to Resolved
- Assignee changed from Kunal Chaudhary to Amit Kumar
- Deliverable changed from ADMIN WEB to BACKEND API
change in sp and add sim name logic
RCA -
Earlier, the SIM Provider was fetched using the SimCard + ValueType join.
When the join failed, it returned NULL, so the UI showed a blank value.
After implementing the MCC–MNC based CASE logic, the ELSE 'UNKNOWN' condition caused “UNKNOWN” to appear instead of blank.
Resolution -
The SIM Provider logic was updated to derive the operator name from the MCC and MNC columns in TMS_DeviceHeartBeat.
Leading zero and spacing scenarios were handled properly.
Now, valid MCC–MNC combinations return the correct SIM Provider, and unmatched cases maintain the expected behavior.
@Kunal Chaudhary validate this issue in UAT env and found this fix is done only for one screen that is for Device monitoring page weather it has be fixed on device detail as well. Hence status of the ticket held Re-opened as of now

- Status changed from Resolved to Re-Opened
- Assignee changed from Amit Kumar to Kunal Chaudhary
- Status changed from Re-Opened to Resolved
- Assignee changed from Kunal Chaudhary to Harshith Jay
Change:
Added SimProvider logic in uspGetDeviceDetailList stored procedure.
RCA:
SimProvider calculation logic did not exist in this stored procedure earlier, due to which provider value was not being returned.
The issue which was raised is resolved and validated in latest deployed UAT release.

Also available in: Atom
PDF