According to recent market surveys 75% of the businesses are in their journey of digital adoption. Covid Pandemic has acted as an accelerator for digital adoption across the globe, with special focus on cloud platforms and solutions. Among all the cloud platforms, Oracle cloud plays a significant role in this due to its high performance, centralized data security, quick deployment, and instant business continuity. For the high paced world there is always a demand for fast-track Implementation. One of the key considerations in every implementation is data security and process controls and how to have a hustle free migration across environments.

The need for accelerated migrations:

The best way to handle business specific controls and segregation of duties in Oracle ERP Cloud is through custom configurations of access roles. This brings in the need for custom roles and custom Data Security Policies (DSP). Even though they are adaptable enough to fulfill client requirements, recreation of the underlying roles and DSPs in every environment through the implementation is a cumbersome activity. This triggers the need for quick and easy role and DSP migration across environments, a migration that is efficient and repeatable.

The traditional approach:

The traditional way of migrating Roles and DSP have been manual and bulky and at times prone to manual errors.

The need of the hour is a more efficient and a repeatable solution using best-in-class features of Oracle that is a combination of an Implementation project and configuration package. Throughout all the phases of an implementation, this combination is a powerful tool for custom role and DSP migration.

The process:

Firstly, it is important to understand the key objects or tasks that would be part of the implementation project which are as below

1. 1. Manage Job Role
   2. Manage Data Security Policies

Create an implementation project which consists of the above task list. These limited number of tasks ensures that no other objects or tasks in the system are impacted by this migration.

Sample Illustration: Implementation project to be created

Secondly, a configuration package must be created which will hold the Implementation package created with Job role and DSP task lists.

Sample Illustration: Configuration Package

Third step would be to export the configuration package from the source environment to the target environment. Using this approach, the efficiency of migrating roles and DSPs can be dramatically increased.

Key callouts:

• Scope can be defined for the custom roles. If no scope defined, all the custom roles would be migrated.
• Duty roles and Seeded roles cannot be migrated using this approach. We can consider leveraging a dummy Job role to migrate the duty role.
• This specific feature does not support migration of user role assignments. HCM data loader tool can be leveraged for this time-consuming task.