web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)
Answered

Quantity is Zero but Value not zero in the inventory valuation report

(0) ShareShare
ReportReport
Posted on by 225

I am on NAV 2009 R2. Using AVCo setup bu item & location. I am having this problem were quantity is Zero but Value not zero in the inventory valuation report. I got a hot fix that was published on the customer source around May 2013. I did make the modifications but I still dont know what to do next - how does the fix work? After applying the changes in codeunit 22 what do i do. Does the fix correct historical data or it prevents future re-occurrence of the problem.

Has anybody used this hot fix out there.

*This post is locked for comments

I have the same question (0)
  • X. GARONNAT Profile Picture
    on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    You should look at KB2781950 which is a rollup dedicated to costing issues with Nav 2009.

    mbs2.microsoft.com/.../KBDisplay.aspx

  • Alex Chow Profile Picture
    4,481 on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    It'll only address this for transactions going forward.

    This article may explain what's going on:

    www.dynamicsnavconsultant.com/.../why-you-have-negative-inventory-value-with-0-quantity-%E2%80%93-navision-37b-to-navision-50

  • Community Member Profile Picture
    on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    Hi,

    In the past has the Average Cost Calc. type always been by Item&Location&Variant? Or has it also been by Item. You can find out this information from the Accounting Periods.

    When this is the case, and you run Inventory Valuation report by Location you might run into a situation where quantity is zero but a value is left (not in total but against certain locations). This even counts when at present the Average Cost Calc. type is by Location.

    None of the hotfixes will address this situation. Additionally as detailed any new hotfixes will likely only 'correct' a data issue on new transactions. You might also need to 'reopen' adjust cost to have the batch job re-visit pending adjustment but this time with the new hotfix merged. How this is done depends on various factors, but further details are described in the Inventory Costing Error Detection Whitepaper.

    mbs.microsoft.com/.../NAVCostingErrorDetectionWP

    Could you detail the ID of the hotfix you referenced?

    Best regards, Christiaan.

  • Mutsa Profile Picture
    225 on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    Thank you for your  help. The AVCO setup has always been set by Item, Location and Variant.

    And also you said i should give you the ID of the hotfix I reffered to; the ID is 2845184

    Thank you.

  • DMV Profile Picture
    1,042 on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    So, is there any way to fix existing items with this issue?  The fix going forward is fine but, what do we do about the ones sitting on the Valuation report that are wrong?

  • Verified answer
    Community Member Profile Picture
    on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    Hi,

    The issue reported on KB2845184 is due when entries of an average cost item have been fixed applied by using the item application worksheet. After the application worksheet been used, the valuation date of the outbound item ledger entries has an incorrect valuation date.

    The fix, will avoid next time you use the item application worksheet to generated an incorrect valuation date.

    The issue was "The Valuation Date (outbnd) is not updated when new Valuation Date (inbnd) is an earlier date and Posting Date = Valuation Date.

    The solution was Valuation Date (outbnd) is also updated to earlier dates when the application is fixed between ILEs to ensure that Valuation Dates are in sync between inbnd and outbnd which is essential to calculate the correct unit cost for average.

    To correct the data, customers experiencing the problems caused by this issue can get into correct state by redoing the fixed applications in application worksheet after this fix is implemented.

    Hope this helps. Then again, having zero quantity and value on the inventory valuation report might have many reasons so even if you merge the KB the issue could 're-appear' due to other reasons. The same counts for options to rectify the existing data.

    Best regards, Christiaan.

  • Mutsa Profile Picture
    225 on at
    RE: Quantity is Zero but Value not zero in the inventory valuation report

    Thank you so much Chris and the rest of the team. I am anwered and I am enlightened in a lot of things as I read through your input. Thank you

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
Saurav.Dhyani Profile Picture

Saurav.Dhyani 2 Super User 2025 Season 2

#1
Alexander Ermakov Profile Picture

Alexander Ermakov 2

#3
RK-25090803-0 Profile Picture

RK-25090803-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans