Hi Amanda,

Thanks for your post. This message means that's there's remnants of the Generate Rent Roll batch that created the charge still in the PM new file. Usually doing Post Entries in Property Management will take care of the problem. Be sure to review the posting journal for any errors or rejections that may need to be addressed.

I just published article 31576 in the knowledgebase so that you can find this error now.

April

Thank you for the information April, but I'm not sure how to resolve the issue because there are no batches to be posed from the PM new file, and the GL entries for the charge I'm trying to reverse are in the current GL file. I can view the charge using the Inquiry --> Transactions Information in PM, and selecting the current PM transaction file while the new file provides no entries to view.

So you confirmed in PM Tasks, Post Entries, under Ranges there are no batches available? What's common with this error is that the transactions are posted and in the current file but the batch record is still in the new file. It won't show anything in the Transaction Information inquiry.

So you confirmed in PM Tasks, Post Entries, under Ranges there are no batches available? What's common with this error is that the transactions are posted and in the current file but the batch record is still in the new file. It won't show anything in the Transaction Information inquiry.

If I try to use the Post Entries function in PM, there is no batch to select. There was an empty change entries batch available to post earlier today (from another user), but I have since posted that batch and there is nothing more to post from the PM new file.

Did anything change after posting that batch? Are you able to void the charge or are you getting the same message?

If you're getting the same message, then the other possibility is that the batch record is locked open on the server, KB 23883.

I am still getting the "Unable to lock the batch record" when I try to void the charge - this is after posting the empty batch from this morning and following the instructions in KB article 23883.

Sounds like we should have you call into support so we can troubleshoot it further.