Item Ledger entry and Value entry compression or archive?

(0) Share

Report

Posted on by Community Member

Will the archiving or compression of the Item Leddger value entry table and value entry table affect the weighted average cost in Navision 3.6? or older? There is a case and 3.1 is still used and need to know the above requirement,

Thanks

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Alex Chow 4,481 on at

Like (0)

Report
Copy link

Link copied!

Never use the compression process on Item Ledger or Value Entry! Compress something else.

Was this reply helpful? Yes No
Jill Geiger Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

As mentioned by Alex, compression is not recommened in the Inventory area. I just wanted to stress this area from past work on Inventory costing. Also this option is no longer available in NAV 5.0 going forward. In Version 5.0, the Item Ledger Date Compression was removed due to several concerns:

1) The date compression rarely resulted in a significant reduction in entries.

2) Changes related to profitability reflected on Customer records for Value Entry adjustments and other historical reporting that required a complete value entry and item ledger entry structure would be lost if date compression occurred

3) Due to issues in early version (2.60 and prior) with compression of data resulting in incorrect historical records.

Development decided to remove the feature to prevent the elimination of historical inventory data that would then negatively impact reporting.

4) Change in 5.00 for G/L Reconciliation to Value Entries would be lost or corrupted without the details.

In Version 4.00, the Date Compression was available. There were reports of some issues where date compression didn't seem to work. However, in some cases, the date compress didn't work because not all of the factors required were met.

In addition to the information above, from my understanding, there were a couple new features within 5.0 to better the product in which Date Compression would conflict with. One area was in regards to the Always Reconciliation feature where Table 5823 - G/L Item Ledger Relation was introduced which allows detailed reconciliation even when posting in summary. The other area was in regards to the Customer Statistics Reporting Original and Adjusted Cost and Profit calculations in which Date Compression would skew those amounts.

Also coupled with that, from the time I can remember, Date Compression has always had its issues. This has been a functionality that had always brought up questions, a functionality which never seemed to result in customer's expectations just because of the pure workings and complexity of Inventory quantities, valuations and applications (due to so many restraints put in place to keep data integrity that not much would be compressed anyhow), as well as issues/bugs it has had in the past corrupting data if users were not careful and appropriate fixes were not applied. These are other possible scenarios in which Dev. had made its decision based on, to go along with the new 5.0 features.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks for informative reply, really appreciate that.

So what will be the solution when it comes to a huge native database? or even SQL when reaching certain size?

thanks

Was this reply helpful? Yes No
Jill Geiger Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Kareem,

It would be possible to do compression through SQL. Here is a blog that talks about it

blogs.msdn.com/.../microsoft-dynamics-nav-and-sql-server-database-compression.aspx

If you are looking for anything more in depth on this, then you would need to enter in a support case directly with Microsoft or reach out to any partners that may offer a service for this.

Thanks

Jill

Was this reply helpful? Yes No