A Utility believes they are receiving duplicate inspections. This has been highlighted since moving to EToN6.
The reason they are seen as duplicates is because prior to EToN6, if an authority made an amendment and resent the batchfile it overwrites the other inspections, but this was never seen before as there was no sequence numbers in batching like there is in EToN6 – Now inspections are sent via the Web Service.
Query the Works reference in TMA3000 – Monitor Web Service Transactions Form
You will need to tick the include ‘successful transactions’ tick box and uncheck the Restrict check box. Put the form in query mode and query back the works reference. Order by sequence number. Then check the inspections individually. Is the Sequence number the same – then YES it is a duplicate
If the sequence number is different check the XML for each inspection. The Created date is Different – Then this is not a duplicate inspection and is it very likely the Authority made an amendment and then sent another inspection to overwrite the change.
Compare the earlier XML to the one you feel was a duplicate and check what has changed.