In this article we will look into the most frequently asked question of how to migrate the Table based Value Sets, Fast Formulas, Lookups, Payroll Flow Patterns etc.
We cannot migrate Table based Value Set and Payroll Flows using any means except this method.. For HCM Extracts, we can do export and Import, for Fast Formulas we can use HDL and bulk loading for Lookups.
Table of Contents
Application Implementation Consultant role is required to access this functionality.
Instructions to Migrate objects:
Let’s look into step by step on how to do this migration in Source and Target.
Login to Source POD.
Navigate to Setup and Maintenance
From Right hand side menu click on Manage Implementation Projects
Create Implementation Project
– Choose Create
– Update the Project Name if desired
– Select ‘Save and Open Project’ to proceed
– Click the Create icon
– Click the Add icon
– Set the Search drop-down to Tasks, and search by Task Names:
Payroll Flow Patterns
– Highlight the result
– Click on Apply then Done
– Click the Done button
Add the Extract, Value Sets, Fast Formula tasks
For Valuesets and Lookups we need to select the module specific task instead of the generic tasks as we cannot select the scope for these objects. We will get to know what is scope in the later part of this article.
Generic Tasks – Manage Value Sets, Manage Common Lookups
Module Specific Tasks –
Manage Value Sets for Global Human Resources – It will export all the Value Sets with module setup as Global Human Resources
Payroll Value Sets – It will copy all the Value Sets with module setup as Global Payroll
Click on Done after adding all tasks that needs to be migrated.
Now, get back to Setup and Maintenance
From Right hand side tasks, select Manage Configuration Packages
Click on New to create a new config package
Now select the previously selected project “Test Project“
Click on Next again
New screen will show up with the list of all objects that will be migrated as per the list of tasks that we have selected in the Implementation Project.
Now, select the business object “HCM Extract Definition“
Click on + for scope and search for extracts and click on Add. Whatever object names we add to the scope, only those will be migrated. If you don’t include anything in scope, then all extracts will be migrated. Make sure you select the right scope for the migration to happen seamlessly. When we add scope for the extracts, the other objects dependent on extracts like extract attributes, data groups will also get extracted as per the scope defined for HCM Extracts object.
So the extracts which have been added to the scope will only be migrated as part of this package.
Note: If you don’t add any scope, then all extracts will get migrated and it might cause issues with unwanted extracts getting migrated or not so tested extracts getting migrated and would land you into trouble. So keep note of the scope and use it effectively.
Now, we need to add the scope for Value Sets, Lookups, Fast Formulas, etc.
For Lookups and Valuesets, we cannot define the scope.. So we need to use the right task like Manage Value Sets for Global Human Resources or Payroll Value Sets etc.
We can set the scope for only the core tasks like “Fast Formula, Payroll Flow Definition, etc.” and automatically the scope will be set for the dependent tasks like “Fast Formula Function, Payroll Flow Task Payroll Flow Definition Parameters, etc”.
We also need to set the scope for Payroll Flow Definition and select the Payroll Flow that needs to be migrated.
Once the scope is set for all tasks, click submit
Click on Yes when it prompts for do you want to continue.
Wait for the process to complete and then you can download the Configuration Package by clicking the Download Icon. This Config package of zip file contains all the data that we have exported now.
We need to import this package into the target environment to migrate the objects.
Now, Let’s login to Target POD
Navigate to Setup and Maintenance > Manage Configuration Packages
Click on Upload to upload the config package.
Click on Choose File and browse for the zip file on your local machine and then click Get Details.
We can verify the configuration package details and then click submit.
Once submitted, it will upload the package and then we will have to import it.
Select the Project and Click on “Import Setup Data” which will take us to the next screen.
Click on Submit to start the import process.
We have to wait for the import to be successful. Once is is successful, we can go to respective tasks and verify the objects.
We can also download the log files and the import report if the import is not successful to identify the cause and fix it at source/target.
For Fast Formulas, they need to be compiled in target POD once migrated.
For HCM Extracts, they need to be compiled and validated in target POD.
Note: Make sure the Source and Target PODs (20B or 20C or whatever) are at same patch level before migrating the objects using this approach as there might be difference in the features and the migration might fail.
Video on Cloud Customer Connect explaining the migration process – https://ora-fusion-apps.custhelp.com/euf/assets/fusion/videos/replays/303800/presentation.html
Hope this helps when you have a requirement to migrate the configuration changes from one POD to another.
Top 10 Popular Posts from our Knowledgebase
- DataFusing FREE Cloud based SQL Developer like tool for Oracle Cloud
- Core HR Entity Relationship Diagram (ERD) for HCM Cloud
- Most Frequently used Document IDs from Oracle Support
- FREE Oracle Training & Accreditation with Oracle Learning Explorer
- How HDL Transformation Formula works with ElementEntry Sample
- FREE Oracle Fusion Demo Instance (VISION) Access
- Top 10 FREE useful tools for Fusion Consultants
- Learning Fusion HCM Technical Skillset
- Sample HCM Data Loader (HDL) files for all Business Objects
- Most frequently used Tables list in Fusion HCM