Sage 100

 View Only

  • 1.  Error in Recalc Item History utility

    Posted 03-17-2023 15:29
    • Error 32 CI_CostRecalc_Upd.pvc; Line 1161; Class:  CI_CostRecalc_upd; Method:  ProcessTranForItemHistory  Last File:  CI_ItemHistoryByPeriod
    • Error 43 IM_ItemValuationChangeREg_Upd.pvc; Line 805; Class:  IM_ItemValautionChangeREg_upd; Method: Check for Restart

    I'm working with a client that has a "troubled past"; data wise, with Sage 100. Average Cost for most items, lot's of problems with the items going negative, on occasion the average cost was very large numbers and negative.  And a total network failure a few years ago that they choose to piece together themselves instead of involving Sage or their reseller.  Recently upgraded from v2016 (Advanced) to v2022 (Advanced); on their way out of the Sage 100 world.  They will move to SAP in 5-6 months, but need inventory to be at standard unit cost. 

    Found about a dozen items in Inventory Valuation Change Utility that warned there was an out of balance between cost and warehouse tables; removed those items from maintenance.  Don't get a warning or an error, but still can't proceed because of these errors when it gets to recalculating item history.  I can see the item code failing, end, clear restart file and start again, and fail on the very next on in the item listing.  Tried to Run Cost Commit Clear Utilities and then the rebalance utilities.  Errors in Recalc Item History.  Then tried doing it in fresh copy of the company skipping the cost commit utilities, running just Balance Inventory Quantity and Cost Utility, the same problems.  

    I will go to Sage about the error unless someone can see what maybe be wrong from those messages. 

    My Question.   I'm never going to have good inventory transaction history for these average unit cost items. They probably will never balance.  Any suggestions other than 1) do inventory physical count to set quantity on hand for all items to zero.  2)  purging item transaction history  3) set new standard unit cost correctly 4) do physical count process to bring counts in at Standard Unit Cost, properly? 



    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------


  • 2.  RE: Error in Recalc Item History utility

    Posted 03-23-2023 11:47

    x-ref to Sage KB - Error 32 CI_CostRecalc_upd.pvc 1161 when changing from Fiscal to Calendar Year in Inventory Options and clicking Accept if Production Management is not installed

    Summary
    Error 32 CI_CostRecalc_upd.pvc 1161 when changing from Fiscal to Calendar Year in Inventory Options and clicking Accept if Production Management is not installed

    Cause
    Scanco P/M or O/M was activated at one time, which created older "JI" Inventory Transactions, but since Sage P/M is not installed, Sage 100 displays error message when encountering these older "JI" Inventory Transactions.

    Resolution
    Sage Engineering is currently reviewing this issue.


    Workaround:

    Install Sage P/M or purge the older "JI" Inventory Transactions



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    Moodus, CT
    ------------------------------



  • 3.  RE: Error in Recalc Item History utility

    Posted 03-23-2023 11:53

    Little bit more information, I meant to come back and post after conversation with Sage and email with @Jane Scanlan  The problem happens for all clients that have also OWNED JobOps for many years, and have "only "used JobOps (Operations Management).  Karen at Sage was able to duplicate in her OM Install with Demo Data.  The programs error out on Recalc Inventory, or on Inventory Valuation.  Obviously, the two work arounds from Sage don't work.  Can't install PM and Can't Remove JT history from clients using that module.  Just go to Development yesterday, no ETA for a Fix yet.  



    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 4.  RE: Error in Recalc Item History utility

    Posted 03-29-2023 08:47

    Just an Update.  Sage provided a legal document for my client to sign which will provide them a "hot fix" for this problem, pre-release.  It is in development and ETA for release is by end of week/early next week.  Again, this is in v2022, client can not run Recalc Item History or Item Valuation Change Utility if they own JobOps (Operations Management); the business code assumed all 'prior Jx" transactions would be converted to Sage PM files, and "forgot" about the Operations Management files?  If you experience the same and need my case number, let me know.  



    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------



  • 5.  RE: Error in Recalc Item History utility

    Posted 02-27-2026 15:38

    Madeline,

         Our customer (JobOps) vs. 2022 is experiencing those errors also.  Do you still have the case # for Sage, or docs Sage sent?



    ------------------------------
    Lee Graham
    Friendly Systems, Inc.
    ------------------------------

    Original Message


  • 6.  RE: Error in Recalc Item History utility

    Posted 02-27-2026 15:58

    Coincidentally, Phil just posted this error Wednesday: JobOps Item History recalculation error 32



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------

    Original Message


  • 7.  RE: Error in Recalc Item History utility

    Posted 02-27-2026 17:00

    @Lee Graham  I think my case number was:  8009577922

    Notes
    04/13/2023          18:13:51            KSMCWHIR
    EXTERNAL EMAIL from Madeline Stefanou:
    Received.  Thank you.  I will put it in place and give it a test.  I am on PTO tomorrow, so probably next week.
    ___________________
    Notes
    04/13/2023          13:34:07            KSMCWHIR
    ==OUTBOUND EMAIL==
    Madeline:
    Please rename the existing MAS90/CI/CI_CostRecalc_upd.pvc program and replace it with the attached corrected program.
    Please let me know if this does not resolve your error.
    ____________________
    Notes
    04/04/2023          13:16:28            KSMCWHIR
    ==OUTBOUND EMAIL==
    Madeline:
    I just wanted to give you an update on the Pre-Release fix for this issue.
    I checked with Engineering today and they said the error has been fixed and tested on version 2022.3.  The next step will be to create the Pre-Release for 2022.2 and they expect they should be able to have that this week.
    ____________________
    Notes
    03/28/2023          11:53:59            KSMCWHIR
    Signed PRA attached
    Waiting on program fix from Engineering.
    ___________________
    Notes
    03/28/2023          11:40:41            KSMCWHIR
    EXTERNAL EMAIL from Madeline Stefanou:
    Thank you.  I have sent this to Client, and hope to get the signed copy back in a day or two.  They are owned by a large corporation, and I believe they need legal review before signing this document.
    Again, thank you for your assistance in our problem.
    Madeline
    ____________________
    Notes
    03/27/2023          13:48:09            KSMCWHIR
    Madeline:
    I am expecting the availability later in the week of a pre-release fix for the Error 32 CI_CostRecalc_upd.pvc 1161.  I have attached a Pre-Release agreement for your customer to review, sign and return to me if they would like the fix once it is available.
    ____________________
    Notes
    03/23/2023          13:46:27            KSMCWHIR
    Discussed in DRC that customer would like pre-release as soon as one is available.
    ____________________
    Notes
    03/22/2023          17:05:43            KSMCWHIR
    Advised Engineering findings:
    The problem is caused by the following:
    JI transactions exist (whether that's from having O/M or previously having O/M or P/M)
    PM is not installed.  (PM_WorkTicketHeader does not exist)
    Engineering is working on issue.
    She said customer needs fix ASAP as they are planning to update to Standard Cost by end of quarter which is 3/31/23.
    ____________________
    Notes
    03/22/2023          13:03:48            KSMCWHIR
    Advised the issue has been reported to Engineering and it has to do with JI and JR transactions existing and Production Management is not installed.
    This customer does have Operations Management installed and still getting the error when recalculating item history.
    Tested on my 2022.1 VM and I could duplicate the error.
    Advised I will let Engineering know.
    ____________________
    Notes
    03/22/2023          12:49:32            KSMCWHIR
    Error 32 CI_CostRecalc_upd.pvc 1161 when changing from Fiscal to Calendar Year in Inventory Options and clicking Accept if Production Management is not installed
    https://support.na.sage.com/selfservice/documentLink.do?externalID=119030version=2&language=en_US
    ____________________
    Notes
    03/21/2023          18:48:27            51906AA2D21
    Error 32 CI_CostRecalc_Upd.pvc; Line 1161; Class:  CI_CostRecalc_upd; Method:  ProcessTranForItemHistory  Last File:  CI_ItemHistoryByPeriod
    Error 43 IM_ItemValuationChangeREg_Upd.pvc; Line 805; Class:  IM_ItemValautionChangeREg_upd; Method: Check for Restart
    Trying to change from Average Unit Cost to STANDARD Unit Cost.  Getting this error.  Ran the Cost Commit Utilities and the Item cost to warehouse balance utilities.  Also got this error when trying to recalculate item history.
    Client has used JobOps (Operations Management); for many years.  WAS on v2016 and this process all worked fine in a test company in v2016 without issue.  Now upgrade to v2022, and we have this problem.



    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 8.  RE: Error in Recalc Item History utility

    Posted 03-03-2026 10:11
    Madeline,
       Thanks - Not optimistic about a 2023 Sage case #,  but I will check with Sage.

    Lee

    On 2/27/2026 5:00 PM, Madeline Stefanou via 90 Minds, Inc. wrote:
    0100019ca11dc94f-11e3e6fa-07bd-4fc9-bf56-732d64edc49a-000000@email.amazonses.com">
    @Lee Graham I think my case number was: 8009577922 Notes 04/13/2023 18:13:51 KSMCWHIR EXTERNAL EMAIL from Madeline Stefanou... -posted to the "Sage 100" community



    Original Message


Related Content