Preparing an Auditing and Electronic Signature Configuration for a JD Edwards EnterpriseOne Upgrade

Before upgrading to a new version of JD Edwards EnterpriseOne or applying software updates that contain table changes, you must turn off the auditing and electronic signature functions. JD Edwards EnterpriseOne must be made unavailable to users, and all the audit tables and configuration tables (F9500001 through F9500006) must be archived.

Note: Audit history will not be migrated when JD Edwards EnterpriseOne is upgraded. You must reconfigure the table audit and electronic signature settings.

1. Make sure that users are signed off from the JD Edwards EnterpriseOne installation that is configured for auditing and electronic approval.

2. Create a backup of the tables that are being audited, shadow audit tables, and auditing configuration tables in a different data source.

3. Manually remove any custom database views or triggers.

   If a custom table trigger already exists, it will be deleted when auditing is enabled or disabled.

4. Disable auditing using the Configuration Application (P9500001).

   This application performs these functions:

   • Drops native database triggers on Fxxxx_ADT.

   • Drops database view Fxxxx.

   • Drops CFR columns for Fxxxx_ADT.

   • Renames Fxxxx_ADT to Fxxxx.

5. Perform the JD Edwards EnterpriseOne upgrade.

6. Enable auditing using the P9500001 application.

   This application performs these functions:

   • Renames target table to Fxxxx_ADT.

   • Adds CFR columns to Fxxxx_ADT.

   • Creates database view Fxxxx (original structure)

   • Creates native database triggers to Fxxxx_ADT.

     Note: Remember that before you enable auditing, you must perform certain tasks on the JD Edwards EnterpriseOne servers and database servers, as previously discussed in this chapter.

7. Recreate and manually enable the custom database view or triggers removed in step 3.