jimmymac
Reputable Poster
We have a user that tried to void a GL transaction with GL date of 12/31/2012. When she tried to post, it errored out becuase some of the business units on the original transaction no longer allow posting, they've been closed.
But the real problem is that now the user says she didn't mean to void them and doesn't want to proceed with the void. The state of things is that this GL document number now has the original transactions that are posted, and the void transactions which are not.
There does not appear to be a way to delete these unposted void transactions. For a normal GL transaction that is not posted, you can just delete it in journal entry. But since the document now contains void entries (though unposted), it does not allow the user to delete.
Our suggestion was to correct the PEC codes so the batch will post, even though they now do not want it to. Then reenter the orginal transactions.
Any other options out there specifically on how to delete this unposted void entries?
Thanks.
But the real problem is that now the user says she didn't mean to void them and doesn't want to proceed with the void. The state of things is that this GL document number now has the original transactions that are posted, and the void transactions which are not.
There does not appear to be a way to delete these unposted void transactions. For a normal GL transaction that is not posted, you can just delete it in journal entry. But since the document now contains void entries (though unposted), it does not allow the user to delete.
Our suggestion was to correct the PEC codes so the batch will post, even though they now do not want it to. Then reenter the orginal transactions.
Any other options out there specifically on how to delete this unposted void entries?
Thanks.
