At this time, it is not on our detailed list of features. Meaning, it isn't in the next release. After that, we don't have many features at that level of detail.
So why would Sage go through the effort of creating this table, and adding it to the schema browser, if they weren't going to actually implement it into the software?
We ran into an issue where a prospect wanted GL security by account and since MAS 500 didn't have it they went with another application. When we spoke to Sage at that time, they indicated it was a feature that had been requested before. So seeing this gave us hope.
Contains the list of GL Account Segment Values (including the natural account segment) that are valid for each user group. This is used to determine if a user (within a certain user group) has the authority to enter the segment value as part of a full GL account in a transaction. Also determines if a user can inquire on a full GL Account that contains the segment value.
Hi Dawn - I have a MAS 500 client where this is an issue (lack of GL account level security). Were you ever able to develop or find a solution to this issue? Basics like allowing only certain users to hit the AP account via GL transactions is what they are looking for. Any ideas would be greatly appreciated. Thanks!
This isn't the best solution, but we created a nightly SQL job that compares the balance in the Accounts Payable module to the balance in the Accounts Payable GL account. If they don't agree, an email is sent out. So, while it doesn't prevent the two from getting out-of-sync, at least we know within 24 hours of when it happens.
Tim Rodman Programmer Analyst rodmant@robbinstbm.com Version 7.30.6.0 (March 2011)
