Hello all, i’ve met a strange message that is multilanguage, tells about the error that blocks the item cost posting into the G/L Entry (T17): >The transaction cannot be completed because it will cause inconsistincies in the G/L Entry table >Check where and how the CONSISTENT function is used in the transaction to find the reason for the error >Contact your system manager if you need assistance. >Parts of the program mark tables as inconsistent during very comprehensive tasks, such as posting. This prevents data from being updated incorrectly. But the error point can not be intercepted in the debugger - it looks like everything performed correctly and message appears. I’ve failed to find error point in the code [xx(]. It’s the first such case in all my work with Navision. So the question - what’s the better way to handle this and similar situations in Attain? Really appreciate any advices Thank in advance, Anthony
It has been discussed a few times. Try Seaching the forum for “inconsis”
HI, If it is while posting see your debit amount and credit amounts going to GL accounts are not equal…
Anthony, there is no “error point”. The error will appear when the transaction is committed, either explicitly with COMMIT or implicitly when code execution ends. Please read the docs for the CONSISTENT function to learn why…
Hi, I had the same error ones and the problem was that the Gen. bus. posting group was not filled in on my general journal line when i tried to post the line. Regards, Wendy
Hello all, to the first thank you very much for your inputs. Apologising for late response i’ve to say follows: there’re not any COMMIT and .CONSISTENT(CONDITION) calls. It is report. Search for calls was completed almost for all execution including tables triggers and codeunits. So it is more question about this message than about the source of error. Is it possible to find it somewhere or it is some kind of system messages unreachable even in debugger viewer? In my opinion it would be great to see part of the code which lead to the error message appearance. It could be a some kind of hint on the source of the problem. Unfortunately i cann’t use local search option due to system issues. Thanks in advance, Anthony take some time to follow
You should really read about CONSISTENT in online help. The scenario you are having probably goes like this: You are making some changes on GL. When going thorugh CU12 (FinishCodeunit) your GL entry is marked as Inconsistent. but this is not necessary an error. next time going through CU12, the GL entry may become consistent. the error is issued at commiting if GL entry is still inconsistent. commit happens explicitely when you call it or it happenes implicitely when all the code is finished. this second is probably your case, since the error is displayed at the end of code… what changes are you doing to G/L? are you sure that they are balanced within posting date…
Hi ®obi, thanks a lot for your advice - i really missed this CU and function. All other recomendations shall take some time. Regards, Anthony
hi, You are facing this message as your Debit/credit are not matching, there could be some unit prices in your records which have a decimel value and while posting the amount into g/l entry table debit and credit amount is not matching and it’s throwint that error message. If you set the unit price to 0.00. It will post the ledger enteries. Regards
Hi and thanks again, we just now updated our system version to 3.70A from 3.60 SP3 (conf 3.11) and this problem disappeared. So it’s in some kind fixed whatever it be. Best regards, Anthony