Reason for Inconsistency error in navision

chandrurec

Hi all,

When I try to post the transaction from Payment Journal Form, I am getting a error as follows.

"The transaction cannot be completed because it will cause inconsistencies in the G/L Entry table.Check where and how the CONSISTENT function is used to find the reason for this error.

If anybody knows the reason for correcting this error , Kindly suggest.

Is this error due to Coding or data entry.

Thanks in advance.

Regards,
Chandru.

Sunset

Sounds like you have changed the posting routine.
The consistent check is there to make sure that when the posting is complete debit and credit match.

matttrax

It doesn't mean you've changed code badly (although that could be the case). If it just a specific document then it is most likely due to rounding issues, usually a tax rate from my experience.

JosephGress

Here is a way to get a clue about where your problem is.

ONLY DO THIS IN A TEST DATABASE!

Comment out the line (or lines) of code that does the CONSISTENT check IN A TEST DATABASE. Post the transactions that are giving the inconsistency error. Then look at the debits and credits and see what is not balanced and why. I agree with MATTRAX that it is most likely due to a rounding issue.

NEVER DO THIS IN A LIVE DATABASE.

matttrax

JosephGress wrote:

ONLY DO THIS IN A TEST DATABASE!

Comment out the line (or lines) of code that does the CONSISTENT check IN A TEST DATABASE.

I think it's better to just go through the debugger (if you have that ability). There's a post on Mibuso about where to look. I want to say it is something like FinishCodeunit in the General Journal Line Post codeunit.

Savatage

i use this...
How to see why you are getting CONSISTENCY Error
viewtopic.php?f=5&t=22748

matttrax

Excellent tip. I had never come across it before for whatever reason.

Savatage

matttrax wrote:

Excellent tip. I had never come across it before for whatever reason.

Hopefully you'll never need it. [-o<

matttrax

Only about every 6 months. When you have tax rates out to 5 decimal places it's bound to happen.