The accounting code is for use in the Job accounting Journal QACGJRN
logging job statistics when a job ends.
This journal doesn't keep entries for changes made to objects.
You need journal the objects you want to monitor in a separate journal
or use an existing. The USER is stored in the journal entries, and by joining to
the user profile you get the accounting code.
Brgds
Helge
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Åke Olsson
Sent: Friday, January 15, 2010 11:07 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Accounting code and journaling
We have a request from the auditors it goes as follows:
They want to be able to see in the database journal any changes that were related to a "change request" i.e. all database updates
performed by people in IT operation and support. The basic idea is that way the can follow up on grounds of "who did what to this
record and why?" The who is the userid that already is in the journal entries. The "why" is the problem part.
Our starting point was that we should set the accounting code of the job to the change request- id that we started working on and
hopefully that this accounting code would make its way into the journals. A lot of other job information is in there so why not
this?
Apparently the accounting code does not get journaled automatically.
Should it? Will the journaling behavior change if we also start the accounting journal? (Not active at the moment).
Med vänlig hälsning / Best regards
Åke H Olsson
Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11
This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please
notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is unauthorized and may be illegal.
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.