Audit Reports in PeopleSoft

For truly understanding the purpose of the peoplesoft audit reports, it is required to back-track a little to recall on what kind of data will be available in the peoplesoft database. 

The peoplesoft database is basically a combination of three layers, 

1. The Database System tables.

2. The Peopletools tables.

3. The Peoplesoft application tables.

The database system tables consists of all the system metadata and the core tables which is required for the proper functioning of the database.

The peopletools tables is populated during the creation of the peoplesoft application. These tables generally start with a PS*** example PSOPRDEFN.

The application tables are also created during the implementation phase of the application. The type of application tables depends upon what kind of data is imported such as it could be HRMS, FSCM and so on. These tables begin with a PS_*** example PS_JOB.

Now that we are clear on what kind of data the Peoplesoft database is composed of we can move on to learn about the peoplesoft audit reports.

Audit reports are generally used pre or post an upgrade or any changes in the application. This is used to check the sanity of the database. The below listed are the reports which are available for use.

1. Alter Audit

2. SYSAUDIT 

3. DDDAUDT

The alter audit is not a process, it is created using application designer by filtering all the records that will be required to be part of this audit and then using alter options as alter in place and building the selected objects with execute and build options. This will help to understand which all tables require an alter to be processed in the database.

The sysaudit is used to check all the orphaned objects which are present in the database. For example there could be a piece of peoplecode which is not being referenced anywhere.

The dddaudit is an sqr program which is used to check the differences in data between the system tables and the peopletools and application tables.