hi
your issue can sometimes arise. Nevertheless don't understand why you say you need to activate manually. Could you give some clue on this (emergency, could not find a solution ...)
i think what you should do first is to check the log of the failed transport.
you should investigate and find the details in order to get a clue of what is triggering this issue.
Doing a kind of forced activation would not prevent you having other issues linked to this unresolved infoobject transport. Could be that you forgot to transport an attribute first for instance or something else. Did you change the properties of the infoobject, it lenght the type or something structuring ?
Please give détails to understand what could happen.
Once you find out the origins of the error create a new transport request containing the correction + the infoobject in question alone.
furthermore if i remember well therewas years ago some Tools exist like in transaction rsrv or with rsd1 screen.
finally from my point of view the option of activating objects, cubes, multis with the rsdg_xxx_activate is for identified issue, which doesn't not seem to be your case.
Don't know where you stand in your project, (new, maintenance, evol) it is always better to understand what happens so that you have better control.
hope this helps.
regards
Boujema
ps contrary to the two first post the program mention do not activate cubes, for cube from the top of my head it is rsdg_cube_activate
