Details

    • Customer:
      Zain Iraq

      Description

      It has been observed that the FR doesn’t sync with the Inventory report.

      The same TAG has different SN showing in Inventory and FR.
      Ideally the SN of inventory should get sync with the FR,

      Pl find attached doc with the snippet.

        Activity

        Daljeet Singh Virdi logged work - 04/Jan/26 12:00 AM
        • Time Spent:
          3 hours, 30 minutes
           

          Did complete analysis and raised issue with L3

        DSVirdi made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2026-01-08 24:00 (milestone: set planned start date to due date)
        Planned End 2026-01-08 24:00 (milestone: set planned end date to due date)
        Daljeet Singh Virdi made changes -
        Attachment Zain IQFr sync issue.docx [ 125401 ]
        Hide
        Abir Messaikeh added a comment -

        same as LS-849

        Show
        Abir Messaikeh added a comment - same as LS-849
        Hide
        Bessem Manita added a comment -

        Hi Daljeet,
        As discussed by teams, the passive node 20107082 was initially imported with a Serial Number (SN = '2121162778ESQ5001679').
        This asset was then financialized at the FR level, where the ItemBarcode was saved as both Tag and RFID.
        Then, the same passive node was imported again with a new Serial Number (SN ='ES2460056169').
        During the sync process, the new passive node was matched with the existing FR record based on the RFID, but the Serial Number now differs from what is saved in FR.
        Kindly advise how can we handle this scenario during FR sync?

        BR,
        Bessem

        Show
        Bessem Manita added a comment - Hi Daljeet, As discussed by teams, the passive node 20107082 was initially imported with a Serial Number (SN = '2121162778ESQ5001679'). This asset was then financialized at the FR level, where the ItemBarcode was saved as both Tag and RFID. Then, the same passive node was imported again with a new Serial Number (SN ='ES2460056169'). During the sync process, the new passive node was matched with the existing FR record based on the RFID, but the Serial Number now differs from what is saved in FR. Kindly advise how can we handle this scenario during FR sync? BR, Bessem
        Bessem Manita made changes -
        Status Open Bug [ 10108 ] Need More Info [ 10011 ]
        Assignee Khaled Khalil [ kkhalil ] Daljeet Singh Virdi [ dsvirdi ]
        Daljeet Singh Virdi made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 3 hours, 30 minutes [ 12600 ]
        Worklog Id 289153 [ 289153 ]
        DSVirdi made changes -
        Baseline Start 2026-01-08 24:00 (set baseline based of initial work logging)
        Baseline End 2026-01-08 24:00 (set baseline based of initial work logging)
        Hide
        Daljeet Singh Virdi added a comment -

        We can close this Ticket, as customer will proivde new logic to be implement under CR

        Show
        Daljeet Singh Virdi added a comment - We can close this Ticket, as customer will proivde new logic to be implement under CR
        Daljeet Singh Virdi made changes -
        Status Need More Info [ 10011 ] Open Bug [ 10108 ]
        Daljeet Singh Virdi made changes -
        Status Open Bug [ 10108 ] Cancelled [ 10013 ]
        Resolution Fixed [ 1 ]
        Daljeet Singh Virdi made changes -
        Resolution Fixed [ 1 ] Not Fixed [ 10200 ]
        Status Cancelled [ 10013 ] Reopened [ 4 ]
        Daljeet Singh Virdi made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Not Fixed [ 10200 ] Fixed [ 1 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Bug Open Bug Need More Info Need More Info
        6h 33m 1 Bessem Manita 05/Jan/26 10:52 AM
        Need More Info Need More Info Open Bug Open Bug
        21d 17h 22m 1 Daljeet Singh Virdi 27/Jan/26 4:15 AM
        Open Bug Open Bug Cancelled Cancelled
        13s 1 Daljeet Singh Virdi 27/Jan/26 4:15 AM
        Cancelled Cancelled Reopened Reopened
        10s 1 Daljeet Singh Virdi 27/Jan/26 4:15 AM
        Reopened Reopened Closed Closed
        11s 1 Daljeet Singh Virdi 27/Jan/26 4:15 AM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Daljeet Singh Virdi
            Reporter:
            Daljeet Singh Virdi
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 3 hours, 30 minutes
              3h 30m

                Drag and Drop