What is the context Shiyaz? If it is for a PSO testing purpose, it is quite easy. But it is not quite easy if you want to duplicate both sides (PSO-FSM). 

Basically we have 1 Access group in FSM and 1 Dataset in PSO, In current dataset we are having more that 30K tasks , so we plan to split 1 Dataset to 2 dataset..

Keeping the 1st Dataset as is & will be creating New dataset and moving some of the resources & task from 1st dataset to 2nd dataset but is it possible to copy the same dataset and duplicate all the data as is, then we can do cleanup of unwanted data, is that possible in Production.

our Major concern is if we add new dataset then we need to assign Rota for all the Field technician manually, we are having almost 150+ Field technicians, which is really a tough task.

In another ways if duplication is not possible, is there any way to copy the exisiting assigned ROTA and assigned to new dataset.

Regards,

Shiyaz

Okay. Understood. From FSM side, you need to assign the moving resources and tasks to a different team and connect that team to the new dataset.

But the Rota details will not be moving and you will have to do it manually because when using ARP, PSO will be considered as master system for Resource data and the team/dataset change you did in FSM is not reflecting in PSO. Unfortunately, doing this manually is not too easy.

• Delete entries in THREESIXTY_RAM_LOAD_HISTORY table for old dataset, delete the existing dataset in PSO and create 2 new datasets (One with your existing ID and other one with new ID). Now the Resources will be split into 2 datasets but you don’t have shifts. You can construct a XML with existing shift details via an export of current ARP file and import them using Import function in Resource Planner (6.12 version onwards) or else using Modelling API. This method would be less prone to errors than splitting your ARP manually. 
• Without recreating 2 datasets, you can create only the new one but then you will have to selectively delete the Resources from old ARP and remove related entries selectively in THREESIXTY_RAM_LOAD_HISTORY table. I believe this will be time consuming.