Item Valuation Report

Hi All,

Please note that in recent days few of our clients are coming up with queries as the Standard Item Valuation report in Sage 300 is taking too long to generate. Majority of our clients use the WS Setup while a few of them use remote connection to use sage.

Some clients are on Sage 300 2019, 2020, 2022, 2023 and 2024. The database size ranges from 25GB to 80GB and one client has a DB size of 240GB.

Has anyone also faced the same issue? How do we go about resolving the issue and making the Item Valuation report faster?

Thanks in advance,

Dhiraj

Parents
  • 0

    Hi Dhiraj, 

    You can try using the non-datapiped item valuation report.

    the ODBC reports are labelled "icvalun1 , icvalun2, icvalun3, etc"...

    To enable the non-datapiped (ODBC) form, you need to edit the ICRPT.ini file located in the ICXX program folder.

    edit the ini in Notepad.. and search for ICVAL01

    edit the following

    Change 

    type=DATAPIPE to type=ODBC

    and Crystal=ICVALU01 to Crystal=ICVALUN1

    Save the file and then close and re-open the IC Item Valuation screen.

    Repeat the same for the other reports 

    ICVAL02, etc

    Regards,

    DCrampton

  • 0 in reply to DCrampton

    Hi DCrampton,

    Thank you for the response.

    Please note that i have tried the above as you had advised. However, i do not notice any difference in the time it takes to generate the report before and after making these changes.

    Is there anything else i can try?

    Do i have to reboot the server after making the changes?

  • 0 in reply to Dhiraj Kumar

    I haven't looked at the existing report but if I recall it starts at 0 and works it's way through all of the transactions up to your cutoff date. David can correct me if I'm wrong.

    If you're good at Crystal, the faster way to write this report is to write a report based on ICILOC which has "today's" values. Then, use a sub-report to sub the net change in the ICHIST table back to the date you want to report on. Be sure to pass ItemNo, AcctSet, Location, FiscYear, and FiscPeriod to the sub-report as that will allow SQL to find that set of records quickly. (Edit: Acctset isn't required as there is a key on Itemno, Location, Fiscyear, Fiscperiod)

    Most of the time you're going back to a period of time that's a few months ago or maybe to the beginning of the year. Rather than processing 5.5 years of transactions per item, you can just process 0.5 years of transactions which is 1/10 of the processing power required so your report will run 10 times faster.

    If you can leverage the power of your database engine, you'll have a report in your hands very quickly.

Reply Children
No Data