Finance | Project Operations, Human Resources, ...

how to delete a stuck journal entry in dynamics GP

(0) Share

Report

Posted on by Braw Rajab

hello ,

i have JE when i try to open in financial -> transaction -> general it says ( journal entry xxxx has been entered in another window) i want to correct the transaction (back out a JE) but it cant let me since the TRX date is 0/0/0000.

so how can i delete/void that transaction

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Hokuminaria 2,950 on at

Like (0)

Report
Copy link

Link copied!

Hello Braw,

Based on the information provided, my thoughts are that the GL10001 records are missing the BACHNUMB and BCHSOURC and why you are getting this message. It also appears that the TRXDATE is missing and the Series field is missing as well.

If you want to delete this, you would need to look at the GL10000 and GL100001 table and remove the records associated with this JE.

select * From GL10000 where JRNENTRY = '6943'
select * From GL10001 where JRNENTRY = '6943'

I would personally review the data and determine what is incorrect and correct the incorrect fields so it can be pulled up and deleted instead of deleting through SQL.

I hope this helps!

Thank you!

Brandon Jarrett | Microsoft Support Engineer.

Was this reply helpful? Yes No
Braw Rajab 25 on at

Like (0)

Report
Copy link

Link copied!

hello brandon,

thank you for your reply but is there any other way to fix this issue beside deleting it in the tables you mentioned? because i do not have access to them

thanks!

Was this reply helpful? Yes No
Leng Papio 855 on at

Like (0)

Report
Copy link

Link copied!

Try having everyone out of GP and running this in SQL:

DELETE DYNAMICS..ACTIVITY

DELETE DYNAMICS..SY00800

DELETE DYNAMICS..SY00801

DELETE TEMPDB..DEX_LOCK

DELETE TEMPDB..DEX_SESSION

When a user logs into GP, the ACTIVITY, DEX_LOCK, and DEX_SESSION tables creates a record indicating it.

When a user opens a transaction entry window, it creates a record in the SY00800.

Usually, when a user processes the transaction, it also creates a record SY00801.

These usually locks the transaction.

As long as the entry is not 'corrupted', you should be able to select it when you have deleted the above tables and get back into GP (and make sure no one selects that same JE).

Hope that helps.

Was this reply helpful? Yes No
Leng Papio 855 on at

Like (0)

Report
Copy link

Link copied!

Oh, missed the part you don't have access to SQL.

Then have everyone out. Usually this also clears the tables I mentioned. If that does not help, then make sure you have the 'sa' password, and login as 'sa'.

Have everyone out, and delete the stuck login if there is any.

There is still other things within GP that you can do if this does not work... but I recommend contacting someone who can access SQL for you; as that will be the easier way to go.

Was this reply helpful? Yes No
Suggested answer

David Musgrave MVP ... 14,151 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

If you don't want to get everyone out of SQL, you can try

winthropdc.wordpress.com/.../

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,061 Moderator on at

Like (0)

Report
Copy link

Link copied!

David,

The OP said that he doesn't have access to the SQL back-end tables.. But using GPPT would provide them with a way of executing the code from the GP front-end, though without the proper permissions (sa) that would likely fail too.

Was this reply helpful? Yes No