× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: User transactions tracking in BPCS v4
  • From: pluta@xxxxxxxxxxxxxxxxxx
  • Date: Wed, 22 Sep 1999 11:49:00 -0500




Al,
thanks for your input. I am going to try to be more specific on the needs I have
and explain the context.
In fact I am IT auditor and I would like, during audits, to be able to know for
certains critical transactions (like posting invoices, creating customers...)
who has created the document (like who has posted the invoice number 999999 the
22/09/1999...).
Now in case of fraud for instance, it is not possible to find out who keyed the
transactions in BPCS.
What I would like to work out is a tracking mecanism that would add a user ID to
the document created for critical transactions, and that would not be too much
resource consuming.
Any idea on how to do that? Thanks for your help.
----------

Zahouani, this might be a good time to investigate database triggers.  Depending
on what you want to do, you can either update a field in the record itself, or
you can modify a secured database file with the apporpriate information (who
update the record and when, for instance).  This way, you can implement your own
journaling techniques.


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.