My Oracle Support Banner

EBI 9.2: Audit Logging Functionality Is No Longer Keeping Track of Event Code COPY for Invoice Transactions Created Using the Copy Single Bill Feature After Systems Upgrade (Doc ID 3046394.1)

Last updated on SEPTEMBER 15, 2024

Applies to:

PeopleSoft Enterprise SCM Billing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

It has been detected that after a system's upgrade to PeopleSoft Enterprise FSCM 9.2 PUM Image #48, the delivered Audit Logging functionality no longer is recording the Event Code of COPY for those Invoice transactions created in the system via the Copy Single Bill feature, if the original transaction got created after such mentioned upgrade. If the originating Invoice existed prior to the system's upgrade, the COPY Audit Logging is properly recorded.

Analysis determined that the wrong codeline may be contained within Component PeopleCode COPY_BILL.GBL.SavePreChange.

REPLICATION STEPS:

  1.- Log into the FSCM Online Application as a System Administrator.
  2.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Audit Logging > Enable Audit Logging > Enable Audit Logging
  3.- Open the Application Name of Billing.
  4.- Ensure to select the below options:
        - Copy Billing Invoice
        - Create Billing Invoice Online
        - Edit Billing Invoice Online
        - Finalize Billing Invoice
  5.- Save the changes.
  6.- Log into the FSCM Online Application as a Billing User.
  7.- Navigate to: Billing > Maintain Bills > Standard Billing
  8.- Create a brand new Invoice transaction, and set it into RDY status.
  9.- Navigate to: Billing > Generate Invoices > Non-Consolidated > Single Action Invoice
  10.- Define a new Run Control ID with the criteria of Business Unit and Invoice pointing to the newly created transaction, and launch the BIJOB03 PSJob.
  11.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Audit Logging > Enable Audit Logging > Search Audit Logs
  12.- Under Application Name Billing, perform a search for the Invoice transaction recently created, and click on SEARCH button.
  13.- Confirm that the system has recorded several Events such as CREATE, EDIT, and FINALIZE.
  14.- Navigate to: Billing > Maintain Bills > Copy Single Bill
  15.- Define the Business Unit, and the Invoice ID of the transaction previously created, and click on SEARCH button.
  16.- At the Copy Single Bill page, select the Copy Bill radio-button, leave the Copy Bill column as NEXT, and define an Invoice Date.
  17.- Save the changes.
  18.- This generates a new Invoice ID, which has been copied from the original transaction.
  19.- Navigate to: Billing > Maintain Bills > Standard Billing
  20.- Open the newly copied Invoice transaction.
  21.- Set the status to RDY (Ready), and save the changes.
  22.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Audit Logging > Enable Audit Logging > Search Audit Logs
  23.- Under Application Name Billing, perform a search for the copied Invoice transaction, and click on SEARCH button.
  24.- PROBLEM: Confirm that the Audit Log has not recorded the Event COPY that generated the new Invoice from the original transaction.

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the problem.

The Audit Logging is not keeping track of new Invoice transactions generated in the system using the Copy Single Bill feature, which causes confusing when audits take place, as creation of such transactions is not being recorded.

The Audit Logging should add a new row with Event COPY for the Invoice transaction created as a copy of an existing one, as it used to, before the system's upgrade.

NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

 

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
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.