[Dave Webb]

We have an open payable which was keyed in a prior month.  We need to void the payable.  When we attempt to void the transaction we get a message which states:  “This document cannot be marked for voiding.  It has been either partially applied or is on hold.”  As far as we can tell in the system, there is no partial application or hold.  I have looked at similar issues through searching online and tried several things  including the steps in this MS article : https://support.microsoft.com/en-us/help/856474/error-message-when-you-try-to-void-a-payables-transaction-in-microsoft

Any help on next steps would be appreciated.  Thanks…

——————————
Dave Webb
MCCC
Prestonsburg KY
——————————

[Jo deRuiter]

Hi

I have seen this happen if you have a check batch in a Work Status in which the invoice is partially or fully set to be paid.

If you don’t have an open check batch, use SQL to see if you have an orphaned payment in a Work status in the tables and delete the Work transaction fully.

Before any of that make sure it has definitely NOT been applied, even partially to a payment or credit memo by opening the inquiry screen and drilling down into the document you want to void and then going to the ‘apply’ button to see if anything is there at all.?

——————————

——————————
——————————————-

[Dave Webb]

Thanks for the quick response Jo.  Can you tell me what table to look at for “orphaned payment in a Work status “?  I am familiar with SQL but not what GP tables hold what information.  Is there perhaps a document describing this process?  We are pretty new to GP.  Thanks..

——————————
Dave Webb
MCCC
Prestonsburg KY
——————————
——————————————-

[Jo deRuiter]

Hi

Try the PM10200, PM1020,PM10300?,PM10400.  Additionally, you may need to reset the CURTRXAM in the PM20000 after you reset work tables and if the CURTRXAM is less than the DOCAMNT.

It’s possible, but not likely that there could be an orphan in the PM20100 as well.

If something became ‘wonky’ in a prior payment or credit batch then you could also find orphans in the apply to history tables, though not likely: PM30300.

——————————

——————————
——————————————-

[Dave Webb]

We were able to find the entry in some of the tables you listed.  Are you saying we should just delete the entry from those tables to fix the issue?  When you say “you may need to reset the CURTRXAM in the PM20000 after you reset work tables and if the CURTRXAM is less than the DOCAMNT.” What exactly do you mean?  Thanks so much for the help.

——————————
Dave Webb
MCCC
Prestonsburg KY
——————————
——————————————-

[Dave Webb]

We deleted all of the entries we found in the tables mentioned and the transaction is no longer showing up.  I hope this was the correct thing to do.  Thanks…

——————————
Dave Webb
MCCC
Prestonsburg KY
——————————
——————————————-