Considerations for Flow Migrations

Use the Export Setup Data and Import Setup Data processes to migrate payroll flows and the related setup data from one environment to the other.

For example, you have a unique payroll process requirement for which you want to configure a payroll flow pattern. Configure the flow pattern and set up the dependent payroll objects in the source environment first. Confirm that the flow runs successfully and meets the requirements, before you deploy it onto the target environment.

When you use the Export and Import Data Setup processes to migrate flows from one environment to another, both the source and target environments must be at the same release levels. The process includes these two steps:

1. Export a configuration package from a source environment to your local computer.

2. Import the configuration package from your local computer to the target environment.

Subsequent to the migration, if you make further changes to the original flow, you must repeat the process of migration. Incorporate the changes to the original flow in the source environment, verify that the changes work successfully, and then migrate the flow into the target environment.

Implementation Project

Create an implementation project, and create the setup objects required for your flow. For example, if you include a payroll report in the flow, you need to set up the balances, balance groups, and so on to run the report successfully within the flow. You may also need other related components for the flow, such as, formulas, parameters, value sets, and so on.

The tasks in your implementation project and their sequence determine the list of setup business objects whose data is exported and imported, and in which order.

Configuration Package

After you create the implementation project, you create a configuration package to generate the ordered list of business objects for export and import.

A configuration package is the medium used to move setup data from one environment to another. You create the flow pattern in a source environment, which is generally a test environment. The payroll flow you set up on the test environment includes several payroll tasks and you require the business objects associated with those tasks to successfully run the flow.

Along with the flow, you may want to export any dependencies such as formulas, reports, value sets, lookups, flow parameters, flow setup tasks, and so on. You create a configuration package to include all of these dependent components in the configuration package and export it simultaneously on to your local computer.

The configuration package also migrates any predefined roles and privileges. However, it doesn't support the migration of flow owner type and flow owner details at the flow level. You will have to update this flow information in the target environment after the migration is completed.

After you export the configuration package, download the package as a Zip file to your local computer, and then import the same Zip file into the target environment. Use the same setup data to run the flow in the target environment.

Offerings and Functional Area

When you create the configuration package, select the Offerings and Functional area as given here:

• Offerings: Workforce Deployment

• Functional Area: Payroll

Use this selection to limit the setup tasks and setup business data to a specific offering and functional area. Use the same values when you export and import the configuration package.

Scope

When you create the configuration package and select the Objects for Export, select the Payroll Flow Definition and select the created flow pattern name as the scope for the export process. The configuration package you create contains only the setup data that matches the Scope criteria you select. This limits the setup data you export.

User Role

You must have an Implementor role to create the setup business objects and an Administrator role to migrate flows.

For more detailed information on data migration refer to the Using Functional Setup Manager guide on the Oracle Help Center.