A Territory is End Dated but its Related Child Assignments are not End Dated in Veeva Align. What may cause this issue and how can it be resolved in an effective way?
The cause of this issue is related to the data itself belonging to the Territory.
In most cases, it occurs when there are date-related problems between the Territory and the child assignments however, there may be other reasons.
The solution is to try resaving the affected Territory again by editing and saving it on the Vault UI. If a Popup window appears with assignment information, that means there are child assignments which are current (not end-dated).
It is also possible to execute the Territory end-dating using the Align Data Loader. It supports end-dating the child assignments as well.
If there are any current (not end-dated) child assignments, the Territory end-dating process attempts end-dating them again. This is reflected by a Process Task called ASSIGNMENT_UPDATE if it is carried out on the Vault UI.
In case the Territory is end-dated using the Align Dataloader, this stage of the Import process task is part of the end-dating process.
Once it has finished, check the Process Task record for any errors. If there are any errors, they are the cause of the issue and need to be resolved.
Align Help Documentation:
Send us your feedback: We're always looking for feedback to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.