My Oracle Support Banner

E-PC: OPRID In Audit Tables Defaults to !NoOPRID Incorrectly When Auditing Table Updates In Integration Broker PeopleCode (Doc ID 2512042.1)

Last updated on JULY 21, 2020

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.

Symptoms


In 8.54, when using Authentication Token with SwitchUser, the AUDIT_OPRID field in the Audit tables fails to be updated with current ID. It doesn't update the AUDIT_OPRID with the Auth Token user ID, but fails and updates it with default User ID, if there is one. In the case of IB events it defaults to the ID of the node. When used in a code button event the user id defaults to !NoOPRID.


Due to this issue, The service operation PeopleCode correctly switches user and application row added and modified fields are set to the current authenticated user.

But, when the audit is triggered AUDIT_OPRID is set to the default user of the IB default local node. This is not big deal for table below, but it is problem with tables that do not have row added and row modified fields like PSROLEUSER..

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.