My Oracle Support Banner

AP9.2.After Applying Fix for Bug 33898534,Fields OPRID_LAST_UPDT, LAST_UPDATE_DT and LAST_UPDATE_DTTM from Voucher Information Page Are Not Updated with Approver's Action Time and ID (Doc ID 2934311.1)

Last updated on MARCH 12, 2023

Applies to:

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

Symptoms

After applying the fix for the bug 33898534, and after the approver is approving the voucher, the fields OPRID_LAST_UPDT, LAST_UPDATE_DT and LAST_UPDATE_DTTM are not updated with the approver’s action time and approver’s ID on Voucher Information Page ( PS_VOUCHER record).

Issue can be replicated following next steps :

1.Enable Voucher Approval for AWE on Payables BU Processing Option for BU US003- Setup Financial/Supply Chain>Business Unit Related>Account Payables>Payables BU Processing Options

2.Go to PeopleTools > Utilities> Administration> Manage TableSet Controls for Set Id : US003 .Update the  Set control value of US003 Record group AP_01  to US003

3.Login as VP1

Create Voucher for BU: US003. Do not Submit for Approval online.

4.Check the Values of the fields SES_LAST_DTTM , OPRID_LAST_UPDT , LAST_UPDATE_DT , LAST_UPDATE_DTTM in PS_VOUCHER Record.

5.Run Budget checking

6.Login again with approver user VP2 and run Process Batch Voucher Approval.

7.The fields SES_LAST_DTTM ,OPRID_LAST_UPDT , LAST_UPDATE_DT and LAST_UPDATE_DTTM have been updated correctly in PS_VOUCHER Record.

8.Login with MGR3 and approve the voucher.

9.Check the voucher summary page.Notice that the fields Last Update and Modified by are not changed.

10.Check the fields in Voucher record. Notice that fields OPRID_LAST_UPDT,LAST_UPDATE_DT, LAST_UPDATE_DTTM have not been updated with approvers ID and time of action as SES_LAST_DTTM.

In the example above, user details/company name/address/email/ telephone number all represent a fictitious sample from the Oracle Demo Vision Database.
Any similarity to actual companies or actual persons, living or dead, is purely coincidental and is in no way intentional on the part of Oracle

Changes

 n/a

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.