My Oracle Support Banner

EGL9.2:Journal Audit Log Reports Multiple CREATE Event Code When Journal is Imported and Re-Imported with Some Field Value Changes. (Doc ID 2889246.1)

Last updated on AUGUST 26, 2022

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Journal Audit Log reports multiple CREATE Event Code when journal is uploaded using Spreadsheet Journal Import, and then, re-imported with some field value changes.
For example:  The imported journal is uploaded with incorrect Department values, and using the same template, corrected these values and then re-imported.

Steps to replicate:

 1.  Enable Audit Logging for all GL JOURNAL events.
     (Set Up Financials/Supply Chain > Common Definition > Audit Logging > Enable Audit Logging)
 2.  Enable Journal Approval at Ledgers for a Unit page:
      Business Unit = US001
      Ledger Group = RECORDING
     (Set Up Financials/Supply Chain > Business Unit Related > General Ledger > Ledgers for a Unit)
 3.  Prepare JRNL1_WS template:
     - Enter required fields in Define Options and Defaults.
     - Enter Journal Header and Lines details, then Import.
     - Journal ID 0000000741 created.
 4.  Check Audit Logging for the Journal ID 0000000741.  Event Code CREATE has been logged.
     (Set Up Financials/Supply Chain > Common Definition > Audit Logging > Search Audit Logs)
 5.  Run Edit Journals (GL_JEDIT) process.
     (General Ledger > Journals > Process Journals > Edit Journals Request)
 6.  Access journal in Create/Update Journal Entries.
     (General Ledger > Journals > Journal Entry > Create/Update Journal Entries)
 7.  Check Audit Logging for the Journal ID 0000000741.  Event Code EDIT has been logged.
 8.  Go back to the template for Journal ID 0000000741, change the DeptID from 14000 to 10000, then import.  It updated the same journal.
 9.  Run Edit Journal Request process.
10.  Access journal, change has been reflected.
11.  Submit journal for approval.
12.  Log in as approver, click on Approvals tile.  Approve the journal.  Journal was approved.
13.  Access Audit Log, and note that transactions done to the journal have been reflected.  
      Note that with every upload, even if it was to update the existing journal, CREATE event code was added.
14.  Tried again for the 2nd time for the same journal, updated DeptID in the JRNL1_WS template from 10000 to 2000, and import.

See replication here.

NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample (based up made up data used in the Product name test environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.