|
I know from experience that if a sub-system posting ends up in maintain events and is corrected by someone else at least the HHUSER field is changed. Gord -----Original Message----- From: rfolsom@xxxxxxxx [mailto:rfolsom@xxxxxxxx] Sent: Tuesday, May 20, 2003 7:38 AM To: SSA's BPCS ERP System Subject: Re: How to check Who posted an event? Eric: The fields are certainly there, HHUSER, HHDATE and HHTIME. Our database has no records without the user field filled. If you check XRF you can see which programs use these fields. It would take some more research to see if the fields are updated on every change, because sometimes BPCS doesn't update all the fields, but you could at least know which user did something to the record. Rick Folsom Yupo Corporation America 757-819-9230 "Eric Tam" <eric-tam@xxxxxxx To: <bpcs-l@xxxxxxxxxxxx> om> cc: Sent by: Subject: How to check Who posted an event? bpcs-l-bounces@xx drange.com 05/20/03 05:16 AM Please respond to "SSA's BPCS ERP System" Dear all, We are on ver 6.1. Is it possible to check by whom and when an event was posted? Are there any fields in GHH for holding such info? Thanks in advance for any suggestion. Best regards, Eric _______________________________________________ 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. _______________________________________________ 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.
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.