|
We have figured out how to pass the user name into the TRMID field (the old workstation ID field) in program AMI3H. If you create a field under the LDA data structure (you can call it anything you want), then you can move it to the TRMID field just before the program writes the record to IMHIST. This will work for transactions that flow through the Unattached Jobs also. One thing we haven't tried though are transactions flowing in from barcoding (ie. PM&C using TRDATA). Also be aware of other add-on packages that create MAPICS transactions, that they might not have all the information in the LDA parm (just enough to allow the program to run).
0101 I*-------------------------------------------------------------------AMI3H
0102 ILDA DS 1024 AMI3H
0103 I 245 245 APCOD AMI3H
M01A * user name from LDA parm
M01AI 277 286 @@USER
0103BI 464 465 APL2 AMI3H
0104 I 715 7338LPLCST AMI3H
0105 C******************************************************************* AMI3H
.
.
.
0624 C END AMI3H
M01A *
M01A * Replace value in TRMID with user name
M01AC MOVEL@@USER TRMID
0625 C* AMI3H
0626 C WRITEIMHISTF 90 AMI3H
P.S. We logged this as an incident with the folks at MAPICS and the person I spoke with said that they are getting more requests for this kind of tracibility and will talk to some people about it.
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
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.