Go to main content
1/11
Contents
Title and Copyright Information
Preface
Audience
Documentation Accessibility
Related Documents
Conventions
1
Introduction to Auditing Administration for JD Edwards EnterpriseOne
2
Preparing JD Edwards EnterpriseOne for Auditing and Electronic Signatures
2.1
Understanding Audit and Electronic Signatures Records
2.2
Prerequisites
2.3
Setting Up JD Edwards EnterpriseOne for Auditing and Electronic Signatures
2.3.1
Understanding Database Considerations for Auditing
2.3.1.1
Database Sizing
2.3.1.2
Table Conversions
2.3.1.3
Database Driver Considerations
2.3.1.4
RDBMS Interface Management
2.3.2
Understanding Database Triggers for Audited Tables
2.3.2.1
Oracle
2.3.2.2
DB2 for IBM i
2.3.2.3
IBM DB2 for LUW (Linux, UNIX, Windows)
2.3.2.4
SQL Server
2.3.2.5
Trigger Naming Conventions
2.3.3
Setting Up a Data Source for Audit Tables
2.3.4
Configuring an Oracle Database for Auditing
2.3.5
Configuring a DB2 for IBM i Database for Auditing
2.3.5.1
Deleting SQL Packages
2.3.6
Configuring a IBM DB2 for LUW (Linux, UNIX, Windows) Database for Auditing
2.4
Preparing an Auditing and Electronic Signature Configuration for a JD Edwards EnterpriseOne Upgrade
3
Setting Up Auditing and Electronic Signatures
3.1
Understanding Auditing and Electronic Signature Setup
3.1.1
Auditing for Interoperability Transactions
3.1.2
Audit Table Setup
3.1.3
Table Design Aid in Audit Mode
3.1.4
Tables Associated with Auditing and Electronic Signatures
3.1.4.1
Configuration Table (F9500001)
3.1.4.2
Reason Code Table (F9500002)
3.1.4.3
Audit Header Table (F9500003)
3.1.4.4
Audit Detail Table (F9500004)
3.1.4.5
Temporary Audit Table (F9500005)
3.1.4.6
Signature Table (F9500006)
3.1.4.7
Audit Table
3.1.4.8
Database Object Template Information table (F986112)
3.1.5
Table Date and Time Data
3.1.6
Table Naming Conventions
3.1.7
Electronic Signature Setup
3.1.7.1
Reason Codes
3.1.7.2
Electronic Signature Features
3.1.7.3
Considerations for Batch Applications
3.1.8
Electronic Signatures for Power Forms and Subforms
3.1.8.1
Embedded Subforms
3.1.8.2
Reusable Subforms
3.1.8.3
Examples of Electronic Signature Configurations on Power Forms and Subforms
3.1.9
Audit Records, Signature Records, and GUIDs
3.2
Enabling Auditing and Electronic Signatures for a Pathcode
3.2.1
Understanding the Auditing and Electronic Signature Configuration for a Pathcode
3.2.2
Setting Up an Audit Only Configuration for a Pathcode
3.2.3
Setting Up an Audit and Electronic Signature Configuration for a Pathcode
3.2.4
Modifying an Existing Configuration
3.2.5
Reviewing Configuration Changes
3.3
Setting Up Auditing
3.3.1
Understanding Auditing Restrictions
3.3.2
Configuring a Table for Auditing
3.3.3
Checking In an Audit Table
3.3.4
Modifying an Existing Audit Table
3.3.5
Verifying and Resetting Audit Tables
3.3.6
Copying an Audit Table Configuration
3.4
Enabling and Disabling Table Auditing
3.4.1
Enabling Auditing for a Table
3.4.2
Disabling Table Auditing for an Oracle, SQL Server, or DB2 for IBM i Database
3.4.3
Disabling Table Auditing for a IBM DB2 for LUW (Linux, UNIX, Windows) Database
3.5
Setting Up Reason Codes
3.5.1
Adding a Reason Code
3.5.2
Changing the Status of a Reason Code
3.5.3
Copying a Reason Code
3.6
Setting Up Electronic Signatures
3.6.1
Prerequisite
3.6.2
Setting Up Electronic Signatures for an Interactive Application
3.6.3
Setting Up Electronic Signatures for a Batch Application
3.6.4
Modifying an Electronic Signature Configuration
3.6.5
Deleting an Electronic Signature Configuration
4
Working with Auditing and Electronic Signature Approvals
4.1
Entering an Electronic Signature Approval
4.1.1
Understanding the Signature Approval Form
4.1.2
Using the Signature Approval Form
4.2
Removing Unmatched Audit Records
4.2.1
Running the R9500005A Batch Application to Remove Unmatched Audit Records
4.3
Viewing Audit and Electronic Signature Records
4.3.1
Prerequisites
4.3.2
Viewing Audit Information
4.3.3
Viewing Signature Information
4.3.4
Viewing Audit and Signature Information Together
A
Configuring Auditing for Interoperability Transactions
A.1
Overview
A.2
Reference Implementations for Auditing
A.3
Configuring a Published Business Service to Pass Audit Information
A.3.1
Overview
A.3.1.1
Using Reference Implementations to Test a Business Services Auditing Configuration
A.3.2
Configuring RI_AuditAddressBookManager to Pass Audit Information
A.3.3
Configuring RI_AuditInsertABStagingManager to Pass Audit Information
A.4
Configuring a Java Connector to Pass Audit Information
A.4.1
Overview
A.4.1.1
Example: Calling a Business Function with Audit Parameters
A.4.2
Reusing Audit Data for Multiple Business Functions
A.4.3
Reference Implementation Resources
A.4.4
Running the Java Connector Reference Implementation to Test Auditing
A.5
Configuring a COM Connector to Pass Audit Information
A.5.1
Example of a Generated COM Function Wrapper with Audit Parameters
A.5.2
Reference Implementation Resources
A.6
Configuring XPI to Pass Audit Information
A.6.1
Adapter Services for EnterpriseOne Business Functions: Auditing Configuration
A.6.1.1
Multiple Business Functions Within a Single Transaction in a Flow
A.6.2
Adapter Services for EnterpriseOne Database Operations: Auditing Configuration
A.6.3
Reference Implementation Resources
B
Setting Up Multiple Path Codes for Auditing and Electronic Signatures
B.1
Understanding Auditing and Electronic Signatures in Multiple EnterpriseOne Path Codes
B.2
Prerequisites
B.3
Creating Required Oracle Table Spaces and Users
B.4
Creating Julian and Non-Julian Database Data Sources for 21 CFR Part 11
B.5
Generating Tables for 21 CFR Part 11
B.6
Creating OCM Mappings for 21 CFR Part 11
B.7
Configuring an Oracle Database for 21 CFR Part 11
B.8
Configuring Auditing and Electronic Signatures for Multiple Path Codes
C
Troubleshooting
C.1
Audit Processing Error
C.2
SQL7032 Problems
Glossary
Scripting on this page enhances content navigation, but does not change the content in any way.