Access and Control Files

[Chris Kelleher]

Hi Peggers,

I would like to know--especially, from a system admin's stand point--as far as security and access, do you normally allow your end-users to have access to any control files in MFG/PRO?

Thanks for your feedback,

Kacee

 

[Chris Kelleher]

Kacee
As a good practice it would be wise to deny access to the end users.

 

[Chris Kelleher]

At my company, only IS has access to the control files. IS includes the
business analysts that implemented the system. It was our responsiblity to
look at the system as a whole and decide the best way to set up the control
files. Most users are concerned about just their area, not the system as a
whole. By denying access, we ensure that the control files don't get
changed without our knowledge. It leads to a more stable, predictable
environment. As business practices changes, we could make changes to the
control files after extensive testing.

--Peggy Harris
IS Business Analyst

 

[Chris Kelleher]

Most of the information on the control files should be restricted. However,
sometimes the user needs to change some fields (the next invoice number, and
next purchase order, for example) and for that reason, sometimes we give
them a program that lets them modify ONLY that field, instead of giving them
access to the whole control file (they can make a truly mess).

For those curious about this:

In Mexico, the invoice number should be kept carefully, so they have to make
sure it prints correctly, and take the next invoice number from the printed
format. The printed form invoice number and MFG/PRO invoice number have to
match.

Greetings.
Armando Franco.

 

[Chris Kelleher]

The way we handle this issue is through MFG/PRO security administrator. If
any changes are required with any of the control tables, the I/S expert and
security administrator will review with the requestor and then recommend
necessary action. It works in our environment.

that's all folks!

Karim
----------

 

[Chris Kelleher]

Kacee,

I have a simple rule when it comes to granting access to anything:

You can touch what you can fix, should you happen to break it.

For that reason, I would typically *not* allow access to *any* control
files (or menu x.25 programs) to anyone except those who really need it.
And I'd have a good discussion with them before I granted them access to
ensure that they understood any implications of their access.

That being said, most folks (in my experience) are happy to work through
this kind of environment.

Good luck.

Scott
===============================================================
Scott M. Dulecki /* 1998061901 */ +1 616 975 6322
Product Manager scott_dulecki@qad.com
QAD, Inc. http://www.qad.com
1188 East Paris SE Grand Rapids, MI 49546 USA

Next Michigan Progress Users Group: 19 January 2000
Next Midwest MFG/PRO Users Group: 13-14 March 2000

All opinions are my own, and don't necessarily reflect those of
any other living being.
===============================================================

 

[Chris Kelleher]

Thanks, Everyone, for responding. I wanted to get feedback from you all to see if we are "in line" with what other companies are doing--and we are.

Again, thank you, for your feedback!

Kacee