Ideas for Acumatica

Important! Please note that we do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive.
This portal is for product ideas and feedback only. If you need customer service assistance, please contact your Acumatica Support Partner or submit a support case.  You can also get assistance from community resources:  LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal. 

Give us some kind of SQL query environment.

We need the ability have read only access to the Acumatica tables but the ability to create temporary and permanent tables for manipulating data.  We need a looping mechanism found in SQL environments to make multiple passes at the data.  Currently Acumatica doesn't have any way to create a fully costed multi-level BOM report.  This is a killer issue for manufacturing companies.  SQL would allow us to create a fully costed multi-level BOM report.  We also don't have a way to show net change open order results from one day to the next.  Again, SQL would give us the ability to determine what net changes are made to a company's open orders for any given time period.  Major ERP systems have these types of reporting systems.  Acumatica is woefully deficit without this kind of reporting tool.

  • Guest
  • Oct 25 2018
  • Rejected
  • Attach files
  • Douglas Johnson commented
    April 26, 2019 12:58

    We do not plan to grant direct access to the database for our SaaS clients, but private cloud clients can get access to their database server.

    Caution: direct access to SQL allows customers to bypass security settings that are enforced when reporting data is retrieved using internal Acumatica reporting tools such as the Generic Inquiry writer.

    Recommendation: if you have specific issues for manufacturing reports, I would recommend creating a separate issue.