process. Here is how we close.We have 477K records in the inventtrans
table.No development except for a modification where the Inventory
that was financial by batch was not closing. This was a problem since
SP1 and the 24-30 hours was based on SP1 with the modification we
have. MBS has corrected this in SP3 so we will remove our
modification when we put SP3 in production.
You must also set the following in Classes\InventCostItemDim\Class
Declaration #Define.commitCountMax(100000000) otherwise you may
receive an error and have to cancel the close.
We have also set our non-inventory items to FIFO. In our case, the
non-inventory item cost is not being used. So by setting the not used
items to FIFO will help too.
When we close, I take the AOS down and run in two tier with two
clients running the close. One client from a server(AOS server) & the
other one a desktop. If you run multiple PC's you must have
comparable speed on each. And if you have too many running, you will
overload the SQL server and slow the process down. Our biggest slow
down with SP1 was the TTS Commit of such a large transaction.
We are on SQL 2000 sp3a, Compaq ML530 with 2-933mhz processors, 3GB
RAM, 100MBS network, 15K Ultra SCSI drives (# for OS, 2 Mirriroed for
log & 6 for Database Raid 5)
Another item that may help is if you run the InventSettlement
summary. In our test environment, we reduced the number of records in
the InventSettlement table by over 15 mil records & reduced the
database size by 5gb. We plan on summarizing our settlement
transactions in production within the next month. If you do it, I
would recommend only doing 3-6 month period at a time. This process
creates another large ttscommit and will greatly affect your SQL
server performance.
Hope this helps.
Best Regards,
MB
--- In [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
> We have Axapta 3.0 using date weighted average and the process
inventory
> closing have problems with overflow in the table inventsum.
>
>
>
>
>
>
> "mblevinsus" <[EMAIL PROTECTED]>
> 07/04/2004 08:33 AM
> Please respond to
> [EMAIL PROTECTED]
>
>
> To
> [EMAIL PROTECTED]
> cc
>
> Subject
> [development-axapta] Re: [tadorna-axapta] Speeding up Inventory
Closing
> (in Axapta 2.5)
>
>
>
>
>
>
> We had the same problem with version 2.5. The slow down is usually
> caused by using date weighted average costing. When we upgraded to
> 3.0sp2, the problem was greatly improved. We went from 24-30 hour
> close to 20 minutes. I don't know if yours would be that drastic,
but
> it is definately worth the look at the upgrade, and go with 3.0SP3.
> We are working on our SP3 upgrade now.
>
> If you are using date weighted average, you should also take a look
> at the inventsettlement table. It will grow very fast and will
> greatly increase the size of your database. In 3.0SP2, they have
> improved & added a summary feature to reduce the number of records.
>
> Probably not the solution you were looking for, but I hope it helps.
>
> Regards,
> MB
>
> --- In [EMAIL PROTECTED], "Arkadiusz Zimniak"
> <[EMAIL PROTECTED]> wrote:
> > Hallo,
> >
> > I have problems with inventory recalculation speed for Axapta
2.5.
> I have
> > found
> > mails below so my question: is the hotfix25-004 part of
> ServicePack4 for
> > Axapta 2.5
> > or should I install it anyway ? Are there any other possibilities
of
> > improving
> > performance ? Is it normal to have 24 hours of recalculation
after
> 3 months
> > of
> > using Axapta (about 100 concurent users) ?
> >
> > Best regards
> >
> > Arkadiusz Zimniak
> > Integris Pozna�
> > tel./fax +4861 8681533, +4861 8681549
> > e-mail: [EMAIL PROTECTED]
> > http://www.integris.pl
> >
> >
> > -----Original Message-----
> > From: Andrew Besedin [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, September 05, 2002 3:26 PM
> > To: ptomaula2
> > Subject: Re: [tadorna-axapta] Speeding up Inventory Closing (in
> Axapta
> > 2.5)
> >
> >
> > Hello!
> > At the www.partnerguide.com you can find and download a HotFix25-
004
> > which speeds up an inventory closing process.
> >
> > Regards,
> > Andrew Besedin,
> > Byte, Barnaul, Russia
> > [EMAIL PROTECTED]
> >
> > p> Hello,
> > p> Does somebody got some experience with running the Inventory
> Closing
> > p> in Axapta 2.5 ?
> > p> At a customer the run lasted more then 10 hours.
> > p> After consulting on the Service System-site I found a document:
> > p> "Performance Considerations, Navision Axapta Inventory
Closing".
> > p> (Document ID AX-250-TIP-001-v01.00-ENUS).
> > p> In this document they " pinpoint set up combinations that will
be
> > p> especially harmful for performance and recommend alternatives
or
> > p> restrictions that would smooth out the most problematic
> situations."
> > p> After reading en executing the recommendations we still got a
> running
> > p> time of more then 10 hours for the Inventory Closing.
> > p> My question now is:
> > p> - Does anybody got more advice to speed up the Inventory
Closing
> > p> or do we have live with this problem and wait for version 3.0
in
> > p> which encreased speed will be offered on Inventory Closing.
> >
> > p> Thanks in advance !
> >
> > p> Pieter Tomaula
> > p> Pulse Automation Experts bv
> > p> The Netherlands
> > p> Mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >
> >
> > p> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
>
> Yahoo! Groups Links
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
