I thought that the UI would prevent accidental reporting of duplicate actions but Im finding duplicates in AFS. How come?
There are a few reasons this can happen. First, the UI will allow some action to be duplicated. When you rely on the number generator to assign action numbers, the UI checks a history file to see if the action you are reporting has ever been recorded before. If it has, it checks to see if it is of a type that EPA business rules have identified as an allowable duplicate (Stack Tests for example). You will see warnings in the validation report about duplication, but those actions can still be exported from the UI for AFS submission. However, if it is a non-allowable type such as an HPV day zero, the UI will report the duplication in the validation report and will not write out an AFS transaction when you export. The rule to remember is that you should review duplicate warning errors in your validation report, because warnings are allowed through to AFS. If you were to report an action that was not already in your UI history but was in AFS, it could also be duplicated. This could happen i
Related Questions
- Someone manually added and changed actions in AFS, and the action history in the UI don match them anymore. How do I get my UI history to match AFS?
- How do you transform complex and historically accidental transactions into tightly controlled, premeditated actions?
- How do I use Picasas Duplicates Report to eliminate duplicate photos?