My Oracle Support Banner

Are There Any Options to Implement Core Row Level Security on Fields where Prompt Tables Are Not Delivered with Views Combining with SJT Tables? (Doc ID 2968342.1)

Last updated on AUGUST 21, 2023

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


Looking for options to implement core row level security on fields where prompt tables are not delivered with views combining with SJT tables.
The fields are Company, Business Unit and Department ID.

While creating new positions, prompt tables behind Business Unit, Company fields does not have SJT tables combined, hence does not restrict values based on core row level security that’s set up.

For e.g:
Business Unit field while creating a new position.
POSITION_DATA_E.BUSINESS_UNIT field on POSITION_DATA_FL page uses a prompt record of  BUSUNIT_HR_VW.
BUSUNIT_HR_VW is not joined to any SJT tables as delivered.

Is there any other delivered approach instead of using a custom view of BUSUNIT_HR_VW that joins with SJT tables?



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

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