In this routine you create the basis for the data base audit management in your system. Make sure that nobody else is using the system when you start the function for any new files, since the files must not be open if they shall be activated. The direct print routine will automatically be cancelled when you open the routine.
Data base audit management is a tool for controlling changes of your master data. You can through this routine analyse the changes, additions and deletions that have been made in the files. Which files and fields for which changes shall be logged is entirely user-defined.
An example is to log the payment terms for a customer and the bank account number for a supplier in the Business partner file. All changes are logged together with the user id of the user who made the change, the date and time of the change, and the value before and after.
This panel displays the libraries for which data base audit management is active in your system. You can add, change or delete entries in the table.
Selection fields
DB audit – library table maintenance (JRND0013)
On this panel you define for which libraries the data base audit management shall be active. If Type of audit is set to 1 or 2, the name of the journal and journal receivers for each library must also be defined. The panel is only displayed when you add a new library to the the table.
Function keys
Maintain files table | Opens the routine for maintaining files in the selected library for which the data base audit management should be active. |
Create journal/receivers | Only displayed when Type of audit is set to 1 or 2. Creates the journal and journal receivers. |
- Library
- This field is used only for new entries and is only displayed when Type of audit is set to 1 or 2. You enter the name of the library for which a journal and journal receivers shall be created.
- Journal
- This field is used only for new entries and is only displayed when Type of audit is set to 1 or 2. Enter the name of the journal in which the log entries from the files in this library shall be created and stored.
- Receiver 1
- This field is used only for new entries and is only displayed when Type of audit is set to 1 or 2. Enter the name of the first journal receiver that shall receive the transactions. The system automatically switches between the two receivers when the log entries shall be created.
- Receiver 2
- This field is used only for new entries and is only displayed when Type of audit is set to 1 or 2. Enter the name of the second journal receiver that shall receive the transactions. The system automatically switches between the two receivers when the log entries shall be created.
- Aux. storage pool ID
- This field is used only for new entries and is only displayed when Type of audit is set to 1 or 2. If your iSeries uses auxiliary storage pools, a pool id can be entered in which the journals and receivers will be stored. If not, enter *LIBASP in this field. The journal will then be stored in the same storage pool as the library which is logged.