|
Forwarded by moderator for Tim Strange <tms@westernenterprises.com>: *************************************** Why not restrict User Id's to device ID's. We have chosen to only allow users to sign on at their terminal or CA session only. So when we look at Imhist we know who performed the transaction. Of course this only works if users do not share their passwords. -----Original Message----- From: Shannon, George [mailto:GShannon@bdfusa.com] Sent: Friday, June 30, 2000 8:55 AM To: 'MAPICS-L@midrange.com' Subject: RE: attaching the userid to inventory batches We have the same problem here. We are looking to be audited by the FDA and one of our accountabilities is to trace back transactions to the operator. The Operator ID on the inventory batches does not get logged on the transactions neither. Therefore we are looking to modify AMI3H (program which adds records to IMHIST) to populate the user id in the WSID field on IMHIST. -----Original Message----- From: ChrisGinaNeely@aol.com [SMTP:ChrisGinaNeely@aol.com] Sent: Thursday, June 29, 2000 10:48 PM To: mapics-l@midrange.com Subject: attaching the userid to inventory batches I am trying to find a way to attach the user ID to inventory batches instead of the job name (qpadev0008 for example) so that we know who entered the batch. Has anyone else had a need to do this? What was your method? Thanks Chris +--- | This is the MAPICS Mailing List! | To submit a new message, send your mail to MAPICS-L@midrange.com. | To subscribe to this list send email to MAPICS-L-SUB@midrange.com. | To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dshaw@spartan.com +---
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.