|
Lloyd, Here is another idea for you to think about. We actually provided this level of security in R2 of XA in the mid 1990's. With the additional user exits it will be easier to control. You didn't mention what level of XA you were on, but consider doing the following: 1) Create a new Warehouse security file. The record will only need two fields: UserID and warehouse code. - Create a maintenance program that will allow easy selection of ALL warehouses, then allow the user to deselect any warehouse(s) the user they are working with (allow them to deselect more than one at a time for ease of use). - Also allow the user to add just one at a time to the file if they want. - If possible, provide a copy option on the screen so a new user can easily be set up in the file. 2) Using the user exit at the header and at the line item level, check to see if the userID has the authority to the warehouse selected. Do not allow them to continue until the warehouse code has been changed to a code they are authorized. You will need to consider Quotes and Credit Memos in this design if you are using them as well. 3) If you are using CSM, yes it is easier to set up the security, but as we all know - R6.5 does not have all the function in it to allow full order entry. Most users still need access to the "green screen" versions to finish up an order that was entered through CSM. >From someone that has done this requirement, this is the cleanest way to >control warehouse security. There is even a requirement in the MAPICS Caliber >tool that requests this level for warehouse control through COM/CSM. However, >they may not have the resources to provide this as an enhancement, nor feel it >is a priority for the customers. Hope this information is helpful. Sincerely, Paola Groeber MAPICS Consultant (Former Application Manager/Business Analyst of COM/CSM & other CRM applications) > > From: DaleGindlesperger@fft-inc.com > Date: 2002/12/17 Tue PM 10:58:29 EST > To: mapics-l@midrange.com > Subject: Re: Component sales to Contract Manufacturers-AGAIN > > > Lloyd, > > I can only think of three ways to accomplish what you want to do, if I > understand your requirements. One, set up the user defaults in COM to the > CM warehouse, then (shudder) modify the COM order entry header screen to > protect the warehouse field. That would automatically set specific users > to the desired warehouse and they wouldn't be able to change the warehouse > ID. If you have sufficient discipline, you could skip the modification of > the COM Order Entry header screen. > > Of course, if you use CSM, you could do the same thing, and by modifying > the panel (VERY easy!) you could protect the field without doing any RPG > coding or MAPICS mods. Much safer, much easier. > > Another alternative would be to use COM_Net to enter the orders. That has > a built in capability to lock users to a specific warehouse. The biggest > problems there are: > > 1. If you don't own COM_Net already, it's a pretty expensive solution to > this particular problem (although it sure can add a lot to your business! > But that's another story and issue). > > 2. You lose a lot of entry capabilities, like terms override, > non-inventory items, AR due date, and such. But it sure is fast! > > Is this what you are looking for? > > Dale Gindlesperger > Fleetwood Folding Trailers, Inc. > > > > > > LDEGNON@AMPRO.COM > Sent by: To: MAPICS-L@midrange.com > mapics-l-admin@mi cc: CFRANK@AMPRO.COM, >SMARKS@AMPRO.COM, > drange.com RECKELS@AMPRO.COM, >LD'ANNA@AMPRO.COM > Subject: Component sales to >Contract Manufacturers-AGAIN > > 12/17/02 08:43 PM > Please respond to > mapics-l > > > > > > > *********************************************************************** > I am posting this again in hopes that I have worded it differently and > it now makes more sense. > *********************************************************************** > > > We have what I'm hoping is not a unique problem. > > Here at Ampro 99% of our manufacturing is done by CM's (Contract > Manufacturers). > > Often times, when components are going end-of-life on one of our products, > we > buy up large amounts to satisfy pending orders. > > We then need to sell these to our CM's. > We have a separate Warehouse to run picks, seperate Backlogs,using > Warehouse to > keep > them off of Customer Sales Bookings and Backlog reports. > > Does anyone know of a way in which to restrict, on a per user/group level, > COM order entry by warehouse. > > The goal being to not allow certain users/groups to enter/maintain orders > against > our Primary selling warehouse, and only to the warehouse in which we stock > these > "stockpiled" items? > > Any other thoughts?? > > > Any Ideas??? > > Lloyd H. Degnon > I. S. Manager > Ampro Computers Inc. > 5215 Hellyer Ave > San Jose, CA 95138 > 408.360.4365 > Ldegnon@ampro.com > http://www.ampro.com > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list > To post a message email: MAPICS-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > > Received: from linux.midrange.com ([207.224.38.113]) by NIXON.AMPRO.COM > with > SMTP > (IMA Internet Exchange 3.14) id 000D9026; Thu, 5 Dec 2002 11:36:07 -0800 > Received: from linux.midrange.com (localhost [127.0.0.1]) > by linux.midrange.com (8.11.6/8.11.6) with ESMTP id gB5JYDa09599; > Thu, 5 Dec 2002 13:34:13 -0600 > Received: from NIXON.AMPRO.COM (nixon.ampro.com [206.79.158.100] (may be > forged)) > by linux.midrange.com (8.11.6/8.11.6) with ESMTP id gB5JTI808562 > for <MAPICS-L@MIDRANGE.COM>; Thu, 5 Dec 2002 13:29:19 -0600 > Mime-Version: 1.0 > Message-ID: <000D9020.C22269@AMPRO.COM> > From: LDEGNON@ampro.com > Subject: Component sales to Contract Manufacturers > To: MAPICS-L@midrange.com > Content-Description: cc:Mail note part > X-MailScanner: Found to be clean > content-transfer-encoding: 7bit > content-type: text/plain; > Sender: mapics-l-admin@midrange.com > X-BeenThere: mapics-l@midrange.com > X-Mailman-Version: 2.0.13 > Precedence: bulk > Reply-To: mapics-l@midrange.com > Date: Thu, 5 Dec 2002 11:25:30 -0800 > X-Spamscreen: Protected by WatchGuard SpamScreen (TM) > v6.1.B1000 Copyright (C) 1996-2002 WGTI WGTI > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list > To post a message email: MAPICS-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > > > > > > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list > To post a message email: MAPICS-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.