Revaluation journal dimension error

Bokk

We have a client that has got a handful of items whose costing has gone south. We need to make an adjustment in the Revaluation Journal. We have brought in all the lines required, but when we try and post we get an error message that says: "The Ledger Entry Dimension already exists. Identification fields and values: Table ID = '5802', Entry No. = '122580', Dimension Code = 'ZONE'

The Entry No. this seems to be referring to would be the next one created (it doesn't exist in the table yet). I did get a work around from MBS for CU 21, but it has not affected the error, which actually stops in debug in CU 408 in the Repeat loop. I am not sure why it is getting in here to begin with.

MoveJnlLineDimToLedgEntryDim(JnlLineDim,ToTableID,ToEntryNo)

WITH JnlLineDim DO
IF FIND('-') THEN

REPEAT

LedgEntryDim.INIT;
LedgEntryDim."Table ID" := ToTableID;
LedgEntryDim."Entry No." := ToEntryNo;
LedgEntryDim."Dimension Code" := "Dimension Code";
LedgEntryDim."Dimension Value Code" := "Dimension Value Code";
LedgEntryDim.INSERT;

UNTIL NEXT = 0;

Also, we are bringing in the lines with inflated positives values in the Cost Amount (Actual) field. Can we/should we do anything with the inflated negative amounts?

If anyone knows how we can get past this error, it would be appreciated.
Thanks!

kine

1) It is on MS SQL server?
2) Can you try if the record is existing before this loop? If yes, there is some other point where the dimension is created...

Bokk

We are running an SQL backend.

When I looked in debug, I can't see that record created already. At the time of the error, the record variables are not initialized. When I check the table after, the record specified in the error message does not exist. I am not sure where else to look to see if it is being created previously.

Thanks,

Marije_Brummel

If you want to see the variables in the debugger you can set a brakepoint just before where the error occurs. The debugger will stop there.

When the debuggers errors out you cannot see some of the values anymore.

hanahana

I have the same error? Did anyone solved it?
I think that the problem is with check dim combionation that works different in Nav 4.
Help please!

Bokk

Our issue was a data corruption problem. If I recall correctly, there were a few records in the Item Ledger Entry table that did not have corresponding records in the Value Entry table.

In the process of determining that, we were also requested to ensure all the fixes were up to date.

Good luck!

coascender

I know this is an old thread but I encountered a similar problem during a new Navision implementation. We could not post any transactions with dimensions. Navision generated this error: "The Ledger Entry Dimension Already Exists ID=17,Entry No.=23118,Dimension Code=Department".

We posted begining balances for April 2007. After review our client realized he gave us incorrect balances. We deleted the transactions from the G/L Entry table but forgot to delete the corresponding entries in the Ledger Entry Dimension table (#355).

New postings with dimensions got a G/L entry no. that had already been used in the Ledger Entry Dim table so Navision errored. When we deleted the entries in the Ledger Entry Dim table (that should have been deleted along with the begining balance postings) everything worked.