It is definitely possible to assign more than one repository for a job.
After manually assigning the second repository you could see that the job is still displayed the same way in the identity center but in the background there is another job added, with different id, and therefore there are two lines in mc_jobs table, one per repository.
Running an insert into mc_jobs table from "to database" pass is possible, but there are so many colums to fill and there could be other tables involved. I hope there is a better way to do that, like a stored procedure.
I am looking for a similar functionality as you as we need to be able to run lot of update jobs for dozens of repositories.
Tested in my sandbox to change the repository for dummy job with update-statement and ran the dummy job. The job got the repository reference correctly (all it did was to print the repository name out) and I was able to run it.
I was happy with that but chose not to go further as we have problems with jobs that are executed manually in MMC..
Change the repository 5 times in MMC and the passes in the job lose the repository (same as the problem in this thread: http://scn.sap.com/thread/3695370).
Changing the repository in MMC changes also the job name, but changing the repository with update-statement changes only the repository in job. So maybe there is more required than the update-statement (or maybe not - no idea).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.