Last updated on JUNE 28, 2017
Applies to:Oracle Demantra Real-Time Sales and Operations Planning - Version 12.2 and later
Information in this document applies to any platform.
On an SSO enabled instance, Demantra user is not getting removed for future end dates of APS Demantra responsibilities. Please note that the user is being removed successfully for past or current date but just not for future dates.
Test Case Steps:
1) Enable SSO
2) Assign Demantra responsibility to the user USER1, now user USER1_SOP is created in USER_ID table in Demantra
3) End date Demantra responsibility for future (Example: Start Date - 04-APR-2016, End Date - 06-APR-2016)
4)Now check this user in USER_ID table on 07-APR-2016. The user user1_SOP still exists in Demantra.
But the expected result was, this user should have been removed from Demantra once the Demantra Responsibility was disabled.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms