Great Plains (GP 2010) Payables Management (PM) - incorrect vendor

I have loaded a lot of transactions into a batch and realized I was using the wrong vendor.  What is the correct way to handle this?  Go ahead and post the batch and the void or change the vendor in the open transactions table using SQL?  I do not want to re-enter all of these transactions if at all possible.  Thanks!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Victoria YudinOwner / Dynamics GP ConsultantCommented:
I would stongly advise against changing the vendor in SQL especially on posted transactions. The main reason for this is that this would bypass any logic that GP would normally apply to these transactions. It's almost impossible to predict what issues this might cause. Checking for all of them might actually take more time than re-entering all the invoices.

For posted transactions, this is even worse - there are probably at least a dozen tables that would need to be checked or changed. Including vendor summary tables, GL tables, etc.

Sorry not to have the answer you were looking for.
pstreAuthor Commented:
I'm confused.. I was asking about unposted transactions and in the answer, you are referring to posted transactions.  For the 2nd paragraph, did you mean "unposted" rather than posted?  Thanks!
Victoria YudinOwner / Dynamics GP ConsultantCommented:
Sorry about any confusion. In your question you asked about changing the vendor in the unposted batch, then asked if you should, "Go ahead and post the batch and the void or change the vendor in the open transactions table using SQL".

My answer is really the same for both posted and unposted - I really do not recommend this. It is bad enough for unposted transactions, but it is even worse for posted ones.

Hope that helps clarify.
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

pstreAuthor Commented:
So the transactions would have to be re-entered with the correct vendor?
Victoria YudinOwner / Dynamics GP ConsultantCommented:
Yes, that is the best course of action. If you have Integration Manager, perhaps you can import them instead of entering them manually?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pstreAuthor Commented:
Great! Thanks..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Dynamics

From novice to tech pro — start learning today.