Problem with 2.60 fin compressed I/L

C2A_denis · 2005-01-26

Hi,

i'm trying to migrate our customer from 2.60 fin to 3.70A Navision and having trouble with compressed I/L entries & codeunit 104049 in UpdateItemApplEntry(). This function takes place after the UpdateItemLedgEntry().

Some of his Item Ledger Entries have been compressed & it seems the migration processes the I/L but is blocked with apply entries associated with some compressed I/L. The problem appears with:

WITH ApplEntry DO
...
REPEAT
ItemLedgerEntry.GET("Item Ledger Entry No."); -> Crash saying "the entry No. xxxxxx does not exists".

Apparently, the first I/L from the original table 32 the UpdateItemApplEntry() function can't find is compr. I/L that has a quantity = 0 and an invoiced quantity <>0.

So, can someone explain to me why I/L entries disppeared from the original table and is it due to compression?

I think the way the UpdateItemLedgEntry() function processed the compressed I/L may be a part of the solution.

Please help...

Waldo · 2005-01-26

(I was told that) the compression in navision-terms is: deleting a bunch of lines in the ledger entries, and combine it in one total line ... .

Solution ... dunno ... no experience with it ... sorry ... .

C2A_denis · 2005-01-27

Yep, thanks

the second time we processed we managed to store the apply entries for which there is no coresponding/source I/L entries in a table Temp and we found some matching criteria between the compressed I/L not present anymore:

It looks like there is two line created when compression is done, grouping some I/Ls together like you said but from this group filtered by "designation" on "compressed entry" and generated by the same operation i.e following each other, only one is present in table Temp.

I don't have screenshot now because i'm not at work till monday but I could easily do detailled screenshots of compressed entries that cause the problem but what I need is also a way to target the problem possibly in Navision standard migration codeunits 104048 & 104049 as soon as possible not to delay the delivery of Test database for too long(we're lread late).

Do you know anybody with some experience about Compression with fin 2.60 ?

cheers.

Waldo · 2005-01-28

Well, I don't know anybody.

Usually, when I explain to the customer that they are going to loose details when compressing ... they decide not to do it...

Problem with 2.60 fin compressed I/L

Comments

Categories