Share
Reportclient merged 2 AP vendors - wrong vendor chosen - what sql tables would be affected to undo this 'oops'
*This post is locked for comments
You’re offline. This is a read only version of the page.
client merged 2 AP vendors - wrong vendor chosen - what sql tables would be affected to undo this 'oops'
*This post is locked for comments
Hi Deanne,
I wholeheartedly agree with the others. If you want to convince yourself it is a job you can't win, do a search on the entire database for the merged item number and note just how many tables it's included in. Still, you will not see all of them because the related table doesn't necessarily include the item number - like the transaction distribution tables and the apply tables. Even if you could identify all of the tables, you would need some creative way to identify which transactions belong to the old vendor.
If you do not have a backup, put in a support case - but just know that this is not a support issue, everything is working, they just picked the wrong vendor. If you can at least identify which of the outstanding transactions belong to the other vendor, you can void them or offset them and then re-enter them to the correct vendor. You can use this same method to void the historical transactions. I would not want to try this if there is an abundance of transactions that need to be split out.
Good luck,
Kind regards,
Leslie
Deanne,
Kirk is right on this... Restore is pretty much the only quick way to fix this... There are so many tables involved.. It's not just the vendor master table.
Deanne,
I would highly recommend not trying to fix this via the individual SQL tables. Restore the database from the backup taken before using the merge utility. If you don't have a backup open a support incident with Microsoft because this is going to be a mess to get sorted.
Regards,
Kirk
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (
