Re: Display-only access

[MacWheel99@xxxxxxx]

From Al Macintyre BPCS 405 CD mixed mode OS/400 V4R3

Depending on BPCS versions, there are options available, such as in the 
security secondary menu selections, to do stuff like this, but none of them 
are trivial to manage.  

Remember that there are programs like ACR310 INV330 etc. ... a whole bunch of 
inquiries already exist, and numerous reports, and while query/400 is not an 
efficient use of AS/400, if you can identify the end user needs, it may be 
simpler to create a new screen with the data they need, than be futzing 
around with 100 series programs.

Make sure that the folks, who have authority to change the data, are aware of 
the volume of folks who have authority to look at the data ... especially in 
accounting areas are folks who seem to be sensitive to other people viewing 
their data.

The simplest solution in my opinion is to clone the source code into 
something named like ACR3A, INV3A, etc. which would be an exact replica of 
ACR100, INV100 etc. except that some command keys have been disabled, then 
put the copied code onto one of the BPCS USER MENUS ... by sharing the 3 
letter prefix, anyone who could do anything in ACR or INV before can run 
these new ones ... but we are careful to use a naming convention on the rest 
of it that will not conflict with future SSA upgrades.

We also have scenarios in which we want certain individuals to be maintaining 
certain fields of item master, or certain sub-groups of item master but not 
the whole ball of wax ... what has happened is we have turn-over in some 
department & the person entering cost updates notices a field is apparently 
blank & starts using it for stuff that is meaningful to them, but that field 
is used elsewhere in BPCS & the fact that it is non-blank triggers effects we 
did not want ... so when we authorize access to item master for some 
department to be entering price or cost, or some specific thing, we do not 
want them to be accidentally field exiting through fields they do not 
comprehend.

Where we want some folks to only be updating a certain sub-group of item 
masters, where we are using some items to track some tooling, we could create 
a logical just over them, then have a CL like INV1TOOL to restrict access by 
tooling folks to the items they are supposed to be messing with.  Thanks for 
the question stimulating my brain cells ... I will suggest to my users that 
they make formal request that I implement this trivial modification.

Where we want some folks to only be updating a certain sub-group of fields, 
we could copy INV100 source code to INV1COST INV1PRICE etc. & change the DDS 
to block access to all fields except the handful allowed ... seems like a 
rather tedious modification to me, compared to the effort of end user 
training.

>  From:    mbazer@dynomerch.com (Mark Bazer)
>  
>  V6.0.02 m/m Jan 98 
>  OS/400 V4R4
>  
>  Is there a quick way to provide the "display" option and deny access to the
>  "revise" option to maintenance programs (ACR100, INV100, etc.)? We would
>  like to allow users from some departments to be able to use the display
>  function of the program for inquiry purposes, but only allow the department
>  that "owns" the module to have access to the maintenance function. 
>  
>  Mark Bazer
>  Dyno Merchandise
>  Pompano Beach, FL

Al Macintyre  ©¿©
http://www.cen-elec.com MIS Manager Programmer & Computer Janitor
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---