My Oracle Support Banner

EAP: Payment Inquiry Ignores Row Level Security for Bank SetID (Doc ID 2936149.1)

Last updated on MARCH 19, 2023

Applies to:

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

Symptoms

Row Level Security is turned on for SetID by Permission List. However, when on the Payment Inquiry page, the Bank SetID still displays a SetID that that the User does not have permission for. Yet, if the User accesses the External Accounts page, the User is only able to see the SetID that he has permission for.

STEPS
1. Logged in as VP1
2. Navigate to Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences
3. User ID = VP1
4. Select the Overall Preferences link
5. On the User Preferences page:
    a. Business Unit is blank
    b. SetID is blank

6. Navigate to Accounts Payable > Review Accounts Payable Info > Payments > Payment
7. On the Payment Inquiry page, clicking on the magnifying glass for Bank SetID shows SHARE and SHR02
8. Navigate to Set Up Financials/Supply Chain > Security > Activate Row-level Security
9. On the Security Options page:
    a. Type of Security = Permissions List Level Security
    b. Secured Fields = SetID

10. Navigate to Set Up Financials/Supply Chain > Security > TableSet by Permission List
11. On the TableSet Security by Permission List page:
      a. Primary Permission List = ALLPAGES
      b. SetID = SHR02

12. Navigate to Set Up Financials/Supply Chain > Security > Apply Security Setups
13. Run Apply Security Setups
14. Display the Payment Inquiry page
15. Clicking on the magnifying glass for Bank SetID still shows SHARE and SHR02
16. Navigate to Banking > Bank Accounts > External Accounts
17. On the External Accounts > Find an Existing Value page, clicking on the magnifying glass for SetID shows only SHR02

NOTE: In the above replication steps, user details / customer name / address / email / telephone number represent a fictitious sample (based upon 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.