Maximum Number of Orders that Sage 100 Can Handle

We are running MAS 200 Version 4.5 - non SQL version.

We are planning to upgrade to Sage 100 2014 before the end of the year.

I am trying to find out the maximum number of orders that MAS 200 / Sage 100 can handle per day, before I will see the performance issue.

If we are forecasting 100,000 orders annually, that will be 8,333 orders per month, less than 400 orders per month.

I want to know if there is anyone using the same version and is processing this kind of volume.

Thanks.

  • 0

    I have questions to qualify and education answer.  The biggest hurdle is how many transaction need to be posted at one time and how much history do need to keep?

    How many inventory items per order?

    Do you plan to post\update daily?

    How long do intend to keep history?

    How many user licenses?

    How many users in Sales Order at the same time?

    How many inventory items do you have?

    Order are imported correct?

  • 0 in reply to dskantor

    dskantor, please see below:

    How many inventory items per order? >>> It varies, it can be 1 item; it can be 50 items, or it can be as high as 100 items.

    Do you plan to post\update daily? >>> We have a habit to post/update on a daily basis, if there is no negative inventory.  Otherwise, it will be 1-3 days if there are any issues.

    How long do intend to keep history? >>> Under SO Options, we have it as 2 Years now.  Not sure if this settings is for closed orders.  We may not need that long, 1 year should be good too.

    How many user licenses? >>> We have total of 20 users licenses.

    How many users in Sales Order at the same time?  >>> About 5 users in SO at the same time, may go as high as 10 users in the future.

    How many inventory items do you have?  >>> We have about 6500 items setup - including both active and non-active items.

    Order are imported correct?  >>> Currently, no.  But we will be implement EDI capability.

    Thanks.

  • 0 in reply to Pak

    One Sales Order with one inventory item is completely different then one Sales Order with 100 inventory items. If you have 30 Sales Order per day with 100 inventory items each is completely different, that would be posting 3,000 items thought the system. Just keep that in mind.

    This will be find if have more than adequate recourse.  RAM, multiple processors, and very fast hard drives.  Fast hard drives help because of the writing to data to disk during updates. Accounting software has that issue with need to update transactions in large batches.  Get with your reseller or hardware guy to spec this out.  I would think about Solid State Drives too.

    This will be find if have more than adequate recourse.  RAM, multiple processors, and very fast hard drives.  Fast hard drives help because of the writing to data to disk during updates. Accounting software has that issue with need to update transactions in large batches.  Get with your reseller or hardware guy to spec this out.  I would think about Solid State Drives too.

    One caveat to this, there are many external items that creates poor performance.  Keep the workstations and server clean from external environmental factors that loads more programs.  Keep the systems off the internet and no downloading iTunes :-) and other such crap.

    I would be more concern about home much history will need to be stored.  For example transaction will be written to these files:

    AR_CustomerSalesHistory

    AR_InvoiceHistoryDetail

    AR_InvoiceHistoryHeader

    AR_InvoiceHistoryLotSerial

    AR_InvoiceHistoryPayment

    AR_InvoiceHistoryTracking

    AR_InvoiceTaxSummary

    AR_OpenInvoice - (Should only store 60 or 90 days)

    AR_TrackingByItemHistory

    AR_TransactionPaymentHistory

    CI_ItemHistoryByPeriod

    CI_ItemTransactionHistory

    GL_PeriodPostingHistory

    IM_ItemCustomerHistoryByPeriod

    IM_ItemTransactionHistory

    IM_ItemVendorHistoryByPeriod

    IM_ItemWhseHistoryByPeriod

    IM_LotSerialTransactionHistory

    IM_PeriodPostingHistory

    IM_PeriodPostingHistory

    RA_ReceiptsHistoryInvoice

    SO_ARInvoiceHistoryLink

    SO_InvoiceHistoryLink

    SO_LotSerialHistory

    SO_SalesHistory

    SO_SalesOrderHistoryDetail

    SO_SalesOrderHistoryHeader

    SO_SalesOrderHistoryPayment

    If you do see problems with excessive history Sage ERP has many purge selections.

    CI

    Menu=Utilities

    Purge Item History

    AR

    Menu=Utilities

    Purge Accounts Receivable History

    Purge Sales Tax History

    Remove Inactive Customers

    Remove Temporary Customers

    Remove Zero Balance Invoices

    AP

    Menu=Utilities

    Remove Temporary Vendors

    Remove Zero Balance Invoices

    Purge Accounts Payable History

    Purge Vendor 1099 Payment History

    Purge Sales Tax History

    Remove Voided Checks

    Purge Electronic Payments

    Purge Vendor Electronic Payment History

    Remove Inactive Vendors

    SO

    Menu=Utilities

    Purge Expired Orders/Quotes

    Purge Obsolete Sales Orders

    Purge Order/Quote History

    Purge Lot/Serial History

    Purge Sales History

    Purge Sales Order Recap

    PO

    Menu=Utilities

    Purge Completed Purchase Orders

    Purge Expired Master/Repeating Orders

    Purge Completed or Cancelled PO Recap

    Purge Obsolete Purchase Orders

    Purge Purchase Order Receipt History

    Purge Purchases History

    RMA

    Menu=Utilities

    Purge Expired RMAs

    Purge Return Reason Detail

    Purge RMA Receipts History

    Versioin 4.50 and 5.20 are pretty much the same.  5.2 will be slightly slower.  I would set up a test box load up 5.20 convert the data from 4.50 and start importing data and test it!

  • 0 in reply to dskantor

    dskantor, thanks to the detail information.  I have a better picture now on how files are 'process' behind the interface.  Does it make any difference between "30 Sales Order per day with 100 inventory items" VS "100 Sales Order per day with 30 inventory items"?

    Also, does it make any difference if it is running with SQL Version or not?  Will it write/read faster on SQL version or the non-SQL version?

    Thanks.

  • 0 in reply to Pak

    The client server non-SQL version processes faster.  

    1. Sage 100 Advanced (non-SQL)  processes fastest

    2. Sage 100 Premium (SQL) processes slower

    3. Sage 100 Standard processes slowest

  • 0 in reply to BigLouie

    BigLouie, we are running the first one in the list - Sage 100 Advanced.

    It looks like we have the 'fastest' edition of Sage 100 on processing.

    Thanks.

  • 0 in reply to Pak

    Here is link to differences between Sage ERP Advanced (PVX) and Sage ERP 100 Premium (SQL)

    sagecity.na.sage.com/.../84931.aspx

  • 0 in reply to dskantor

    dskantor, thanks for the information.

    We may need to replace what we are using now (Sage 100 Advanced (non-SQL) to something else.

    Sage 300 ERP / Sage 500 ERP / Sage ERP X3.  Any place where I can see their differences?

    Thanks.

  • 0 in reply to Pak

    Sure, at the Sage Summit you can see the differences first hand.  Here is the Cliff Notes version.

    Sage 300 is the old Acc-Pac about like Sage 100.  As for Sage 500, remember the movie Warm Bodies where the kid starts out as a zombie and becomes human at the end. Sage 500 is sorta like that. A few years ago Sage announced Sage 500 was dead and then recently they sent out the, well maybe coming back to life notice.  X3 is getting all the love and development right now. And How. So if you want a step up from Sage 100, go with X3 if it has the modules to handle what you need.