Inventory Valuation

SUGGESTED

Our Inventory Valuation has some issues.  If we run the Inventory Valuation with a start date after our 09/08/2014 period end date we get incorrect results.  If we start the inventory valuation from an earlier date (08/01/2014) it works fine.  After lots of review I am somewhat perplexed.  It looks like records in timInvtFiscPerHist for a given period should match the inventory valuation/balance sheet for the same date range (say 06/01/2014-06/30/2014).  But of course they don't.  I have traced quite a bit of code to see if I can find the issue and if I had to guess timInvtHist is bad. 

Anyone have any suggestions for research/fixes besides the standard rebuild utilities?  I have used these in an attempt to fix in the past and they did not work well. There isn't a design doc sitting around I could read to help me is there?  I'm thinking I might change the rebuild utilities to use a post date range for timInvtHist but I'm trying to avoid guessing or spending a lot of hours/brain power tracing more code.

Thanks for any help/suggestions.

John

  • 0

    We've had this same issue before and the problem was due to exactly what you discovered. What fixed it for us was to schedule a job that runs the following code every night just in case the history tables get out of sync during the day. I'd be curious to know if this fixes your issue too.

    /*
    This SP recalculates each inventory record's period history in timInvtFiscPerHist & timInvtCalPerHist.
    */
    
    SET NOCOUNT ON
    
    DECLARE @P1 int
    
    EXEC spimRecalcPeriodHist null, 2, @P1 OUTPUT
    
    IF @P1 = 1
    
    PRINT 'Recalculation Successful!'
    
    ELSE
    
    PRINT 'Recalculation Failed!'
  • 0
    SUGGESTED

    Hi John,

    This sounds like a support issue which might require a data fix.

    Please open a web case on support.na.sage.com, mention this thread.  You can also review and reference KB Article ID 56961 - Inventory valuation report is not consistent when ran for a single date versus a date range.

    While we can't verify that this is for sure something that would be resolved with a data fix, Sage support can review your issue and then make that determination.

    As a precaution we recommend that you test any data fixes in a test environment and have a verified back up before running fixes in your production environment.

    Thanks,

    Jennifer Pitt

  • 0 in reply to Jennifer Pitt

    Tim I manually fixed timFiscPerHist so didn't need the SP.  I'm going to review timInvtHist further.  I am not planning on calling support.  We are currently on 7.4 and I did call about it but felt it was better to review it internally.