E-SEC: Migration of Roles Results in Orphaned Permission Lists
Last updated on FEBRUARY 17, 2016
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.53 and later
Information in this document applies to any platform.
When migrating roles from one environment to another, if the role definition in the source environment contains permission lists that do not exist in the destination environment, then the migrated role will contain references to the permission list that does not exist.
1) Create custom permission list in environment A
2) Associate custom permission list to delivered role
3) Migrate role from environment A to environment B through App Designer database to database migration
4) In environment B, the freshly migrated role will contain references to the orphan permission list
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