During the payroll training this week their was a discussion about the general ledger accounts for earnings expense, tax expense and benefit expense being driven by a project. I was wondering if in the design, you will be supporting non-construction based projects or only the construction edition? From what was discussed, it sounded like these accounts would come from the cost centers, which I don’t think is part of the standard project edition. As a follow up, it would be helpful to provide some level of coding for “x” projects. If the accounts are going to be based on projects where do the non- project costs go?
Does anyone have a recommendation toward when to license Microsoft SQL Server per Cal verse per Core for a PCS Acumatica system. This customer would only be hosting the Acumatica database so I would think that one Cal per instance of Acumatica would be all that is needed. This assumes that users connect to the Acumatica web server and the server consumes one Cal as it connects to SQL. Can someone confirm this theory or make a recommendation. What other factors should we concider.Thanks
We would like to see the user profile enhanced to default values for the scan move process. Currently at a minimum it requires three scans to enter any move transaction. At one of our customer sites they only have one operation step so having to enter this information each time is a waste of time and has made the adoption rate of the application slow. If we could default the values for order type, operation number, and location based on the user profile that would save three steps. If you made this a preference to use default values from the user profile then this could be deployed in a number of cases. It would be very useful if all the possible default fields that are required by a hand held had the capabilities to default based on a user profile.
Our customer has started to use discounts extensively and originally we setup 6 decimal Price / Cost because it allowed us to match to the current price structure which is specific for almost each customer. We have learned that this causes rounding issues when unit of measure conversions are introduced. We have an opportunity when publishing the new price sheet to clean up some of this rounding by changing to a 2 decimal Price / Cost setting in Company miscellaneous settings. In our testing this appears to correct many rounding issues. Has anyone seen negative impacts in the transactions by reducing the number of decimals? All input is appreaciated.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.