ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Suggestions for Updates >> Menu Access Changes
http://www.istechforum.com/YaBB.pl?num=1106756958

Message started by John Bierrie on 01/26/05 at 08:29:18

Title: Menu Access Changes
Post by John Bierrie on 01/26/05 at 08:29:18

Would like to see more of a break-out in giving access to individuals for certain functions. At present, Purchasing is able to put in Vendor information, Name, address, remit-to address, etc., etc., similar with Sales and customer information. Of particular concern is the "remit to" and other (similar) sensitive information that should not be able to be changed by someone who can enter in the basic info to begin with. Or, another possibility, it should not be able to be entered / changed without a password or some other blaring reminder that something "odd" is being done.

Two issues related to why this is being asked for:

Somehow a remit to address was changed in our system (no one remembers doing it) and checks went out to the wrong vendor. The checks were cashed by "someone else" and no one knows why the address was changed.

Second: With the remit to address being "secure", it makes it that much more difficult for someone to create a "false" vendor / customer and enter bills, etc.

We want purchasing / sales to put in the "basic" information, but until approved, not let the system generate a sales order, puchase order, etc., etc., against it.

There are probably a few other, related / similar items that would be good to sparate out so the functions can be a "check & balance" for the company.
Thanks

Title: Re: Menu Access Changes
Post by aricon on 01/26/05 at 10:36:52

John,

Simply put, there is NO way to do field level security (which is what you are asking for) in DBA.

And if there was a reasonable practical way to do it, the programming cost would be too great for any of the DBA clientele to swallow. Just would not happen.

I would suggest you look into other solutions that offer such functionality as this, such as:

Microsoft Small Business Financials

Best Software BusinessVision 32

Netledger NetSuite

You might also look at:

BusinessWorks

Cougar Mountain

ACCPAC Discovery Series

Just an idea. ;D

Title: Re: Menu Access Changes
Post by Lynn Pantic on 01/26/05 at 10:50:27

If you are only looking at AR-A and AP-A, the programming involved wouldn't be that much. Just a matter of defining what fields to control and how to control them - password or a separate entry screen.

Title: Re: Menu Access Changes
Post by aricon on 01/26/05 at 11:13:40

Lynn,

My point is that it is NOT a case of just AR or AP. It is a global issue. The architecture would need to drastically change to really deal with this properly. You know that so I am singing to the choir I suppose.... ;)

Title: Re: Menu Access Changes
Post by Lynn Pantic on 01/26/05 at 13:14:23

Can we say Evo? User defined screens are just one of the potential capabilities of the Evo interface, it is just a matter of getting a large enough user base to justify the programming effort. Master file entry screens such as AR-A, AP-A and IN-B are logical first candidates.

Title: Re: Menu Access Changes
Post by aricon on 01/26/05 at 17:35:59

Totally agree! Of course you know that. The EVO OOD capabilities do allow such. But the key is "it is just a matter of getting a large enough user base to justify the programming effort"......

Based upon what exists today and in the near-term forseeable future, there isn't a large enough base, nor is there the revenue potential from said base to make it fiscally feasible.

That is all I was getting at.

Title: Re: Menu Access Changes
Post by lmk223a on 01/27/05 at 05:55:15

I second John's request for controlled access to AP-A.

We have many cases where someone (i.e. purchasing, receiving, whoever) changed the "REMIT TO" address in the vendor file such that it is a weekly routine to manually verify each check address with the invoice before mailing AP checks.

It is a nice feature that in AP-B and AP-C that the remit to address is shown, but that does not prevent someone from changing this address before the vendor's check is printed.

???

Title: Re: Menu Access Changes
Post by kevind on 01/27/05 at 09:44:46

Maybe a resonable amount of effort could be expended to have a different menu selection to edit / maintain the critical information like REMIT Address, GL account number, and anything else that if changed causes hardship. Kind of like the menu entry that allow MRP paramiters to be edited, but nothing else.

There could then be an AP-A option in the ISTECH settings that would flag these fields as View Only in the AP-A or CM-E Screens.

Better yet, how about just making the CM-E screen Read-Only for these critical Fields. In my situation here, I would only allow AP-A access to Accounting people. I would allow CM-E access to sales and purchasing people so that they could enter just enough info to complete a Purchase order.

Title: Re: Menu Access Changes
Post by Tammy on 06/16/05 at 06:16:38

I like kevind's idea

Title: Re: Menu Access Changes
Post by Lynn Pantic on 06/16/05 at 08:55:16

There are already AR-Q and PO-P programs that are view only of customer and vendor information.