Batch stuck with status Updating

(0) Share

Report

Posted on by AndreaIES

1,005

I have an user who asked me to release the batch held on posting. We took a backup and ran the SQL update to release as recommended on KB article 850289 -UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='CMTRX00000612'. After running the SQL update, the batch now shows as Available if you go to Series posting but if you go to the actual batch (Financial>Transactions>Batches) it still shows as Updating.

I ran reconcile on batches and it certainly gave me an error where the batch total for that batch was updated but it did not do anything else. The batch still shows with Updating status.

See below the results on the SQL query for the SY00500 table.

Screen-Shot-2014_2D00_08_2D00_15-at-11.48.17-AM.png

Screen-Shot-2014_2D00_08_2D00_15-at-11.48.34-AM.png

Screen-Shot-2014_2D00_08_2D00_15-at-11.48.50-AM.png

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (1)

Suggested answer

Mahmoud Saadi 32,738 on at

Like (0)

Report
Copy link

Link copied!

Hello AndreaIES

You are absolutely on the right track, you may check the batch total in both GL10000 and SY00500, additionally, set the PSTGSTUS to 1.

When I have such problems with batches, I usually just delete the old one (if possible) and recreate a new one, which will recalculate and inherit the parent details and information from the original module. For you, this is a valid option to consider.

Your feedback is highly appreciated,

Was this reply helpful? Yes No
AndreaIES 1,005 on at

Like (0)

Report
Copy link

Link copied!

Thanks Mahmoud. I did check the batch on GL10000 table and it looks OK compared to SY00500. I also checked the Journal entries on GL10000 for that batch and those look posted and good so your suggestion is to set the PSTGSTUS to 1 and delete the batch? I think that transactions don't need to be recreated since they show posted and good. I appreciate your reply.

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report
Copy link

Link copied!

Not at all, by deleting the batch I don't mean deleting the transactions within. You may go to the General Ledger Journal Entry, enter a new batch number in the batch field, then delete the old batch.

This is what I mean by assigning your transactions to a new batch, and delete the old one. The batch is nothing but a container for your transactions.

Was this reply helpful? Yes No
AndreaIES 1,005 on at

Like (0)

Report
Copy link

Link copied!

I understand what you are are saying, I will recreate the journal entries and delete batch afterwards. However, I updated to set the PSTGSTUS to 1 and I still cannot retrieve the transactions nor select the batch for deleting since I have the message that the batch is being posted.

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report
Copy link

Link copied!

AndrealES

The batch status is retrieved from SY00500, which is why I found it weird that the system is giving you such an error. I believe you need to save your time and create a new batch.

Do not "recreate the journal entries", just assign them to a new batch simply.

Was this reply helpful? Yes No
AndreaIES 1,005 on at

Like (0)

Report
Copy link

Link copied!

I appreciate you time and support. I got it just assign the existing JE to a new batch but is not letting me to retrieve the transactions on the General entry window. It shows a message saying "This batch is being posted".

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report
Copy link

Link copied!
Lets do it as illustrated below;

Go to Financial > Transactions > Batches

Create a new batch, fill in the batch id "XXX" and choose the origin as "General Entry"

Now run the following update statement on GL10000

UPDATE dbo.GL10000
SET BACHNUMB = 'XXX'
WHERE JRNENTRY IN (....)

Now go back and check the General Ledger journal entry window.

Your feedback is highly appreciated,

Was this reply helpful? Yes No
AndreaIES 1,005 on at

Like (0)

Report
Copy link

Link copied!

OK, we are making some progress but still not there. remember when I said that the journal entries show posted. Well, I got the Journal entries into the new batch using your SQL update, when I try to open the Journal entry from the General Entry window, I got a message saying The journal entry XXX has already been posted

If I look up for the journal entries, I still see the journal entries showing with the new batch number

If I see the batches, I still can see the old batch 612 updating and the one I moved the transactions to says no transactions. Weird! isn't it?

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report
Copy link

Link copied!

I have missed the GL10001, the update should include this table as well

UPDATE dbo.GL10001
SET BACHNUMB = 'XXX'
WHERE JRNENTRY IN (...)

I would like to check these journal entries, which we moved into the new batch, could you find them in the GL20000 ? I am afraid, they have been posted, and remain in the work table.

Let me know how it goes,

Was this reply helpful? Yes No
AndreaIES 1,005 on at

Like (0)

Report
Copy link

Link copied!

Mahmoud, I ran the UPDATE dbo.GL10001 SET BACHNUMB = 'ADJ-BTCH612'WHERE JRNENTRY IN (166503,166504,166505,166506) but no rows got updated.

I checked the table GL20000 and those journal entries are there so I believe we have to remove from the work tables. Right? Should I remove the entries from the work table as well as the batches sitting on SY00500?

Was this reply helpful? Yes No