Entry Number in G/L Entry table

franklin1232

I am trying to post some invoices. When the post calls MoveJnlLineToLendgerEntryDim Function it errors out trying to enter a new GL Line. The error is TableID=17, Entry No.=7693548,Dimension Code='Department'

It seems like Then Entry No. thinks it already used 7693548 and can't use it again. I checked the table and the last Entry No. 7693547. It's possible someone manually deleted a G/L Register using developers license, but how do I get past this error. If the table doesn't auto increment the Entry No. were does it come from. It appears to be creating the Vendor Ledger Entry record with the same Entry No. with out a problem. What creates the Entry No? Can I manually assign it a higher number?

Navision 4.05 on SQL Server

Savatage

so when you checked table 17 did that Entry No exist?

awarn

It's hard to tell from the error message you descrie, but I think the error message is talking about the Ledger Entry Dimension table.

Check that table to make sure that the dimension isn't there already (specifically check for that table, entry # and dimension code).

If that all looks OK, check the journal line dimensions and make sure nothing looks odd - was that data imported from somewhere with a custom dataport / code? It may be possible that the dimensions were not validated properly.

-a

Marije_Brummel

What is Navision 4.05? Is that half a servicepack O:)

themave

Why don't you try to make another journal entry, outside of the sale invoice, this should make the system create a new entry, use that number and increment it for you.

franklin1232

awarn you hit it on the head. The Ledger Entry Diemension table had the Entry number in it. I think our vendor put a newbie on one of our account's requests to delete some miss posted data. They forgot to delete everything. I don't agree with this method, but they've done this for as long as they've use NAV.

4.05 is really Version 4 pre SP1 with the 5 critical security updates.

Adux

franklin1232 wrote:

awarn you hit it on the head. The Ledger Entry Diemension table had the Entry number in it. I think our vendor put a newbie on one of our account's requests to delete some miss posted data. They forgot to delete everything. I don't agree with this method, but they've done this for as long as they've use NAV.

4.05 is really Version 4 pre SP1 with the 5 critical security updates.

It is not good idea to delete posted data.
[-X
It is easy way, but it is not right way

kriki

Adux wrote:

It is not good idea to delete posted data.
[-X
It is easy way, but it is not right way

And it is especially an easy way to create potentially big problems later on. The problem you have now, is only a small taste.