Notices Failing after OD and ASD61 NSG Changes using TMA_EXTERNAL_NOTICE_API

Majority of our notices are created using TMA_EXTERNAL_NOTICE_API. On the 16/JAN/2014 there was a change in OD file from a HA (1050). Their NSG December2013 data has successfully been loaded on , so that the USRN's are referencing the new DISTRICTS with a new NOTICE URL in the OD file. The old DISTRICT's NOTICE URL is different and unavailable from 17/JAN/2014.

The problem we are now getting is when notices are created using the TMA_EXTERNAL_NOTICE_API where an INITIAL/FORWARD PLANNING INFORMATION notice for a given WORK REF were created before the 16/JAN/2014, i.e. when the USRN is pointing to the old DISTICTS, then subsequent notices for the same WORK REF are being created in MONITOR WEB SERVICE TRANSACTIONS with the OLD DISTRICT and subsequently failing.

The same senario occurs if there is a previous PHASE for a given WORK REF using the OLD DISTRICT.

There seems to be a bug in the API because if the USRN's ASD TYPE 61 record changes the AUTHORITY DISTRICT in between the above stages of a WORK REF then the new AUTHORITY DISTRICT is not being used from the STREET GAZETTEER record to send notices, but instead using the details of where the NOTICE was sent last for the WORK REF.

We need this behaviour looking at urgently and guidance on how to get the failed notices processed to go to the new DISTRICTS.

(SWM v4400; TMA_EXTERNAL_NOTICE_API PACKAGE $Revision:   3.3  $; TMA_EXTERNAL_NOTICE_API PACKAGE BODY $Revision:   3.25  $)

Parents Reply Children
No Data