How to automatically deep copy ETL job?

[former_member747985]

I have an ETL job in Data Services Designer that I need to make a complete but independent duplicate of. The job has several hundred reusable pieces, so it'll take a while to replicate all of those reusable pieces. Is there a way to deep copy a job automatically?

[lenastodal]

Welcome and thanks for visiting SAP Community to get answers to your questions. While you're waiting for help, check out our tutorial to get started in SAP Community: https://developers.sap.com/tutorials/community-qa.html, as it provides tips for preparing questions that draw responses from our members.
For example, you can:
- outline what steps you took to find answers (and why they weren't helpful)
- share screenshots of what you've seen/done
- make sure you've applied the appropriate tags

The more details you provide, the more likely it is that members will be able to help you. Should you wish, you can revise your question by selecting Actions, then Edit.
By adding a picture to your profile you encourage readers to respond to your question. Learn more about your profile here: https://developers.sap.com/tutorials/community-profile.html

[Nawfal]

Hi,

In addition to what Julian has proposed. You can also consider using a second local repo where you export your entire project to it without changing or renaming any object.

Thanks

Nawfal

[Julian_Riegel]

Hi there,

unfortunately there is no way of doing this, unless you want to heavily manipulate the .atl file of the Job you want to replicate.

I would suggest three options:

1. Replicate each and every object from top to bottom JB->WF->DF etc. as you want to do it already and as per following blog: https://blogs.sap.com/2015/08/18/tutorial-how-to-duplicate-a-job-batch-in-sap-data-services-designer...

Change all JB WF DF names and replace the table objects

2. Export your current Job(which would be final Version) as an .atl and do all the required changes including renaming of Job, WFs, DFs target tables etc. within DS Designer - Once you are done and have changed all dependent objects, import the old job. This leaves you with two independent jobs aswell.

3. This depends on the requirement behind your need to replicate the Job. What is the reason you need to duplicate the Job in the first place? You could set up specific system configurations and/or aliases to pull data from/write to different targets.