MO Security Profile not Enforced after Creation
Last updated on FEBRUARY 06, 2018
Applies to:Oracle Receivables - Version 184.108.40.206 and later
Information in this document applies to any platform.
On : 220.127.116.11 version, Transactions Related
Security Profile not enforced after creating new security profile or updating existing security profile in HRMS
For e.g., you expect Security profile to include 2 Operating Units, but it it not working in Transactions form.
You still see old behaviour.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms