Record already exist even though there is no such record

RachelSoon

Dear All,
When my customer is trying to post the FA GL journal, after the system checking the line and trying to post the 1st line of the journal, then system will prompt "The FA Ledger Entry already exists. Identification fields and values : Entry No = '3670477'"
However , the last entry no for the table is 3670476.


Any one has any ideas how to solve this?

Thank you.

Regards
Rachel

ara3n

Do you have any modifications?

Usually you get this error is because of this scenario.

FAEntry."Entry No." := LastNumber;
FAEntry.insert;

FAEntry2."Entry No." := LastNumber;
FAEntry2.insert;

Two Entry in same posting routine getting the same entry and you get an error on the second.
Fixed asset have not changed in a while, so check partnersource and knowledgebase for the bug.
Or if you have a modification then take alook at that.

RachelSoon

Dear ara3n,
Thank you for your prompt reply.

No, there is no modification for this FA codeunit (5600).

The user has been doing the posting for some time already. the error message just start prompting within these few days.

Below below is from the codeunit 5600, function : InsertFA
The error is at the line i mark with %%%%%

FALedgEntry."Canceled from FA No." := FALedgEntry."FA No.";
FALedgEntry2."Canceled from FA No." := FALedgEntry2."FA No.";
FALedgEntry2."FA No." := '';
FALedgEntry."FA No." := '';
FALedgEntry2.MODIFY;
FALedgEntry.MODIFY; %%%%%
FALedgEntry."FA No." := FALedgEntry3."FA No.";


Are you saying that this is the standard bug?

Thank you.

Regards
Rachel

ara3n

Are you sure it's .MODIFY?

It should be .INSERT.


Please check MS partnersource for the bug. It looks like standard bug.


Also what version are you on?

RachelSoon

ara3n wrote:

Are you sure it's .MODIFY?

It should be .INSERT.


Please check MS partnersource for the bug. It looks like standard bug.


Also what version are you on?

yes. i on activated the debugger and the error stops at "Modify".

I am using NAV4.0 (without SP).

can not find any similar problem at MS partnersource. Will post the problem to MS.

Thank you.

jannestig

HI Rachael

No its not a bug, this type of error i have seen a few times throughout the systems usually related to something impact on the GL or other financial information.

though i have solved it a few time its always related to the data you are trying to post, you will have to review what its posting carefully to identify it.

RachelSoon

jannestig wrote:

HI Rachael

No its not a bug, this type of error i have seen a few times throughout the systems usually related to something impact on the GL or other financial information.

though i have solved it a few time its always related to the data you are trying to post, you will have to review what its posting carefully to identify it.

Hi,
actually my customer SQL log file was corrupted on 17 Jan, there system wen to suspect mode. and we manage to rebuild the SQL log on 17 Jan evening.
However, on 18 Jan, we have problem on posting journal (cash receipt journla, payment journal), where by the system complain that the entry no XXX already exisit in ledger entry dimension, but there was no such record in the system.

On 19, Jan, the ledger entry dimension message still persist.

On 20 Jan, the ledger entry dimension error message disappear, we can post the cash receipt journla, payment journal.
But we have we can not post FA GL Journal, system complain the entry no XXX already exist in the FA ledger entry table.

So, would it be the database is not at the "good" stage?

THank you.

Regards
Rachel

ara3n

Please get a consultant to look at the Ledger and dimension entries.
You can also do a navision back .fbk and restore it and see if you still have the problem. Otherwise get a consultant/developer to cleanup the data.