|
when we DSPJRN, we have to put a number on the ENTDTALEN the first time the outfile is created for each file. Then with a query we output just the JOESD field from that file to another outfile. Then CPYF this outfile to a duplicate of the CUSMAS (or whatever) file with option *NOCHK. Then this last file can be queried just like the regular file. Each record has an entry type for update before, update after, etc. this is found in the first output file from the DSPJRN command. There may be an easier, better way but this is how we look at the records so they make sense. Once you get it all working manuallly, you could write a pgm to do all the steps. You just need to be careful to not name your files the real Infor file name to avoid accidents. Ann -----Original Message----- From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]On Behalf Of Greg Wenzloff Sent: Wednesday, December 07, 2005 9:04 AM To: mapics-l@xxxxxxxxxxxx Subject: [MAPICS-L] MAPICS - customer master file - auditing Hello List, Our SOX auditors have said that we should have a way of detecting and approving all changes to the Customer Master file. I have set up physical file journal and can see the before and after images of the file's records. My question is how should I take that data and create a report that makes sense? Does anyone have something they would share? Other suggestions are welcomed. Thanks, Greg _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mapics-l or email: MAPICS-L-request@xxxxxxxxxxxx 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.