Investigating and Voiding Disconnected Events
Under most circumstances, you should verify that a disconnected event did not occur due to a data entry error in the HR data associated with the event.
You also want to review the impact of the event's disconnection as well as the impact of the correction of the event disconnection. For example, if the disconnection takes place because HR data was inadvertently deleted, the correction of that mistake will most likely cause the system to create new BAS_ACTIVITY records and possibly a new participant event.
If a participant event is disconnected after it has been finalized (also because eligibility information related to the event was lost), you may have to void the disconnected event to back out any election information it entered.
To void a disconnected event:
-
Access the finalized, disconnected event on the Controls page of the Processing Controls Update component or the Event Status Update page.
-
Select a Process Indicator value of Void.
-
Reprocess the event.
When you do this, the system backs out elections associated with the event, sets the event status to Void, and sets the event's process status to RE.