Re: Restricting Inventory Transactions

Tom,
 
When restricting users to inventory transactions, the follwong occurs:
 
1.  There users will only see the transactions that they have access to in 
INV500, PUR550 and DRP550.
2.  Removing the B transaction from the users valid transaction effects has no 
impact on their execution of Pick Confirm.
3. Within inventory inquiry (INV300) the users see everything in the display 
panels.

________________________________

From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx on behalf of 
Molyneux, Tom
Sent: Thu 1/25/2007 8:32 AM
To: SSA's BPCS ERP System
Subject: [BPCS-L] Restricting Inventory Transactions



We are on V6.04, July Cum.

Up to now, we haven't tried to restrict a user's access to selected
Inventory Transactions when we set up a user in SYS600. We have used
menu restrictions to restrict what our users can do. But we would like
to investigate the possibilities.

What are the ramifications of doing so?

I'm not sure what happens if, for example, we take away a user's
authority to do "B" transactions but leave "Pick Confirm" on their menu.
If they run Pick Confirm, which generates "B" transactions, does it bomb
out or not start at all ?

When doing Inventory enquiries, does the user still see transactions of
types that they aren't authorised to ?

I'm sure Infor will have thought this through and it will hang together,
but I want to be sure before we start restricting users in this way.

Any advice gratefully received.

Thanks in advance.

Tom Molyneux

National Oilwell Varco
Mono Pumps Limited
MIS Department

Tel.      0161 214 2142
Fax.     0161 214 2344
E:mail  Tom.Molyneux@xxxxxxx
            tmolyneux@xxxxxxxxxxxxxx

--
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.

Delivered-To: dsweeney@xxxxxxxxxxxxxxxx